Troubleshooting Facebook Ads Imports
Use this guide after you save credentials.
It covers setup, manual runs, scheduled runs, and backfills.
For access token or authorization code errors, see Credentials.
Quick Checks
Section titled “Quick Checks”Before changing credentials or app settings, check these items:
- Check Run history for the exact Meta error.
- Check Account IDs.
- Use numeric IDs only.
- Do not include the
act_prefix. - Separate multiple Account IDs with commas or semicolons.
- Check Facebook access.
- The authorized Facebook user must access every selected ad account.
- Check Permissions.
- The token must include
ads_readandads_management. - For large backfills, reduce the date range, selected fields, or breakdowns.
- If the error continues, open the Data Mart settings.
- Expand Advanced settings.
- Lower API Page Limit, for example to
25. - Save the Data Mart and rerun it.
If these checks look correct, match the Run history error with the cases below.
Common Import Errors
Section titled “Common Import Errors”| Error or symptom | Likely cause | What to do |
|---|---|---|
Invalid OAuth access token, Error validating access token, or Session has expired | The token expired, or Meta invalidated it. | Reconnect with Facebook. For manual credentials, generate a new access token. Then update the Data Mart credentials. |
Missing ads_read, missing ads_management, or a permissions error | The token lacks a required scope. The user may have removed it during authorization. | Reauthorize with both ads_read and ads_management. ads_read covers Insights endpoints. ads_management covers account and ad object endpoints. |
| App is not approved, app is in Development mode, or the app cannot access this ad account | The Meta app or user cannot access the selected ad account. Development mode only works for app roles. | Test with a user assigned to the Meta app and ad account. For external accounts, check App Review, advanced access, Marketing API access, and Business Verification. |
Account does not exist, account cannot load, or Unsupported get request | The Account ID is wrong. It may include act_, or the user lacks access. | Enter the numeric Account ID only. Remove act_. Confirm Admin, Advertiser, or Analyst access. |
| Import fails for only one account in a multi-account setup | One Account ID is invalid, or the user lacks access to that account. | Run the Data Mart with one Account ID at a time. Find the failing account. Then fix the ID or Meta access. |
Rate limit errors, Application request limit reached, or User request limit reached | Meta throttled requests for the app, user, or ad account. | Wait and rerun later. If the error repeats, reduce run frequency, date range, selected accounts, fields, or breakdowns. |
Please reduce the amount of data you're asking for, then retry your request or request timeout errors | The request asks Meta for too much data. | Reduce the date range, fields, or breakdowns. Then lower API Page Limit in Advanced settings and rerun. |
| Empty results with no obvious API error | The date range has no delivery data. The selected fields may have no values. | Check the same date range in Meta Ads Manager. Then try Ad Account Insights with spend, clicks, and impressions. |
Still Blocked
Section titled “Still Blocked”If the Run history error does not match any case above:
- Search Q&A.
- Open an issue to report a bug.
- Join the discussion forum.