Also known as: Revenue Per Thousand Impressions, Revenue Per Thousand, Page RPM
Revenue Per Mille (RPM) is the estimated revenue a publisher or affiliate earns for every 1,000 impressions of an ad unit, page, or video. It is a yield metric: it tells you how efficiently your traffic converts into money, expressed on a per-thousand-views basis so campaigns of different sizes can be compared fairly.
RPM rolls every revenue source on a placement into one number. For a Forex review blog that means broker CPA and RevShare commissions, plus any display network income (Google AdSense, Ezoic), divided by total impressions and multiplied by 1,000. Because it normalises against volume, RPM lets you rank a 5,000-view comparison page against a 500,000-view homepage on equal footing.
The arithmetic is direct. If a page earns $1,500 from 50,000 monthly page views, its RPM is ($1,500 / 50,000) × 1,000 = $30. In finance verticals RPMs run far above general content: a general lifestyle site might see a $5–$15 page RPM, while a well-optimised Forex or CFD affiliate page can clear $40–$120 because a single referred trader can be worth $250–$1,200 in CPA.
RPM is a diagnostic, not a lever you pull directly. You raise it by improving the inputs — placement, relevance, offer payout, and conversion rate — then watch RPM confirm whether those changes actually added yield per thousand views.
RPM aggregates all revenue attributed to a set of impressions over a period, then scales it to a per-1,000 basis. Analytics and ad platforms compute it automatically: Google AdSense reports "Page RPM" and "Impression RPM", while affiliate dashboards let you derive it by dividing commission revenue by the sessions or impressions on that placement.
The key is defining the impression denominator consistently. Page RPM uses page views; impression RPM uses individual ad-slot views; a single page can carry several ad impressions. Mixing these denominators is the most common way to misread the metric, so pick one basis and hold it constant across the pages you compare.
Decide whether you are measuring page RPM (per page view) or ad-impression RPM (per ad slot). Keep it consistent across every placement you compare.
Sum all income tied to those impressions over a fixed window: broker CPA, RevShare, hybrid commissions, and any display network earnings.
Divide total revenue by total impressions, then multiply by 1,000 to get revenue per thousand views.
Break RPM down by page, device, geo, and traffic source to find which segments yield the most per thousand views.
Improve placement, offer payout, and on-page conversion, then re-measure to confirm the change lifted RPM rather than just traffic.
Why it matters for partnership: RPM tells an IB which pages, traffic sources, and offers actually monetise, so budget and content effort flow to the highest-yield placements. It exposes when swapping a display ad for a direct broker CPA banner lifts earnings per thousand views.
A Forex education blog gets 80,000 monthly page views. Its broker-comparison pages earn $2,800 in Exness and IC Markets CPA commissions, and its lower-intent news pages earn $600 from AdSense. Blended page RPM is ($3,400 / 80,000) × 1,000 = $42.50. Segmenting reveals the comparison pages run at a $95 RPM while news pages sit near $9 — so the affiliate shifts internal links to push more traffic into the high-RPM comparison funnel.
| Metric | Whose view | Represents |
|---|---|---|
| RPM | Publisher / affiliate | Revenue earned per 1,000 impressions |
| CPM | Advertiser / buyer | Cost paid per 1,000 impressions |
| eCPM | Publisher | Effective RPM blended across all monetisation sources |
Segment RPM by page and traffic source before optimising — lifting the RPM of your top three comparison pages beats tweaking site-wide ad density.
Chasing RPM by stacking more ad units degrades page experience and trust, which cuts broker registrations and can lower your total earnings even as the RPM figure rises.
No. CPM is what an advertiser pays for 1,000 impressions; RPM is what the publisher or affiliate earns from those impressions. They can differ sharply after the network's revenue share.
It varies by traffic intent, but well-optimised broker-comparison pages often run $40–$120+ page RPM, far above general-content sites, because a single converted trader can be worth hundreds in CPA.
Divide total revenue for a placement by its total impressions, then multiply by 1,000. Keep the impression basis consistent across the pages you compare.
Page RPM divides revenue by page views; impression RPM divides by individual ad-slot views. One page can hold several ad impressions, so the two numbers are not interchangeable.
Yes. A blended or effective RPM should roll in broker CPA and RevShare income alongside any display earnings to reflect the true yield of your traffic.
Extra ad units can lift raw impressions while hurting user experience and conversions, so revenue may not keep pace — dividing similar revenue over more impressions pulls RPM down.