> For the complete documentation index, see [llms.txt](https://docs.hockeystack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hockeystack.com/marketing-intelligence/report-examples-and-insights/goals/linkedin-impressions-different-ways-of-measuring.md).

# LinkedIn Impressions: Different Ways of Measuring

When analyzing LinkedIn impressions in HockeyStack, it’s important to note that impression counts may vary depending on the data source used. \
\
When using the **LinkedIn Ads List integration goal**, impression data is pulled directly from LinkedIn’s API. Due to LinkedIn’s privacy constraints, impression metrics with a value of **2 or less are not included** in the data. This may result in lower impression counts when compared to filtering Impressions by Ad Network = LinkedIn.\
\
For accurate analysis, ensure you're comparing data from the same source and be aware of these limitations when using the LinkedIn Ads Account List integration.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hockeystack.com/marketing-intelligence/report-examples-and-insights/goals/linkedin-impressions-different-ways-of-measuring.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.