Common Issues

Connection issues

I can't see all my ad accounts after connecting

This usually means your LinkedIn profile doesn't have the right role on those accounts. LinkedIn Ads requires you to have at least an Analyst role on an account for it to appear in Coupler.io. Ask your LinkedIn Ads admin to check your access level in Campaign Manager under Account settings > Manage access.

If you manage accounts through a Business Manager, make sure the LinkedIn profile you authenticated with is also added directly to the ad accounts — Business Manager access alone is not always sufficient.

I get an error when connecting to Looker Studio

If you're using the Coupler.io Looker Studio community connector, make sure you've completed a successful manual run of the data flow first before connecting to Looker Studio. If you see a connector error, try disconnecting and reconnecting the data source in Looker Studio, then re-authorizing.

My data flow fails with a timeout error

Timeout errors typically happen when you're requesting too much data at once — for example, a very wide date range combined with many metrics and a daily split across multiple ad accounts. Try narrowing the date range, reducing the number of selected metrics to under 18, or splitting the request into multiple data flows.

Missing data

The Reach metric or approximateUniqueImpressions column is empty

LinkedIn applies privacy thresholds to reach-related metrics. If an audience segment is too small, LinkedIn returns null instead of a value. This is a LinkedIn platform limitation and affects all tools — not just Coupler.io. Broaden your targeting or aggregate over a longer period to get non-null values.

I'm missing columns when pulling from multiple ad accounts

When accounts have different campaign types or settings, some columns may not be populated for all accounts. Make sure you're selecting the same metrics and dimensions across all accounts. If you're using Append mode to combine multiple account exports, column alignment depends on both sources returning the same schema.

I can't find ad names in the analytics report

Ad name is not exposed as a dimension in LinkedIn Ads analytics — this is a LinkedIn API limitation. To get ad names, pull the Creatives entity separately and use Coupler.io's Join transformation to match it to your analytics report on the creative ID field.

My Sponsored leads export is missing some submissions

Check that you haven't filtered by specific lead gen forms when you intended to pull from all forms. Leave the Lead generation forms field blank to fetch leads from every form under the selected ad account. Also verify the date range includes the period when the leads were submitted.

Permission errors

I get a "permission denied" or "unauthorized" error

Re-authenticate the LinkedIn connection in Coupler.io. LinkedIn OAuth tokens can expire or be revoked, especially if you changed your LinkedIn password or revoked app permissions. Go to your data flow's source settings, disconnect the account, and sign in again.

Data discrepancies

Numbers in Coupler.io don't match what I see in Campaign Manager

The most common cause is a timezone mismatch. LinkedIn Campaign Manager uses your account's timezone setting, while the API may return data in UTC. Check your Split data by period setting and compare the totals (not daily breakdowns) first to rule out day-boundary differences.

Also confirm you're using the same date range. LinkedIn's UI sometimes defaults to a different window than what you've set in your data flow.

Preview data looks different from exported data

The preview in Coupler.io shows a sample of your data and may not reflect the full export. Always verify against the actual destination output after a successful run rather than relying on the preview.

Rate limits

My data flow fails with a rate limit error

LinkedIn's Ads API has rate limits that can be hit when pulling large volumes of data — especially with many ad accounts, a long date range, and daily granularity all at once. If you hit a rate limit, space out your data flows, reduce the date range, or split one large data flow into multiple smaller ones.