Meta connection troubleshooting

Last updated: May 19, 2026

Meta connection troubleshooting

Quick-fix reference for the 10 most common Meta integration issues. Each entry has symptom + likely cause + fastest fix. For anything outside this list contact support@wevion.ai with your meta_user_id (visible at /connect/meta detail drawer).

Who is this for

Mediabuyers and admins hitting a Meta connection problem. Bookmark this page.

1. OAuth popup blocked by browser

Symptom: clicking Connect does nothing or shows a tab that immediately closes.

Cause: browser popup blocker active for app.wevion.ai.

Fix:

  • Allow popups for app.wevion.ai in browser settings

  • Retry Connect

  • If using a corporate browser policy: contact IT to whitelist the OAuth domain

2. "No ad accounts found" after OAuth

Symptom: OAuth completes successfully, but the Ad accounts section at /connect/meta is empty.

Cause: the Facebook user that authenticated has no role on any ad account in any Business Manager Wevion was shared with.

Fix:

  • In Meta Business Manager: verify the user has at least Advertiser role on at least one ad account

  • The BM containing the ad accounts must be shared with Wevion during OAuth (when Facebook prompts BM selection)

  • Disconnect Wevion from Facebook app settings (Settings & Privacy → Apps), reconnect — fresh BM selection prompt

3. Sync stuck on "Syncing" > 1 hour

Symptom: a connected ad account shows Syncing badge for hours.

Cause: usually Meta API rate limit. Sometimes a transient Meta API error.

Fix:

  • Wait 30 minutes (rate limit windows reset every hour)

  • Refresh /connect/meta page

  • If still stuck after 2 hours: open the account detail drawer → Force sync button → check error log

  • If error mentions "rate limit exceeded": split sync across more time (Wevion auto-throttles future syncs)

  • If error mentions "permission denied": Meta BM role was removed; reconnect

4. Token revoked (yellow connector card)

Symptom: connector card turns yellow with "Token expired — Reconnect".

Cause: see meta-107 token health for causes. Common: Facebook password changed, app revoked, account suspended.

Fix:

  • Click Reconnect

  • Complete OAuth flow with the same Facebook account

  • Sync resumes within 15 min; no data lost

5. Pixel showing Inactive despite site traffic

Symptom: at /pixels, the Meta Pixel shows Inactive even though your site has traffic.

Cause:

  • Pixel JS installed after </head> close tag (load order)

  • Pixel installed twice (double-firing → first one wins, may conflict)

  • Ad blocker on your test browser

  • Wrong pixel ID in the snippet

Fix:

  • Verify snippet is before </head>

  • Check there's only one pixel snippet on the page (browser DevTools → search HTML for fbq()

  • Test in incognito browser (no ad blockers)

  • Verify pixel ID matches what's in Meta Events Manager

  • Wait 24 hours after fixing — Meta's status updates daily

6. CAPI access token rejected

Symptom: setting up CAPI (meta-105), the access token is rejected with "Invalid access token".

Cause: token from wrong scope, expired, or copied with extra whitespace.

Fix:

  • Regenerate the CAPI access token in Meta Events Manager → pixel → Settings → Conversions API → Manage Integrations → Generate access token

  • Paste without leading/trailing spaces

  • Verify the access token has the ads_management scope (Meta generates this scope for CAPI tokens by default)

7. Page missing from import list

Symptom: a Facebook Page you manage doesn't appear in the Pages list at /connect/meta.

Cause: the Facebook user that authenticated lacks the required role on that Page (needs Admin, Editor, Advertiser, or Analyst).

Fix:

  • Meta Business Manager → Pages → find the Page → assign the FB user a role

  • Wait 15 min for Wevion's next sync

  • If still missing: disconnect Wevion, reconnect (forces re-fetch of accessible Pages)

8. Wevion shows different spend than Meta Ads Manager

Symptom: Wevion shows €1.200 spend for last 7d; Meta Ads Manager shows €1.450.

Cause:

  • Timezone mismatch: Wevion uses workspace TZ, Meta defaults to Pacific Time. "Last 7 days" boundaries differ → different totals

  • Currency conversion: cross-channel reports auto-convert via daily FX, while per-account Meta view is native currency

  • Attribution window: Meta may use 1d-click + 1d-view by default; Wevion may use 7d-click — different conversion counts → different ROAS

  • Sync delay: Wevion is up to 15 min behind Meta's real-time

Fix:

  • Set Meta Ads Manager to the same TZ as Wevion workspace

  • Use the same attribution window in both

  • Wait 24h to compare (gives sync + attribution time to settle)

  • Use Meta as ground truth for dollar-level reconciliation, Wevion for optimization decisions

9. Duplicate ad accounts in import list

Symptom: the same ad account ID appears multiple times in the Ad accounts list.

Cause: the same ad account is accessible via multiple Business Managers (e.g. BM-Client-A and BM-Client-A-Backup both have access to act_123).

Fix:

  • Pick whichever instance — the import is per-account-ID, not per-BM relationship

  • Disconnect the duplicate (toggle OFF)

  • Wevion deduplicates internally based on account_id

10. Cannot disconnect last ad account "blocked"

Symptom: trying to toggle OFF the only connected ad account, Wevion shows an error.

Cause: pending publish jobs, active rules, or in-flight bulk launches depend on this account.

Fix:

  • Cancel pending bulk launches (Bulk Launch page → pending tab)

  • Pause or disable rules that target this account

  • Wait for in-flight publishes to complete (Ads Manager → Recent activity)

  • Retry disconnect

When to contact support

Contact support@wevion.ai when:

  • An issue isn't on this list

  • Reconnect doesn't restore sync (check error log first)

  • A Meta API error code Wevion shows you isn't documented in Meta's Marketing API docs

  • Data discrepancy between Wevion and Meta is > 10% across multiple accounts (potential bug)

  • CAPI deduplication isn't working despite correct event_id setup

Include in your email:

  • Your workspace ID

  • Affected meta_user_id (visible at /connect/meta detail drawer)

  • Affected ad account act_NNNNNNNNN

  • Exact error message text (copy-paste, don't paraphrase)

  • Approximate timestamp of the issue

Typical response: 1-2 business days; priority on Pro and Enterprise plans.

Useful diagnostics

Before raising a ticket, gather:

  • /connect/meta → Meta user detail drawer → Last sync + Last refresh timestamps

  • /connect/meta → account detail drawer → Last error field (if present)

  • Audit log filter: action: meta_sync_failed (admin view) — see team-113

  • Browser DevTools → Network tab while clicking Reconnect — capture any 4xx/5xx responses

Related