About discrepancies in LinkedIn Company Pages data

Some data source fields cause confusion by appearing as the same metrics. However, they are from different query types/end-points, which result in different calculations.

Check if your discrepancies are caused by:

• Total impressions (from Share Totals): Lifetime count of all post/share impressions for the page
• Impressions (from Share Statistics): Time-based count of post/share impressions (affected by date range, is splittable by date/month)
• Total comments (from Share Totals): Lifetime count of all post/share comments for the page
• Comments (from Share Statistics): Time-based count of post/share impressions (affected by date range, is splittable by date/month)
• Update comments (from Update Details): Count of comments for a specific post/share, use with Update ID dimension

The design of LinkedIn's API means that video posts are only available through the UGC chart type. This means that you need to pull the missing posts into a different chart.

To get this data, pull video posts into a different chart. Use the "UGC details" query type.

Data Studio’s data blending feature can also help resolve this issue. Learn more about data blending.

The documentation for the LinkedIn Company Pages API notes the following delays that may occur in data fetched through API:

• Follower Statistics: Endpoint requests up to 12 months in the past and up to 2 days before the end date of your query. This may occur up to 2 days of delay on current follower data.
• Likes and Comments for Updates/Posts: There can be up to 48-hour delays when reflecting the removed/deleted likes and comments.
• Updates/Post metrics: These could be delayed by up to 48 hours.

The API and the export reports from LinkedIn Company Pages are both in UTC time, so the values reported back for a given time range may be affected by this.

Depending on the timezone you’re in, you may need to adjust the date range forward or back by 1 day to get data that matches the reporting. Note that the date adjustment will depend on which direction you are from UTC +0 (if forward, you need to add a day; if back, remove a day).

For example, to get the data for the actual dates of January 1, 2021 to January 7, 2021 in the Helsinki timezone, you’ll need to adjust the date range to January 2, 2021 to January 8, 2021. Otherwise, the export report and the API will both return data from December 31, 2020 to January 6, 2021.

Learn more about timezone settings and timezone discrepancies.