Publisher workflow
A 15-Minute Weekly Revenue Review for Publishers
Checking revenue every day and learning nothing from it is common. The numbers move, you feel briefly good or bad, and nothing changes. A fixed weekly routine turns that anxiety into decisions: same steps, same order, fifteen minutes.
Published 3 min read
Step 1: Confirm the data is current (1 minute)
Before any number earns your attention, check the connection status. A feed that stopped syncing on Tuesday makes the rest of the week look like a collapse, and no amount of chart reading will tell you that. AdRevFlow puts sync warnings at the top of the dashboard for exactly this reason: freshness first, totals second.
Step 2: Size the change against its normal range (2 minutes)
Compare the week with the previous one, but judge the move against your own normal range, not against zero. Most sites swing within a familiar band from week to week. A move inside the band is weather, not climate, and the correct action is none.
Step 3: Find which platform moved (3 minutes)
A combined total hides the source. Check the per-platform cards: did AdSense move, Adsterra, or both? One platform moving alone points to a platform-side cause, such as fill rate, a layout change on a site that runs only that platform, or an advertiser-side swing. Both moving together usually means traffic itself changed.
Step 4: Find which site caused it (5 minutes)
Platform moves almost always trace to one or two sites. Open the top-sites table or the platform page, sort by revenue, and compare each site with its own previous weeks. When a single site explains most of the change, you have found your subject; everything else that week is context.
Step 5: Write down one action (4 minutes)
The review ends with a decision, not a feeling. One sentence is enough: what you will change, on which site, and which number will tell you next week whether it worked.
- Test a layout or placement change on the site that moved.
- Check that site for a technical cause: slow pages, broken ad code, a traffic source that vanished.
- Deliberately do nothing when the move is inside the normal range, and write that choice down too.
The monthly close
Once a month, after the platforms finalize earnings, do a slower pass. Record the finalized totals for your books, export the rows you need, and compare the month with the previous one. AdSense finalizes early in the following month, so closing on the first compares a finished month with a still-open one. Give it a few days.
Mistakes this routine prevents
- Reacting to estimates as if they were finalized payouts.
- Comparing mismatched date ranges, or mismatched metrics like Page RPM and CPM.
- Trusting a dashboard without checking when it last synced.
- Changing five things after one noisy week, which makes the next week unreadable.
Frequently asked questions
- Is a daily check still useful?
- Yes, but only for freshness, not decisions. The daily glance answers 'is the data flowing?'. The weekly review answers 'what changed, and what will I do about it?'. Keep the two separate.
- What if both platforms dropped at once?
- That usually points to traffic rather than monetization: a lost source, a seasonal dip, or a technical issue on a site. Check visits before touching ad settings.
- How big a move deserves action?
- One outside your sites' normal weekly range that persists for more than a few days. Single-day spikes and dips are usually estimate noise, and both platforms revise recent days.