Troubleshooting
Why Your Ad Revenue Dashboard Stopped Updating (and How to Fix It)
You open your dashboard and the newest row is three days old. Is the money still coming in? Is the problem the platform, or the pipeline between the platform and your screen? Work through the checks below in order.
Published 3 min read
First, decide which side is stale
Open the platform's own dashboard (adsense.com or publishers.adsterra.com). If the platform itself shows no new earnings, the issue is your traffic or ads, not your analytics. If the platform shows fresh numbers while your dashboard does not, the pipeline between them is stale.
The five causes behind most stale pipelines
| Symptom | Likely cause | Fix |
|---|---|---|
| No platform updates at all | The scheduled sync stopped; serverless cron only runs where it is deployed | Confirm the cron route responds in production and is triggered on schedule |
| One platform stale, the other fine | That platform's credential expired or was revoked | Reconnect AdSense; for a replacement Adsterra token, export first and disconnect the old connection |
| AdSense goes stale every week or two | The Google OAuth app is still in Testing mode, which expires refresh tokens after seven days | Publish the consent screen for verification, or reconnect weekly until verified |
| Everything stops at the same time each day | Syncing too frequently exhausted the platform API quota | Reduce sync frequency and let the quota window reset |
| Numbers stop at one specific past date | A transient platform outage was treated as fatal and the connection stopped retrying | Trigger a manual sync; retryable errors should recover on their own within about an hour |
Reporting lag is not a bug
Both platforms publish intraday estimates with a delay. Adsterra statistics refresh at intervals of roughly ten minutes to half an hour, and AdSense intraday data can trail real time by a few hours, with the closing hours of a day still moving until the day closes in its billing time zone. A dashboard that is two hours behind is healthy. A dashboard that is two days behind is not.
How AdRevFlow shows which case you are in
- Syncing: the connection is healthy and waiting for its next scheduled run. Free plans sync daily, Pro plans hourly.
- Needs reconnect: the platform rejected your credential. Stored history stays readable while you decide what to do; replacing an Adsterra token requires a clean disconnect.
- A stale-data notice: primary pages warn when the latest successful sync is later than the plan's schedule should allow.
If AdSense says reconnect, authorize the same account again and its stored rows remain in place. Adsterra does not expose a stable account id, so AdRevFlow will not put a different token on top of existing history. Export anything you need, disconnect the old Adsterra connection, then connect the replacement token cleanly.
Frequently asked questions
- Does reconnecting delete my history?
- Reauthorizing the same AdSense account keeps its history. Replacing an Adsterra token requires an explicit disconnect first because the platform provides no account id; that disconnect removes the old Adsterra history to prevent two publisher accounts from being mixed.
- How fresh should the data be?
- Free plans sync once a day and Pro plans once an hour, on top of each platform's own reporting lag, which can run to a few hours.
- Why does AdSense always lag a few hours?
- Google publishes intraday estimates before the day is finalized. The trailing hours keep being revised until the day closes in AdSense's billing time zone.