Connect a Meta Ads Access Token Fallback

Connect an encrypted fallback token using ads_read scope when Growth Hub OAuth is unavailable for Ads Insights.

Reviewed 2026-09-20

Overview

Growth Hub OAuth is the primary method to connect Meta Ads for Ads Insights. If OAuth cannot be completed, you can provide a manual encrypted system user token strictly scoped to ads_read as a fallback. Arth only reads advertising analytics and insights; it does not manage catalogs, product feeds, audiences, or ad campaigns.

Steps

  1. Step 1

    Primary setup: Use Growth Hub OAuth to connect your Meta account directly without manually handling tokens.

  2. Step 2

    Fallback setup: In Meta Business Settings, navigate to System Users.

  3. Step 3

    Assign the system user to your ad account with read-only performance insights access.

  4. Step 4

    Generate an access token with strictly the ads_read permission and paste it into Arth as an encrypted fallback.

Examples

Expected formatA long alphanumeric access token beginning with EAAB or EAAG.

Frequently asked questions

When should I use a manual token instead of OAuth?

Only use a manual token if your organization policies restrict direct OAuth logins in Growth Hub. Manual tokens require only the read-only ads_read permission.

Troubleshooting

Ads Insights reporting fails to load metrics.

Check

  • Confirm the token includes the ads_read permission.
  • Ensure the system user has been granted access to the target Ad Account.

Resolution

Generate a replacement token with ads_read permission assigned to the correct Ad Account and save it in Arth.

Take action