Support and recovery
AdSense Sync Troubleshooting
Fix common PushRPM AdSense sync problems — no revenue data, the wrong Google account, missing per-page revenue, and stale figures.
Main intent
Give a clear recovery path for AdSense connection and sync issues.
Short answer
Most sync issues come from connecting the wrong Google account, a new account with little history, or AdSense not exposing page-level reporting. Reconnect with the owning account, give the first sync time, and check the measured-vs-estimated label.
No revenue data after connecting
If the dashboard still shows estimated RPM after you connect, the most common causes are a brand-new AdSense account with little history, or authorizing a Google account that does not own the AdSense property. PushRPM shows a soft 'no AdSense data yet' state rather than an error in these cases.
- Confirm the Google account you authorized owns the AdSense property.
- Give a new or low-history account time to accumulate reporting.
- Re-run a sync from Integrations after a day if data is still empty.
Connected the wrong Google account
If you picked the wrong account during the Google step, return to Integrations and reconnect AdSense, choosing the account that owns the reporting. The new authorization replaces the old one.
Per-page revenue is missing
Per-URL revenue is best-effort. AdSense does not expose page-level reporting for every site, and even when it does, it can lag the daily totals. Daily revenue often appears first, with per-page rows filling in over the following days. This is expected, not a failure.
Figures look stale
PushRPM syncs periodically rather than in real time, and AdSense reporting itself has a delay. A short lag between AdSense and the dashboard is normal. If figures have not moved in several days and a manual sync does not help, contact support with your site and the approximate dates.
Implementation checklist
- Verify the authorized Google account owns AdSense.
- Reconnect from Integrations if the account was wrong.
- Allow time for new accounts and per-page data to populate.
- Trigger a fresh sync and recheck Reports.
- Contact support if data stays empty or stale after a few days.
Common mistakes
- Assuming an empty state is a bug when the account is simply new.
- Expecting per-page revenue for every site — it is best-effort.
- Treating short reporting lag as a sync failure.
Example
A publisher connected a personal Gmail instead of the account that owns AdSense; reconnecting with the correct account let measured revenue flow within a day.
Use a related tool
Continue in PushRPM
Policy and platform references
FAQ
Why is my revenue still estimated after connecting?
Either the authorized Google account does not own AdSense, or the account has little reporting history. Reconnect with the owning account and allow time for data to accumulate.
Why don't I see per-page revenue?
Per-URL revenue is best-effort and depends on AdSense exposing page-level reporting. Daily totals usually appear first.
Sync seems slow — is something broken?
PushRPM syncs periodically and AdSense reporting has its own delay, so a short lag is normal. Contact support if data is stale for several days.
Related docs
Connect Your AdSense Account to PushRPM
Link your Google AdSense account to PushRPM with one click so the engine measures real RPM and revenue per page instead of estimates.
PushRPM Plugin Connection Troubleshooting
Troubleshoot PushRPM plugin connection issues, site mismatch, expired authorization, payment access, HTTPS, and diagnostics.
Reading the PushRPM Dashboard
Make sense of the PushRPM dashboard — the site scan score, the revenue leak detector, and before/after proof — and know what each number means.