Skip to main content

Troubleshooting Facebook Ads connection

Fix common issues — permissions errors, missing ad accounts, disconnected tokens, and re-authentication.

Updated today

If you are having trouble connecting or syncing your Facebook (Meta) Ads data, this article covers the most common issues and how to resolve them.

Connection fails during Facebook authorization

Problem: You click Connect but the Facebook authorization window shows an error or closes without completing.

Possible causes:

  • Pop-up blocker is preventing the authorization window from opening.

  • You are not logged into Facebook, or you are logged into a different Facebook account than intended.

  • Your browser has stale Facebook session cookies.

Solutions:

  1. Disable pop-up blockers for app.datadrew.io and facebook.com.

  2. Log into the correct Facebook account in a separate tab before starting the connection.

  3. Clear your browser cookies for facebook.com and try again.

  4. Try using an incognito/private browsing window.

No ad accounts appear after authorization

Problem: You successfully authorize with Facebook, but no ad accounts are listed for selection.

Possible causes:

  • The Facebook account you authorized with does not have Ad Account Admin or Business Admin access to any ad accounts.

  • You denied the required permissions during the Facebook authorization step.

Solutions:

  1. Verify that your Facebook account has admin access to at least one ad account in Meta Business Settings.

  2. Disconnect and reconnect the integration from Settings > Integrations. Make sure to accept all requested permissions during the authorization step.

Token expired or revoked

Problem: Your Facebook Ads data stops syncing and you see a "disconnected" or "error" status in your integrations.

Possible causes:

  • You changed your Facebook password, which invalidates all active tokens.

  • You removed Datadrew from your Facebook app settings.

  • Facebook's data access authorization expired (tokens have a data access expiry, typically around 90 days for some configurations).

  • A Facebook Business Manager admin removed your access to the ad account.

Solutions:

  1. Go to Settings > Integrations in Datadrew.

  2. Find the affected Facebook Ads integration and click Reconnect.

  3. Complete the Facebook authorization flow again. Select the same ad account(s).

  4. Your data pipeline will resume from where it left off.

Data is syncing but metrics seem wrong

Problem: Facebook Ads data appears in Datadrew but the numbers do not match what you see in Facebook Ads Manager.

Possible causes:

  • Attribution window differences -- Facebook Ads Manager may be using a different attribution window than the default 7-day click, 1-day view.

  • Timezone mismatch -- Your ad account timezone may differ from what you expect.

  • Data delay -- Facebook adjusts conversion data for up to 7 days. If you are comparing very recent data, Datadrew may not have the final adjusted figures yet.

  • Date range -- Ensure you are comparing the exact same date range in both platforms.

Solutions:

  1. Check your attribution settings in Facebook Ads Manager and match them when comparing.

  2. Verify the timezone of your ad account in Meta Business Settings.

  3. Wait 24 to 48 hours for very recent data to stabilize before comparing.

Sync is stuck or taking too long

Problem: The initial sync has been running for many hours without completing.

Possible causes:

  • Very large ad account with years of historical data.

  • Facebook API rate limiting.

Solutions:

  1. Initial syncs for large accounts can take up to several hours. Give it at least 6 hours before contacting support.

  2. If the sync has been stuck for more than 12 hours, contact us at support@datadrew.io with your store name and we will investigate.

Need help? Contact us at support@datadrew.io.

Related articles


Need help?

If you have questions or run into issues, reach out to us at support@datadrew.io or use the in-app chat. We're happy to help.

Did this answer your question?