Facebook Ads: Troubleshooting#
The status of a campaign, ad set or ad is not correct when fetching data from Facebook Ads#
If the status of an object is incorrect, for example if an ad is inactive but its status is shown as active when fetching data for a long date range, this is because the metadata for the authorization used in this datastream is out of date.
To resolve this issue, follow the steps in Synchronizing metadata for the authorization used in this datastream.
Note
Metadata for an authorization with a large number of ad accounts is refreshed in batches, so an individual account can be up to a week behind. Synchronize the metadata manually when you need it to be current.
A campaign, ad set, or ad disappeared from my data#
Meta excludes archived and deleted objects from the lists it returns. An object that was collected while it was active is not collected again once it is archived, even though it can still be retrieved individually in Meta.
This is expected behavior rather than an error, and it also explains why the number of objects in your data extract decreases over time.
Some ad accounts are missing from my data extract#
When Meta refuses a request for one ad account, Adverity records a warning, skips that account, and continues with the remaining ones. The datastream completes successfully, so the missing accounts are only visible in the datastream warnings.
Accounts are skipped when the authorization lacks permission for them, when the account is not enabled, or when two-factor authentication is enforced but the authorizing user is not enrolled.
To resolve this issue, check the datastream warnings of the fetch to identify the affected accounts, then confirm that the authorization has access to each one.
Note
A fetch that returns no data at all does not produce a warning. If your data extract is empty, check that the date range and the selected accounts contain data for the period you requested.
Troubleshooting conversions#
Select actions (in fields) and action_type (in action breakdowns). Conversions will come through under actions.offsite_conversions.
If this field isn’t coming through in your extracts then conversions are zero. You should force action fields and fetch a larger time range.
“Missing Permission” errors during ad account updates#
If “Missing Permission” errors appear as warnings during ad account updates, this means that Adverity encountered an ad account for which the connected Facebook account does not have sufficient permissions.
To resolve this issue:
Ensure the Facebook account used for authorization has the correct roles and permissions to access all ad accounts configured in the datastream. Review Facebook’s documentation on managing roles and permissions.
Even with warnings, the update process will continue for other ad accounts. Check the issues tab for specific details on affected accounts.
Nonexistent objects during ad account updates#
If warnings related to “nonexistent objects” appear during Facebook Ads ad account updates, this indicates that certain ad accounts or related entities are no longer available or accessible via the Facebook API.
In such cases, the system will gracefully skip these nonexistent objects and continue the update process for other valid ad accounts. This prevents the entire update from failing. Review the issues tab for specific details on which objects were skipped.
“An unknown error occurred” during ad account updates#
If “An unknown error occurred” messages or rate limiting issues appear during Facebook Ads ad account updates, the system is designed to automatically retry these requests.
This improves resilience against intermittent API issues or temporary rate limit exceedances, reducing the frequency of update failures. If issues persist after retries, check the issues tab for further details.