Publisher workflow
How to Use AdRevFlow: A Tour of Every Page
The setup guide covers creating an account and connecting platforms. This article picks up from there: what each screen inside AdRevFlow is for, when to open it, and how to read what it tells you. None of it takes long. The whole loop fits into a minute a day plus one weekly review.
Published 4 min read
Dashboard: the 30-second check
This is the first screen after sign-in and the only one worth opening daily. It answers three questions at a glance: how much the selected period earned, how that compares with the previous period, and which platform earned it. Connection problems and stale feeds are announced at the top before you read a single number.
- Total revenue with the change versus the previous period.
- Per-platform cards with each platform's share.
- A revenue trend chart and the most recent daily rows.
- Top sites for the selected range.
Revenue: the daily table
When the dashboard shows a move, the Revenue page tells you exactly which day it happened. Rows are stored per platform per day, so you can see whether a drop came from one platform or both, and whether it lasted one day or started a trend. Date ranges follow your plan: the last 7 days on Free, longer and custom ranges on Pro.
AdSense and Adsterra: the platform pages
Each platform gets its own page because each platform has its own metric language. The AdSense page is organized around Page RPM and page views; the Adsterra page around CPM and impressions, with placements where Adsterra provides them. Open these when one platform moved and the total alone does not explain why. Site, ad unit, and country breakdowns live here.
Reports: longer views and bookkeeping
Reports is where period-level questions go: daily, per-site, per-country, and per-platform views over longer ranges. The Excel export writes exactly the stored rows you see on screen, so the file you archive matches the dashboard you checked. Reports is a Pro feature, and the page says so plainly if you open it on Free.
Settings: connections, sync, and account
- Connections: connect or disconnect platforms and read each connection's status and last sync time.
- Data sync: the automatic schedule for your plan and the state of the full-history import.
- Account: your plan and billing. When checkout runs against the Creem sandbox, a Test mode badge appears next to the plan name.
What Sync Now actually does
Sync Now pulls the latest reports from every connected platform immediately instead of waiting for the next scheduled run. One run per minute is allowed, because platform APIs are quota-limited; if you click again too soon, the button tells you how many seconds to wait. When a run finishes, the button reports the outcome honestly, including a platform error or a rate limit, instead of claiming success.
One expectation to set: Sync Now cannot create data the platform does not have. If a connected account has no earnings in the period, the sync succeeds and stores nothing, and a notice on the dashboard explains that the platform returned no data. That is a property of the account, not a broken sync.
Reading numbers without fooling yourself
- Check the last sync time before reacting to any total.
- Treat the last two or three days as provisional; platforms revise recent estimates.
- Never compare AdSense Page RPM with Adsterra CPM directly; the denominators differ.
- Free covers the most recent 7 days. Upgrade when you actually need older history, not before.
Frequently asked questions
- How often should I open AdRevFlow?
- Thirty seconds on the Dashboard daily is enough for most publishers. Add the Revenue or platform pages when something moved, and keep a fixed weekly slot for the deeper review.
- Why does Sync Now sometimes tell me to wait?
- Manual syncs are limited to one run per minute to protect platform API quotas. The scheduled sync keeps running on its own either way.
- Where is my older data?
- Free covers the most recent 7 days. Pro imports the available history progressively after upgrade; AdSense provides up to three years through its reporting API, and the import walks backwards until it has it all.