Common Issues
Here are the most common issues you might run into when working with the Facebook Ads source in Coupler.io, along with how to fix them.
Connection issues
OAuth token expired
Facebook access tokens can expire or be revoked. If your imports start failing, go to the Sources page in Coupler.io and reconnect your Facebook account.
Permissions not granted
Make sure you granted all requested permissions during the OAuth flow. If you skipped any, disconnect and reconnect your Facebook account.
Two-factor authentication
If you recently enabled 2FA on your Facebook account, you may need to re-authenticate in Coupler.io.
Missing data or accounts
Ad account not showing up
You need Admin or Advertiser access to the ad account in Meta Business Suite. If you were recently granted access, try disconnecting and reconnecting your Facebook credentials.
No data returned
Check that the selected ad account has active or past campaigns for the date range you specified. An empty report usually means no ads ran during that period.
Missing recent data
The Facebook Ads API has a data latency of 1–2 days. Data for today or yesterday may be incomplete. Use yesterday's date or two days ago as your end date for reliable results.
Permission errors
"Insufficient permissions" error
Your Facebook user must have access to the ad account at the Admin or Advertiser level. Check your roles in Meta Business Suite > Business Settings > People.
"User does not have sufficient permissions for this action on this page"
This typically occurs when getting Page-related reports. To fix it:
The page owner should go to Facebook Profile Access Settings and verify you are not added as a user with Page or Task access that limits your scope.
Check your permissions in Facebook Business Manager: open the Business that owns the page, open your username settings, and confirm you have Partial access to the page.
If you're using the new Pages experience, you need Partial Access to the linked Facebook account.
After fixing permissions, remove Coupler.io from Business Integrations on your Facebook account, then delete and recreate the Facebook connection in Coupler.io.
Ad account access revoked
If someone removed your access to an ad account, imports for that account will fail. Contact the account owner to restore access.
Facebook Pages or Instagram Profiles not showing up
If a Facebook Page or Instagram Profile is missing from the selection dropdown in Coupler.io:
Check page permissions. You need Administrator access to the Page, or Page Editor access via Business Manager. With the new Pages experience, you need Partial Access to the linked Facebook account.
Reconnect your Facebook / Instagram connection. Click Reconnect if you see an error below the Pages/Profiles field. Log in to Facebook, approve any missed permissions, and re-select your Page or Profile.
Check app permissions in your Facebook account. Go to Facebook > Settings > Business integrations > View and Edit for Coupler.io. Make sure the needed page is selected under "Read content posted on the Page" and "Show a list of the Pages you manage."
If a page was connected but later disappeared, it's often because Facebook didn't provide the scope consent screen during the initial connection — especially when only one page was selected. Reconnecting and re-approving permissions typically resolves this.
Data discrepancies
Reach metric appears inflated in dashboards
Reach counts unique users over a time period — it is not summable. If you export daily Reach and aggregate it in Looker Studio, Google Sheets, or any other tool, you will double-count users who saw ads on multiple days, producing totals higher than what Ads Manager shows.
To match Ads Manager's Reach figure for a date range:
Use "Split data by period: Totals only" in Coupler.io so the API returns a single deduplicated Reach value for the entire period.
If you need daily granularity, display Reach per-row (e.g., per day or per campaign) and do not sum it in your dashboard.
CTR, CPC, CPM and other ratio metrics show incorrect totals
Ratio metrics like CTR (click-through rate), CPC (cost per click), and CPM (cost per 1,000 impressions) cannot be summed. If your dashboard tool (e.g., Looker Studio) uses SUM as the default aggregation, the resulting totals will be meaningless.
Instead, create calculated fields in your dashboard that recompute the ratio from raw totals:
CTR = Clicks / Impressions
CPC = Spend / Clicks
CPM = (Spend / Impressions) × 1,000
This ensures correct values at every aggregation level.
Numbers don't match Ads Manager
The most common cause is mismatched attribution settings. In Coupler.io Advanced settings, make sure the action attribution window matches what you use in Ads Manager. If nothing is selected in Coupler.io, a 7-day click window is used by default.
Other things to check:
Time aggregation — Verify that "Split data by period" in Coupler.io (Daily, Weekly, Monthly, or Totals) matches what you're viewing in Ads Manager.
Entity aggregation level — Coupler.io returns insights for the lowest entity for which you selected dimensions. If you selected Campaign name and Ad set name, the report is at the Ad set level. If you compare that to a Campaign-level report in Ads Manager, numbers will differ.
Breakdowns — Make sure the breakdowns in Coupler.io match those in Ads Manager. For example, if Coupler.io breaks down by Publisher platform but Ads Manager doesn't, the numbers won't align.
ROAS values are different
Facebook calculates ROAS using specific attribution windows. If Coupler.io uses a different window, ROAS values will differ. Check your attribution settings under Advanced settings.
Overinflated numbers with breakdowns
When using action breakdowns (like action type or action destination), totals may appear higher than expected. This is because a single action can be counted across multiple breakdown values. For accurate totals, avoid action breakdowns.
Daily vs. monthly totals don't add up
If you switch between "Daily" and "Totals only" in Split by period, rounding and attribution differences may cause slight variations.
Filters hiding deleted or archived entities
When you use any filter in Advanced settings, Facebook's API applies a default status filter that returns only ACTIVE objects. This means deleted or archived ads/ad sets/campaigns are excluded, and totals will be lower than what you see in the parent-level report in Ads Manager.
To include deleted and archived entities, add an explicit status filter alongside your other filters.
Conversion counts lower than Ads Manager (1-day engaged-view attribution)
Meta Ads Manager can display conversions attributed to a 1-day engaged-view window. This attribution window is not available through the Facebook Ads API, so Coupler.io cannot pull those conversions.
If you see fewer purchases or other conversions in Coupler.io than in Ads Manager, check whether Ads Manager is including 1-day engaged-view attribution. The difference is the conversions attributed to that window. To get the closest match, explicitly set your attribution windows in Coupler.io's Advanced settings to 7-day click + 1-day view and compare against the same setting in Ads Manager.
API errors
"Request to Facebook API has failed" (status 400 / deprecated metric)
This usually means a metric you selected has been deprecated by Meta. The error message from the API is:
(#100) The value must be a valid insights metric
To fix it:
Open your data flow in Coupler.io and go to the column selection step.
Look for any metric highlighted with a warning or that you don't recognize.
Remove the deprecated metric and re-run the import.
Meta periodically deprecates metrics across API versions. If you're unsure which metric is causing the issue, try removing recently added metrics one at a time until the import succeeds.
"Async Job failed" error
Facebook generates large ad reports asynchronously. If the job fails, you'll see an error like:
An error occurred during fetching data from Facebook: 'Async Job failed'
Common causes:
Temporary issues on Facebook's side — the report generation infrastructure may be overloaded.
Rate limits — the ad account has too many concurrent report requests.
Report too large — the combination of date range, breakdowns, and metrics produces a dataset that exceeds Facebook's processing limits.
To resolve:
Re-run the import after waiting a few minutes — transient failures often resolve on their own.
Narrow the date range or change the "Split by" interval to reduce report size.
If the same account consistently fails, split the data flow into multiple sources with smaller date ranges.
"Call was not successful" error
This is a generic error from the Facebook API, sometimes accompanied by a status 500 response:
An error occurred during fetching data from Facebook: 'Call was not successful'
It can be caused by:
Temporary Facebook API server issues
Permission problems on the ad account
Account-specific limitations or restrictions
In most cases, retrying after a few minutes resolves the issue. If it persists, verify that your Facebook connection is still active and that you have the required permissions on the ad account.
Rate limits
Import fails with rate limit error
Facebook limits how many API requests can be made per ad account. If you have multiple data flows pulling from the same ad account simultaneously, some may hit rate limits. Space out your scheduled refreshes or reduce the number of concurrent imports for the same account.
Last updated
Was this helpful?