Meta Ads
OAuthAdvertisingOrg connection
Org-level connection
Meta Ads is connected once at the org level by an admin. The credential is shared across all groups that have been granted access — individual team members don't need to connect their own accounts.
How to connect
Click "Connect with OAuth" and sign in with the Facebook account that can access your Meta ad account. After connecting, choose the ad account On Belay should use for spend and performance.
Ready to connect?
Sign in to On Belay and open the Integrations page to add Meta Ads.
Permissions (scopes)
These are the data scopes On Belay can be granted for Meta Ads. Your org admin controls which scopes are enabled per group.
| Scope | Description | Access |
|---|---|---|
ads_read | Read ads | Read only |
ads_management | Manage ads | Read / Write |
business_management | Manage business assets | Read / Write |
Troubleshooting
"redirect_uri_mismatch" error during OAuth
Your OAuth app's authorized redirect URIs don't include the On Belay callback URL. Add
https://app.onbelay.ai/api/oauth-callback/meta_ads to the allowed redirect URIs in your OAuth app settings."invalid_scope" error
The API or scope isn't enabled in your cloud project. For Google integrations, make sure the relevant API (e.g. Google Ads API, Search Console API) is enabled in Google Cloud Console for your project.
Connected but Claude can't access data
Check that your group has been granted access to this integration in On Belay → Groups → [your group] → Integrations. Also verify the specific scopes your group is permitted to use match what your query requires.
Still stuck? We're happy to help.
Contact support →