# LinkedIn Ads

Below is the updated documentation, including the newly listed fields.

***

## LinkedIn Ad Impressions & Engagement

HockeyStack’s LinkedIn Account List Integration add-on pulls account-based ad impression and engagement data from LinkedIn Ads. You can use this data in your attribution reporting, segmentation, or when viewing a single account’s journey.

### How It Works <a href="#block-802b356172564281b1b7ccb856892378" id="block-802b356172564281b1b7ccb856892378"></a>

HockeyStack can pull impression and engagement data daily by company & campaign to capture changes over time. If it detects a change in any of the metrics, it inserts a Goal related to that change.

**Goals:**

* LinkedIn Ads Impressions Changed
* LinkedIn Ads Ad Engagements Changed

The “Changed” label indicates the difference since the last time data was pulled (e.g., yesterday). All of these goals use the same action and user property schema outlined below.

### Action Properties

| Property                 | Type   | Description                                                                                                    |
| ------------------------ | ------ | -------------------------------------------------------------------------------------------------------------- |
| impression\_change       | Number | The change in impressions since the last data pull                                                             |
| ad\_engagement\_change   | Number | The change in ad engagements since the last data pull                                                          |
| linkedin\_campaign\_name | String | The name of the LinkedIn campaign associated with the impressions/engagement                                   |
| linkedin\_campaign\_id   | String | The LinkedIn campaign’s unique ID                                                                              |
| video\_views             | Number | The number of video views recorded                                                                             |
| video\_completions       | Number | Number of times your video was watched at 97-100% of its length, including watches that skipped to this point. |

### User Properties

| Property                       | Type   | Description                                             |
| ------------------------------ | ------ | ------------------------------------------------------- |
| company\_id                    | String | The associated CRM company ID, if found.                |
| linkedin\_company\_id          | String | The company’s LinkedIn ID                               |
| linkedin\_account\_id          | String | The LinkedIn Ads account ID associated with the data    |
| linkedin\_company\_url         | String | The LinkedIn profile URL of the company                 |
| company\_name                  | String | The company’s name                                      |
| company\_domain                | String | The company’s website domain                            |
| company\_number\_of\_employees | String | The range of employees the company has                  |
| company\_industry              | String | The industry the company is associated with on LinkedIn |

### Caveats <a href="#block-086895363ef247a0b8e1e3d6e77a65d6" id="block-086895363ef247a0b8e1e3d6e77a65d6"></a>

LinkedIn only provides impression and engagement data if the metric is greater than 2, due to privacy constraints. This might cause slight accuracy issues when reporting on very low-engagement accounts or campaigns.

The LinkedIn API can be a bit inconsistent when it comes to reporting impressions. LinkedIn has a unique way of calculating these metrics, which often leads to noticeable differences between the impression counts shown on your LinkedIn dashboard and the numbers reported by HockeyStack. This isn’t an error on either end—rather, it stems from the accuracy caveats that LinkedIn clearly outlines in its [documentation](https://learn.microsoft.com/en-us/linkedin/marketing/integrations/ads-reporting/ads-reporting?view=li-lms-2025-01\&tabs=http).

Because metrics are approximate, you may observe minor inconsistencies when comparing:

* Similar time ranges, for example, reporting on results over 7 days vs. 8 days
* The sum of daily metrics to the full corresponding time period
* Reporting levels, for example, adding campaign level data and comparing it to account level data

To minimize the effect of this approximation, select:

* A full time period instead of adding up daily metrics for that time period
* The highest reporting level you want to view, for example, selecting account level data instead of adding up campaign level data

### **Historical Data Availability**

The LinkedIn Ads API allows access to historical data for up to **2 years**.&#x20;


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.hockeystack.com/integrations/ad-platforms/linkedin-ad-impressions-and-engagement.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.