Connect Google AdMob Data to Revenue Sensor for Revenue Reporting
Authorise AdMob with a Google sign-in to import ad revenue across your own network and mediation.
Google AdMob connects with a Google sign-in. You sign in with a Google account that has AdMob publisher access, approve read-only access, and Revenue Sensor imports your ad earnings, including revenue mediated through other networks.
Before you begin
- A Google account with access to a fully set-up AdMob publisher account.
Connect the account
- 1
Start the connection
Integrations → Google AdMob → Connect in the Revenue Sensor console.
- 2
Sign in and approve
Google's consent screen opens in a popup. Approve the read-only AdMob access. The popup closes itself when it is done.
- 3
Let it sync
Your publisher accounts and apps are discovered automatically. The first sync loads recent days within minutes and then imports the rest of your history in the background.
What gets imported
| Field | Notes |
|---|---|
| Ad revenue | Estimated earnings, per app, country and day. This is your publisher share, after Google's revenue share. |
| Impressions | Used for the delivery view; eCPM is derived from revenue and impressions rather than stored. |
| Mediation | Revenue from the third-party ad sources AdMob mediates is included, not just AdMob's own network. |
A revenue source
AdMob is monetization revenue, sitting alongside your store income in the P&L. It carries no spend, and because its earnings are already your share, Payout is its only revenue basis.
Troubleshooting
- “AdMob couldn't authorize this account”: make sure the AdMob API is enabled for your Google project and that the account is a fully set-up AdMob publisher, then reconnect.
- Revenue looks low for a recent day: AdMob earnings are estimates that can still move for a few days. Every sync re-reads the last 14 days.