Step 6 — Connect Meta and Google

This page is the In the app track for step 6 of the golden path. The agent track is at the bottom, under With the API / an AI agent.

Connecting your ad platforms lets Atribu pull in your campaigns, ad sets (or ad groups), individual ads, and daily spend data. This is what makes it possible to calculate ROAS (Return on Ad Spend) -- the ratio of revenue earned to money spent on advertising. Without this connection, Atribu can still track visitors and conversions, but it cannot tell you which specific campaigns are profitable.

What gets synced

Once connected, Atribu automatically imports:

Performance metrics like CPM (cost per thousand impressions), CPC (cost per click), and CTR (click-through rate) are calculated automatically from this data.

Connect your platforms

Troubleshooting

I do not see my ad accounts

• Meta: Make sure you are logging in with a Facebook account that has at least "Advertiser" access to the ad account. If you manage ads through a Business Manager, the ad account must be shared with your personal Facebook account.
• Google Ads: Make sure you are signing in with the Google account that has direct access (or Manager Account access) to the Google Ads customer account.

Data is missing or incomplete

• Recent changes: After connecting, the initial sync pulls historical data. This can take a few minutes for accounts with many campaigns. Check back in 10-15 minutes.
• Paused campaigns: Atribu imports all campaigns regardless of status (active, paused, archived). If you do not see a specific campaign, check that you connected the correct ad account.
• Spend shows zero: Some campaigns (especially brand awareness campaigns) may have impressions but very low or zero recorded spend on certain days. This is normal.

I need to reconnect

If your connection stops working (for example, if you changed your Facebook password or revoked access), go to Settings > Integrations, find the platform, and click Reconnect. Your historical data is preserved.

With the API / an AI agent

A connect is an OAuth consent: it needs a browser and a person who can grant it. What an agent can do is start it, hand the URL over, and detect completion.

curl -H "Authorization: Bearer atb_live_YOUR_KEY" \
  "https://api.atribu.app/api/v1/connections"

Only connected and syncing are working. Anything else is a connection that exists and is not delivering — readiness reports it as degraded, never missing, because the fix is to re-connect.

When one consent exposes several ad accounts, the connect lands pending and the choice is explicit:

curl -H "Authorization: Bearer atb_live_YOUR_KEY" \
  "https://api.atribu.app/api/v1/connections/pending/meta_ads"

curl -sX POST https://api.atribu.app/api/v1/connections/pending/meta_ads/finalize \
  -H "Authorization: Bearer atb_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"account_id": "act_1234567890"}'

Mint a session-less URL instead of sending them to the console (#1046):

curl -sX POST https://api.atribu.app/api/v1/connections/meta_ads/handoff \
  -H "Authorization: Bearer atb_live_YOUR_KEY" \
  -H "Content-Type: application/json" -d '{}'

meta_ads · google_ads · google_search_console · gohighlevel · stripe · mercadopago. The response is a hand-off — the same shape GET /api/v1/handoffs/{id} returns, so mint and poll need one parser. Whoever holds url completes it: signed out, on a phone, with no Atribu account. Poll until status settles.

A completed connect answers one of two result shapes: connection_id when the consent resolved to exactly one account, or pending_selection when a human must choose — which is what the two pending routes above are for. A failure names its reason (provider_denied, no_candidates, connect_failed, token_exchange_failed, origin_not_allowed, handoff_unusable).

Next steps