Plain Reckoner
EN

Per thousand views

Is what you earn per thousand views any good?

Sources and limits
1.17 billion pageviews and $6.84m of verified ad revenue, from historical business records checked by a broker; full study scope is in the method Read the data and method ↗ How to use the tools
Free analytics workspaceFree to use · No signup
Compare two periods

Your figures

See results ↓

Your result

Edit figures ↑

Worked out for 50,000 views a month and $760 a month from ads — the example figure, until you put your own in.

Add your figures to calculate your result.

Why did ad revenue change?

Compare traffic and earnings across two periods. Nothing is uploaded.

Use USD, complete days and the same traffic unit and timezone.

CSV format and limits

Use exactly date,traffic,revenue_usd: one row per complete day, no missing dates, USD only. Maximum 100 KB and 366 days. Use the template, or select columns from a provider export below. Negative adjustments need reconciliation.

Have a larger report? Contact us for a free manual review. Please do not send sensitive files before we agree on what is needed.

Download template CSV

Earlier period
Import a daily CSV locally

Files stay in this browser. Preview the totals before applying them.

Later period
Import a daily CSV locally

Files stay in this browser. Preview the totals before applying them.

Worked example: 50,000 pageviews and $750 over 30 days → 40,000 pageviews and $480 over 30 days.

Earlier RPM
$15.00 /1,000 pageviews
Later RPM
$12.00 /1,000 pageviews
Earlier traffic per day
1666.7 pageviews/day
Later traffic per day
1333.3 pageviews/day
Daily traffic change
-20%
Earlier revenue per day
$25.00
Later revenue per day
$16.00
Daily revenue change
-$9.00 (-36%)
RPM change
-20%
Traffic component of daily change
-$4.50 /day
RPM component of daily change
-$4.50 /day
Method and what to check next

The unrounded components add to the daily revenue change. Displayed amounts are rounded to cents; the CSV keeps calculation precision. They split the interaction equally using midpoint arithmetic; they do not identify what caused either change. Different period lengths are normalized per day. Session results are not compared with the page-RPM benchmark above.

Compare two reporting periods to separate traffic and RPM changes. The result uses your figures, with no account or upload. Period figures are separate from the benchmark above and are not kept between visits. Switching language preserves the figures in this tab.

Use USD and the same revenue definition, traffic unit and reporting timezone in both periods. Use complete days. Monetized sessions and total sessions are different denominators.

RPM = revenue ÷ traffic × 1,000. Traffic component = change in traffic/day × average RPM ÷ 1,000. RPM component = change in RPM × average traffic/day ÷ 1,000. This symmetric split gives the same components with opposite signs if the periods are reversed.

If traffic fell, check acquisition sources and complete reporting dates. If RPM fell, compare like-for-like traffic geography, device mix, consent and ad delivery in your network dashboard. These figures alone cannot diagnose a network fault, a Google update or AI traffic loss.

Start with Journey’s reporting window, session versus page RPM and monetized RPM denominators. The basic definition follows Google’s RPM formula.