1. Page Views results will stay the same regardless of the date range chosen
Adding page views as a metric in any widget and expecting the results to vary by date range won't work.
Why does this happen? LinkedInās API does not support combining demographic breakdowns with custom time intervals. Meaning, displaying historical results by demographics such asĀ Job Function,Ā Seniority, or Industry, or as overallĀ performance data for a custom date range, won't change the results. This is because the metric Page Views only gives you lifetime results.
Recommendation: Use Page Views Lifetime as a KPI instead of adding it to a table. This helps avoid confusion.
2. Geographic Demographic Cost Differs from Campaign-Level Totals
Summing costs broken down by individual countries produces a higher total than the total account or campaign spend.
Why does this happen? LinkedIn's default location targeting tracks members based on "Recent or Permanent location". An individual traveling between regions (e.g., living in Austria but traveling through Germany and Switzerland) may have ad spend attributed to multiple locations, leading to double-counting when summed.
Also, at the campaign and account levels, LinkedIn credits back cost adjustments caused by ad over-delivery, reporting a net cost.
3. Total Impressions Differ When Broken Down by Industry
Total impressions for a campaign might equal x number, for example, 420,000, but adding an Industry as a dimension increases the result, for example, 570,000.
Why does this happen? Profiles and company dimensions on LinkedIn can belong to multiple industry classifications simultaneously. When an ad impression is delivered to a user associated with more than one industry, LinkedIn attributes that impression to each qualifying industry category in demographic reports. Therefore, you might see that the total of impressions might be lower than the impressions attributed to specific dimensions.
4. Total Impressions For The Post Performance widget Are Lower Than the Overall KPI
Summing impressions across all individual posts yields a total lower than the overall Impression KPI.
Why does this happen? Impressions registered at the Page/Company level are not restricted to organic or sponsored post streams. Overall account impressions include direct visits to the main LinkedIn Page, tab views, and non-post ad placements.
5. Lifetime Followers Are Different in LinkedIn than in Swydo
Swydo displays X number, for example, 4,812 followers, whereas LinkedIn's header interface shows 5k followers.
Why does this happen? In the LinkedIn UI, follower counts get rounded (e.g., rounding 4,812 to "5k"). The API endpoint fetches the unrounded, precise follower count directly, and this is what is shown in Swydo. The exact unrounded number can be verified on the main LinkedIn Company Page management sidebar.
6. Campaigns or Ad Groups Are Missing from Reports
Out of several active campaigns or ad groups running on LinkedIn, only a subset appears in reports without active filters.
Why does this happen? LinkedIn's underlying endpoint architecture requires explicit entity filters when retrieving performance data for certain structures. Requesting campaign or ad group level data without passing explicit campaign IDs in the request payload can cause the API to omit active entities.