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.
In Meta Business Suite, go to Business Settings → Users → System Users
Create a System User (Admin role), then click "Generate New Token"
Select your app, set token expiration to "Never", and add permissions: ads_read, ads_management, business_management
Copy the System User access token and paste it below
Note: Your Meta app must have Standard Access (not Development) for production use. Apply via the app's App Review page.
Ready to connect?
Go directly to the integrations page in your dashboard.
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 | Write ads | Read / Write |
ads_management | Read campaigns | Read only |
ads_management | Write campaigns | Read / Write |
insights | Read insights | Read only |
business_management | Read audiences | Read only |
business_management | Write audiences | Read / Write |
Double-check that you copied the full key without any leading/trailing spaces. Some platforms show a truncated preview — make sure to copy the full token. If the key was generated with restricted scopes, verify it includes the permissions listed above.
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.
Some API keys have expiration policies. Generate a new key in Meta Ads and update it in On Belay → Integrations → Meta Ads → Update key. Consider creating a dedicated service account or machine user for On Belay so the key isn't tied to a personal account.
Still stuck? We're happy to help.
Contact support →