How to connect Meta safely
Authorize the correct identity, review discovered accounts, and know when to reconnect.
Copy the article as Markdown to paste it into an AI agent.
Before you begin
- Meta access to the businesses and ad accounts managed by the agency.
- Confirm the active Workspace and the Meta identity that will be authorized.
Expected result
The correct Meta identity will be authorized in the active Workspace, and discovered ad accounts will appear in Integrations.
Before you start
Use a Meta identity with access to the businesses and accounts managed by the agency. The connection requests permissions for ads, businesses, pages, and WhatsApp because Agencify reads resources and also supports authorized change flows.
Requirements
- The correct Workspace is selected.
- An active Meta session for the identity being authorized.
- Access to the required Business Managers and ad accounts.
- An active subscription or trial when required.
Permissions
Owners, Admins, and Members can connect Meta. Viewers cannot manage integrations.
Steps
- Confirm the active Workspace in the sidebar.
- Open Integrations.
- In the Meta Ads card, select Connect Account Meta Ads.
- If a connection already exists and access must be renewed, use Reconnect.
- In Meta, confirm the identity, businesses, and requested permissions.
- Return to Agencify and wait for account discovery.
- Check the name, ID, status, and Business Manager for each account before linking it to a client.
Validation
The Meta Ads card should show the connection and discovered accounts. Confirm that the accounts belong in this Workspace and that the displayed Business Manager is correct.
Troubleshooting
- If no account appears, confirm that the identity can access a Business Manager with owned accounts.
- If only some accounts appear, review permissions in each business.
- If the connection is expired or revoked, use Reconnect.
- If a page or another asset is still missing, first check the account linked to the client.
Limits and safeguards
Discovery checks Business Managers and their owned accounts. Businesses with insufficient permission may be skipped, and shared-only accounts may not appear. The connection can finish without finding accounts. Token lifetime is not guaranteed. Reconnect renews authorization without requiring a disconnect first. Disconnect attempts to revoke provider access.
Related articles
- What Agencify reads, syncs, and changes.
- How to connect Google safely.
- An account, page, or asset is missing.
Was this article helpful?
Related articles
- What Agencify reads, syncs, and changesDistinguish provider reads, local synchronization, and real changes in Meta or Google.
- How to connect Google safelyAuthorize the correct Google account and review discovered direct accounts and MCC subaccounts.
- An account, page, or asset is missingIdentify whether the issue is in the Workspace, integration, client, or provider access.