Support
Get help with your Meta connection
Common failure modes, what they usually mean, and how to reach a person when the documentation does not resolve the problem.
Where to get help
Start with the documentation for anything that looks like a configuration or permission problem — most connection failures are one of a small number of known causes.
Developer documentation
Covers the authorization flow, permission scopes, webhook verification, token lifecycle and the full error reference.
Best for configuration, integration and error questions.
Browse documentationError reference
Every error the connection flow can surface, with the likely cause and the specific next step for each one.
Best when you have a specific error message or a failed redirect.
Open error referenceContact the team
Send details of the problem, including what you attempted and what the interface returned, and we will follow up by email.
Best for account-specific problems and anything unresolved by the docs.
Open the contact formData and deletion requests
Request deletion of stored integration data, ask what is held for your account, or withdraw a previously granted permission.
Handled through a dedicated request form with a tracking reference.
Submit a data request
Common problems
These account for most reported connection failures. The reference column links to the section with the full explanation.
Redirect fails immediately with a URI mismatch
Likely causeThe redirect URI sent in the authorization request does not exactly match a URI registered in the Meta app.
What to doOAuth flowCompare the registered value character for character, including scheme, host, port, path and trailing slash. Register each environment separately.
Returned to the site with an “access denied” style error
Likely causeConsent was declined in the Meta dialog, or the dialog was closed before completion.
What to doError referenceRetry the connection and complete every step of the Meta dialog. Nothing is stored when consent is not granted.
A required asset does not appear after connecting
Likely causeThe asset was not selected during consent, or the signed-in account lacks an admin role on it.
What to doPermission scopesReconnect and select the asset explicitly. Confirm the account holds an admin role in Meta Business Settings first.
Connection worked, then stopped after a period of time
Likely causeThe stored access token expired, or access was revoked from the Meta side.
What to doAccess tokensReconnect to obtain a fresh token. If it recurs quickly, check whether an administrator removed the app or changed asset roles.
Events are not arriving from Meta
Likely causeThe webhook subscription is not active, the endpoint is unreachable over HTTPS, or deliveries are failing signature verification.
What to doWebhooksConfirm the endpoint responds to the verification challenge over HTTPS and returns success quickly. Check that the signing secret matches.
The connect page says the integration is not configured
Likely causeThe server-side Meta environment variables are not set in this deployment.
What to doGetting startedSet the authorization URL, app ID and redirect URI as server-scoped variables, then redeploy. This is expected in an unconfigured environment.
| Symptom | Likely cause | What to do | Reference |
|---|---|---|---|
| Redirect fails immediately with a URI mismatch | The redirect URI sent in the authorization request does not exactly match a URI registered in the Meta app. | Compare the registered value character for character, including scheme, host, port, path and trailing slash. Register each environment separately. | OAuth flow |
| Returned to the site with an “access denied” style error | Consent was declined in the Meta dialog, or the dialog was closed before completion. | Retry the connection and complete every step of the Meta dialog. Nothing is stored when consent is not granted. | Error reference |
| A required asset does not appear after connecting | The asset was not selected during consent, or the signed-in account lacks an admin role on it. | Reconnect and select the asset explicitly. Confirm the account holds an admin role in Meta Business Settings first. | Permission scopes |
| Connection worked, then stopped after a period of time | The stored access token expired, or access was revoked from the Meta side. | Reconnect to obtain a fresh token. If it recurs quickly, check whether an administrator removed the app or changed asset roles. | Access tokens |
| Events are not arriving from Meta | The webhook subscription is not active, the endpoint is unreachable over HTTPS, or deliveries are failing signature verification. | Confirm the endpoint responds to the verification challenge over HTTPS and returns success quickly. Check that the signing secret matches. | Webhooks |
| The connect page says the integration is not configured | The server-side Meta environment variables are not set in this deployment. | Set the authorization URL, app ID and redirect URI as server-scoped variables, then redeploy. This is expected in an unconfigured environment. | Getting started |
What to include in a report
Providing these details in the first message usually removes an entire round trip.
- The page or step where the problem occurred, and the exact time it happened.
- What you expected to happen, and what happened instead.
- The full text of any error message or error code shown on screen.
- The Meta asset type involved, such as an Instagram professional account or a Facebook Page.
- Whether the account you signed in with holds an admin role on that asset.
- Whether the problem is reproducible, and the steps that reproduce it.
Reporting a security issue
If you believe you have found a vulnerability, report it privately rather than opening a public discussion so it can be addressed before wider disclosure.
Still stuck?
Send the details listed above and we will follow up by email with the next step.