What does each visit earn? Page RPM from your GA4 traffic
Revenue Analytics is the report in Fusion that joins your ad revenue with your Google Analytics 4 traffic. It shows RPM, your revenue per 1,000 page views, sessions or users, so you can see what each visit earns rather than only what each ad impression earns. Traffic filters leave out GA traffic that never saw your ads, such as visits through a syndication partner.
Page RPM, session RPM and user RPM, and how they're worked out
Every RPM view can show gross or net revenue. Page views, sessions and users come from Google Analytics 4; ad requests and unit loads come from the Fusion ad tag.
| Measure | How it's worked out | What it tells you | Traffic from |
|---|---|---|---|
| Page RPM | Revenue ÷ page views × 1,000 | What 1,000 page views earn. The best single measure of how well your pages monetise | GA4 |
| Session RPM | Revenue ÷ sessions × 1,000 | What 1,000 visits earn. Divide by 1,000 for revenue per session | GA4 |
| User RPM | Revenue ÷ users × 1,000 | What 1,000 readers earn, however often they visit | GA4 |
| Ad request RPM | Revenue ÷ ad requests × 1,000 | What each ad request earns, for comparison | Ad tag |
| Unit load RPM | Revenue ÷ ad unit loads × 1,000 | What each ad opportunity earns, for comparison | Ad tag |
From your GA4 property to RPM per visit
- 01Connect Google AnalyticsConnect GA4 under Integrations and map your property IDs. Organisation mapping matches each property to the right site by exact domain.
- 02Filter out traffic that never saw your adsExclude, for example, a syndication partner or news aggregator app by session source, medium, campaign or hostname. Preview the impact before you save.
- 03Read RPM per visitThe Overview tab shows RPM against each traffic metric, a daily RPM chart and an exportable table. Single views break down page views, users, sessions, ad requests and unit loads.
Leave out GA traffic that never saw your ads
Your GA4 property can record visits that happen somewhere else, such as articles read through a syndication partner or a news aggregator app. Those visits never load your ads, so they drag RPM down. Traffic filters exclude them from Fusion's figures without changing anything in GA.
- 01What you can filter onGA dimensions such as session source, medium, campaign or hostname, matched with Is, Contains or a regex. Paste a list of values at once.
- 02How matches workTraffic matching any filter is excluded, a filter matches if any of its values match, and matching ignores case.
- 03Preview firstThe Traffic Filter Impact Previewer shows page views, sessions and users before and after, the share excluded and the top matched traffic.
- 04When it takes effectTotals for custom date ranges change at once. Stored daily figures for the last 90 days update over the next few hours; older figures stay as they were.
Domain matching only. If you map a GA property to a single site, switch this on to count only that site's own domain (for example example.com and www.example.com) and leave out subdomains and staging sites. Organisation mapping already does this.
Where filters apply. Revenue Analytics and the traffic tiles in Diagnostics. A chip in the report header shows how many filters are active, and says "Traffic filters updating…" while stored figures catch up.
Older figures. Figures more than 90 days old keep the old settings. Ask your account manager if you need them updated.
Why users and sessions can differ from GA4
GA4 deduplicates users and sessions over long periods. Fusion keeps that deduplication wherever it fetches totals directly.
| Where you see it | How Fusion gets it | Compared with GA4 |
|---|---|---|
| Daily figures | Pulled from GA4 once a day | Match GA4 for that day |
| Charts grouped by week, month or quarter | The sum of the daily figures | Users and sessions can be higher than GA4, and RPM slightly lower, because a reader who visits on several days is counted once a day |
| Totals for a date range | Fetched from GA4 in real time | Match GA4's deduplicated totals |
Revenue Analytics and the reports next to it
Revenue Analytics is part of the Insights Hub in Fusion and shares its publisher and date filters, including Month-on-Month and Quarter-on-Quarter grouping.
| Report | Use it when | What you see |
|---|---|---|
| Revenue Analytics (this page) | You want to know what each visit or page view earns | RPM against GA4 page views, sessions and users |
| Revenue Insights | Revenue moved and you want to see which part moved | Revenue and eCPM by country, device, partner and six other dimensions |
| Revenue reporting | You need your own report, with your fields, filters and dates | Report Builder: any combination of fields, as a table or chart, or by API |
| Diagnostics | Analytics page views are higher than ad page impressions | Traffic Stats and Traffic Trend tiles, which use the same filtered GA data |
| Benchmarking | You want to know if your CPM is good for a publisher like you | CPM and fill against your cohort and the whole network |
Where publishers got to on Fusion
Results are for each publisher's whole Fusion set-up.
Page RPM, revenue per session and GA4: questions, answered
What is page RPM?
What is the difference between RPM and eCPM?
How do I calculate revenue per session?
Why are users and sessions higher in Fusion than in GA4?
How do I connect Google Analytics to Fusion?
How do I exclude syndicated or aggregator app traffic from RPM?
Do traffic filters change my data in Google Analytics?
Is RPM shown gross or net?
Which analytics platforms are supported?
Find out what your traffic should be earning.
Get a free Revenue Healthcheck: your consent set-up, ads.txt, tags and Core Web Vitals scored and benchmarked against similar publishers.