Connect Google Ads
Authorise Google Ads, pick the customer accounts to sync, and understand what gets imported.
Google Ads connects over OAuth. You sign in with a Google account that can see the accounts you want, approve read-only access, and then choose which customer accounts to sync.
Before you begin
- A Google account with at least read access to the Google Ads accounts you want to track.
- If you use a manager account (MCC), sign in with the manager — it exposes every child account in one connection.
Connect the account
- 1
Start the connection
Integrations → Google Ads → Connect in the Revenue Sensor console.
- 2
Sign in and approve
Google's consent screen opens in a popup. Approve the read-only Google Ads scope. The popup closes itself when it is done.
- 3
Select customer accounts
You will see every account the login can reach, including the ones under a manager account. Tick the ones you want; leave test and archived accounts off.
- 4
Let it sync
The first sync backfills your available history. The card shows a progress state and turns green when the backfill completes.
What gets imported
| Field | Notes |
|---|---|
| Cost / spend | Daily, per customer account, in the account's own currency. |
| Impressions and clicks | Daily totals, used for the delivery metrics on the dashboard. |
| Installs and conversions | As reported by Google Ads, where the account tracks them. |
| Campaign detail | Where the account exposes it, so spend can be broken out below the account level. |
Spend only
Conversion value reported by Google Ads is not imported as revenue. Revenue comes from your stores and monetization sources, so a conversion cannot be counted twice.
Troubleshooting
- No accounts listed: the signed-in Google account has no Google Ads access. Sign in with the manager account instead.
- Zero rows for an account that clearly has spend: check that the account is not a manager-only shell, and that the date range you are looking at is after the account started spending.
- Access revoked in Google: reconnect from the connection card — revoking in Google's security settings breaks the token, and we cannot restore it from our side.