Explore the tabs below to learn more about different types of discrepancies that you might encounter between LinkedIn Company Pages and your Supermetrics reporting.
Types of discrepancies
Field selection and query type
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
Missing posts
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 Studio's native data blending feature.
Limits on number of shares fetched
The API has a limit of fetching 3000 shares, counting from newest to oldest. So if you are missing posts/shares from earlier periods, this is likely why.
Corrupted Posts / Title limitation to 400 characters
These are Posts that have previously caused failed API calls (status 500 in response) to the https://api.linkedin.com/rest/posts endpoint, and have required a fix on LinkedIn’s side.
Corrupted posts may include unnecessary spacing in the text or URLs, among other issues. The use of broken or invalid URLs is problematic.
Posts have a 400-character title limit, a limitation that was not present in the legacy APIs.