Meta Account Connection Troubleshooting
Last updated: April 18, 2026
Connecting and maintaining your Meta (Facebook) account is essential for Wevion to manage your ad campaigns. This article covers the most common connection problems and how to resolve them.
Prerequisites
- An Wevion account with an active subscription (or active trial)
- A Facebook account with access to at least one Business Manager
- Admin or Advertiser access to the ad accounts you want to connect
How It Works
Wevion connects to Meta through OAuth, where you log in with your Facebook account and grant permissions. This generates an access token that Wevion uses to read your ad data and manage campaigns on your behalf.
Tokens can have three statuses:
- ACTIVE — The token is valid and working. Wevion can sync data and manage campaigns.
- EXPIRED — The token has expired (Meta tokens typically expire after 60 days for user tokens). You need to reconnect.
- INACTIVE — The token has been manually deactivated in Wevion or revoked in Facebook.
Wevion monitors token health and sends notifications when tokens are about to expire or encounter issues.
Common Issues and Solutions
1. "Token Expired" — Cannot Sync Data or Manage Campaigns
Symptoms:
- Token status shows "EXPIRED" in the Meta Users page
- Data stops updating
- Campaign actions fail with "Invalid access token" errors
- You receive a "Token Expiring" notification
Cause: Meta user tokens expire after approximately 60 days. System user tokens may have different expiration settings.
Solution:
- Navigate to Meta Users in the left sidebar
- Find the user with the expired token (marked with "EXPIRED" status)
- Click the Reconnect button next to the user
- You'll be redirected to Facebook — log in and grant all requested permissions
- After completing the flow, you'll be redirected back to Wevion
- Verify the token status now shows "ACTIVE"
- Wait a few minutes for the initial data sync to complete
Tip: Enable the "Token Expiring" notification in your Telegram preferences to get alerts before tokens expire. This lets you reconnect proactively.
2. No Ad Accounts Appear After Connection
Symptoms:
- You successfully connected your Meta account, but no ad accounts are listed
- The sync appears to complete with zero results
Cause: The Meta user may not have access to any ad accounts in Business Manager, or the required permissions were not granted during OAuth.
Solution:
Step 1: Verify Access in Facebook Business Manager
- Go to business.facebook.com
- Navigate to Business Settings > Accounts > Ad Accounts
- Confirm your user is listed with at least "Advertiser" access on the target ad accounts
- If not, ask your Business Manager admin to grant you access
Step 2: Verify Permissions Were Granted
- Go to facebook.com/settings > Security and Login > Apps and Websites
- Find "Wevion" in the list of connected apps
- Click it and verify all permissions are granted
- If permissions are missing, remove Wevion from the list and reconnect from scratch
Step 3: Reconnect in Wevion
- Go to Meta Users in Wevion
- If the user already exists, click Reconnect
- During the Facebook OAuth flow, make sure to:
- Select all ad accounts when prompted (or "Select All")
- Grant all requested permissions — do not uncheck any
- After reconnecting, wait for the sync to complete (may take a few minutes)
3. "Invalid Access Token" Errors During Campaign Actions
Symptoms:
- Publishing, pausing, or editing campaigns fails
- Error message contains "Error 190" or "Invalid OAuth access token"
Cause: The access token has been invalidated. This can happen when:
- The Facebook user changes their password
- The user removes Wevion from their Facebook app settings
- Facebook detects suspicious activity and revokes the token
- The token naturally expires
Solution:
- Navigate to Meta Users
- Check the token status of the affected user
- Click Reconnect and complete the OAuth flow
- Retry the failed campaign action
4. "No Permission to Access This Ad Account"
Symptoms:
- Some ad accounts work fine, but specific accounts throw permission errors
- Error message references "ad account access" or "Error 100"
Cause: Your Meta user may have been removed from a specific ad account in Business Manager, or the account was transferred to a different Business Manager.
Solution:
- Open Facebook Business Manager and verify your access to the specific ad account
- If access was revoked, ask the Business Manager admin to re-grant access
- After access is restored, go to Meta Users in Wevion and click Reconnect to refresh permissions
- Wevion will re-sync the available ad accounts
5. Connected a System User Token but No Data Appears
Symptoms:
- You pasted a system user access token manually
- The token was accepted, but ad accounts or data are not appearing
Cause: System user tokens require specific configuration in Business Manager.
Solution:
Step 1: Verify System User Setup
- In Facebook Business Manager, go to Business Settings > Users > System Users
- Select the system user
- Verify it has admin or employee access to the required assets (ad accounts, pages, pixels)
Step 2: Verify Token Permissions
- The system user token must include these scopes:
ads_managementads_readbusiness_managementpages_read_engagement(if managing pages)
- If scopes are missing, generate a new token in Business Manager with the correct permissions
Step 3: Re-add the Token
- In Wevion, go to Meta Users
- Deactivate the existing system user entry
- Click Add System Token
- Paste the new token and enter the correct Business Manager ID
- Wevion will validate the token and sync available assets
6. Multiple Business Managers — Wrong Accounts Showing
Symptoms:
- You have access to multiple Business Managers but only see accounts from one
- Accounts from a specific Business Manager are missing
Cause: The OAuth flow connects all Business Managers accessible by the Facebook user. However, some assets may be filtered based on the primary Business Manager associated with the token.
Solution:
- If you need accounts from multiple Business Managers, make sure your Facebook user has access to all of them before connecting
- Reconnect in Wevion to refresh the full list
- For maximum control, consider using separate system user tokens for each Business Manager
7. Token Works in Wevion but Campaigns Don't Publish
Symptoms:
- Token status is ACTIVE
- Data syncs correctly
- But publishing campaigns fails with Meta API errors
Cause: The token may have read permissions but lack write permissions, or the ad account may have restrictions.
Solution:
- Check the specific Meta error code in the failed publish notification
- Common issues:
- Ad account spending limit reached: Increase the spending limit in Facebook Ads Manager
- Ad account disabled/restricted: Check facebook.com/accountquality for violations
- Policy violation on ad content: Review Meta's advertising policies for the rejected ad
- If the token lacks write permissions, reconnect and ensure all permissions are granted
Options and Configuration
| Setting | Location | Description |
|---|---|---|
| View token status | Meta Users | Shows ACTIVE/EXPIRED/INACTIVE for each connected user |
| Reconnect token | Meta Users > Reconnect | Refreshes the OAuth token |
| Add system token | Meta Users > Add System Token | Manually add a system user token |
| Deactivate token | Meta Users > Deactivate | Soft-deletes the token; disconnects associated assets |
| Token expiry alerts | Telegram > Preferences | Enable "Token Expiring" notification |
Preventive Measures
- Enable token expiry notifications via Telegram or in-app to get warned before tokens expire
- Use system user tokens for production accounts — they don't expire like user tokens and aren't affected by password changes
- Grant all permissions during the OAuth flow — selectively denying permissions causes partial functionality
- Don't change your Facebook password without reconnecting in Wevion afterward
FAQ
How often should I reconnect my Meta token? User tokens typically expire after 60 days. You'll receive a notification a few days before expiry. System user tokens with "never expire" setting don't need reconnection unless permissions change.
Can I connect multiple Meta users to one Wevion account? Yes. You can connect as many Meta users as needed, each providing access to different Business Managers or ad accounts.
Will reconnecting disrupt my running campaigns? No. Reconnecting only refreshes the access token. Your campaigns and settings remain unchanged.
I was prompted to "Select All" during OAuth — is that safe? Yes. Wevion only requests the minimum Meta permissions needed to manage ads. Selecting all ensures full functionality. Deselecting specific permissions may cause features to break.
Can a team member's Meta connection work for the whole team? Each user connects their own Meta account. However, the owner can see and manage all team members' connected accounts and their associated ad accounts.