Common Issues
Connection issues
LinkedIn authorization fails or redirects incorrectly
Make sure you're signed into the correct LinkedIn account (the one that manages your company page). If you have multiple LinkedIn accounts, sign out of the others first, then try authorizing again.
If you're still having trouble, try:
Clearing your browser cookies for LinkedIn.com
Using a different browser or incognito window
Ensuring you have Editor or Admin permissions on the company page
Company page doesn't appear in the page selector
Your page may not show up if:
You don't have Editor or Admin role on the page
The page was recently created (LinkedIn may need time to sync it)
You're signed into a personal account that doesn't manage the page
Verify your access level in LinkedIn by visiting the page and checking the "Admin tools" menu. You need at least Editor permissions to export analytics.
"Access Denied" error when trying to run the flow
This typically means your LinkedIn permission level changed after you authorized Coupler.io.
Solutions:
Check your company page role in LinkedIn (it may have been downgraded)
Re-authorize Coupler.io with your LinkedIn account
Ensure your LinkedIn account is still active on the page
Missing data
Post data not appearing in the export
For "Post: individual posts performance" reports, LinkedIn only includes posts from the last 2 years. Older posts won't appear.
Also verify:
Your date range (if specified) includes recent posts
The page actually has posts published in that period
You're not filtering out deleted or archived posts
If you're still missing data, check the data preview before running the full flow to see what's being pulled.
Follower count or demographics showing incomplete data
Demographic insights (follower demographics, audience demographics) only include members with complete LinkedIn profiles. LinkedIn doesn't provide demographic data for private or minimal profile members.
Also note:
"Page: lifetime overview" shows all followers, but demographics reports only break down profiled users
Some geographic regions may have small sample sizes and won't appear in results
Job title and seniority data depends on member profile completeness
Null or blank values in the export
This is a known issue when certain report types return metrics that aren't available for your page or time period.
Common causes:
Selecting metrics not available for your chosen report type
Demographic dimensions with no data (e.g., very few followers in a region)
Time periods with zero engagement
Try:
Checking your data preview before running the full flow
Starting with a simpler report type (like "Page: lifetime overview")
Extending your date range to capture more data
Video metrics showing zero or incomplete data
Video performance data is only available if your company page has published native LinkedIn video posts (not links to external videos). Text and image posts won't have video metrics.
Also:
Set a date range that includes your video posts
LinkedIn only tracks video metrics for videos published in the last 2 years
Private or restricted videos may not be included
Permission errors
"Requested version 20240101 is not active" error
This error occurs when LinkedIn's API version changes. It's usually temporary and resolves on LinkedIn's side.
What to do:
Wait a few hours and try again
Check LinkedIn's API status page for announcements
If the error persists after 24 hours, contact Coupler.io support
Your data flow may be temporarily disabled during LinkedIn API updates. Re-enable it once the error clears.
"Service Unavailable" (503) error
LinkedIn's API is temporarily down or overloaded. This usually clears within an hour.
Try:
Waiting 30 minutes and running again
Checking LinkedIn's status page
Running during off-peak hours (outside 9 AM–5 PM in your region)
Do not run the flow repeatedly while the error persists — it will increase quota usage.
426 error or "API version not supported"
This indicates a breaking change in LinkedIn's API that affects your data flow.
This usually means:
LinkedIn deprecated the report type you're using
Your account was moved to a new API version
Contact Coupler.io support if this occurs — we may need to update the connector.
Data discrepancies
Exported data doesn't match LinkedIn's analytics dashboard
Small differences (1–5%) are normal due to:
Time zone differences — LinkedIn reports in the viewer's time zone; Coupler.io may use UTC
Real-time vs. historical data — LinkedIn's dashboard is updated in real-time; exported data may be 6–12 hours behind
Rounding — LinkedIn displays rounded metrics; raw API data may differ slightly
Filtering — Your dashboard may apply filters not reflected in the raw export
Larger discrepancies (>10%):
Check your date range — make sure it matches LinkedIn's dashboard
Verify you're comparing the same report type
Check if LinkedIn made changes to the metrics definition
Post performance metrics changing after export
LinkedIn post metrics continue to accrue after publication. If you pull post data on day 1, then pull again on day 7, the numbers will be higher.
This is expected behavior. To track historical snapshots:
Pull the data regularly on a schedule
Archive each export with a date stamp
Use append mode to build a historical time series in your destination
Demographic percentages don't add up to 100%
Demographic data is based on incomplete profile information from LinkedIn members. Not all followers provide complete job title, seniority, or geographic data.
The percentages shown represent only profiled members, so the total may be significantly less than 100% if many followers have incomplete profiles.
Rate limits
Getting throttled after multiple runs
LinkedIn enforces rate limits on analytics API calls. If you run the same flow too many times in a short period, requests may be delayed or rejected.
Best practices:
Avoid running the same flow manually multiple times per day
Use scheduled runs instead (e.g., daily or weekly)
Space out manual test runs by at least 15 minutes
If you need frequent updates, use a longer date range rather than daily snapshots
Last updated
Was this helpful?