Earnings by Ad Network
Enter your own historical publisher rates for the networks you have measured. Compare the same dates, visitor countries, devices and ad formats, with the same revenue and traffic definitions. No network rate is supplied by AdNetworkRank.
Uses the website calculator’s current monthly traffic, mode and currency. Enter Page RPM for pageviews or publisher net eCPM for ad impressions. Amounts are input scenarios, not network quotes or expected benchmarks.
| Network | Your measured rate | Monthly input scenario |
|---|---|---|
| Adsterra | Selected currency per 1,000 pageviews | Enter your own measured rate. |
| Monetag | Selected currency per 1,000 pageviews | Enter your own measured rate. |
| PopAds | Selected currency per 1,000 pageviews | Enter your own measured rate. |
| AdMaven | Selected currency per 1,000 pageviews | Enter your own measured rate. |
Blank means no measured rate was supplied; 0 is a valid zero-revenue assumption. Switching between Page RPM and impression eCPM clears the rates so unlike units are not reused. Reset clears them too. Use “Copy scenario link” in the website calculator to share valid rates with its current inputs. Nothing is saved to local storage.
How Ad Revenue Is Calculated
Know what your inputs mean
- Page RPM and impression eCPM use different denominators. A pageview can generate more than one ad impression, or none.
- A historical Page RPM already reflects the ad delivery, fill, placement, and traffic mix in that sample. Do not multiply it by ad slots, fill rate, or viewability again.
- Use a publisher-side revenue rate. Advertiser CPM describes advertiser cost and may include revenue that the publisher does not receive.
- Viewability is not a universal revenue multiplier. A viewable-impression pricing model needs a rate defined per viewable impression; Active View viewability itself is measured against measurable impressions.
- Country, device, season, consent, ad format, and network rules can change the rate. This tool compares input assumptions; it does not establish a network’s expected CPM.
From Your Report to a Reproducible Revenue Scenario
Choose a revenue scope before copying numbers. Match dates, currency, countries, devices, ad formats and content or app inventory within each historical sample. The historical sample can cover a different period from the monthly scenario, but its earnings and denominator must cover the same dates. Report labels can vary; the table maps definitions, not a guaranteed dashboard click path.
Pageviews + publisher Page RPM: Report Fields to Calculator Inputs
Revenue scope: Publisher website advertising earnings and matching pageviews.
| Report field or calculation | Calculator input | Unit and scope rule |
|---|---|---|
| Pageviews from the matching publisher report | Monthly pageviews | Use a monthly pageview total, not visitors, sessions or ad requests. |
| Your separately supported rate assumption or measured historical sample | Low scenario rate | Use per 1,000 pageviews. This is an input scenario, not a reported confidence bound. The historical-rate helper sets all three rates to one measured rate. |
| Matching reported publisher/creator rate, or earnings ÷ matching denominator × 1,000 | Base scenario rate | Use per 1,000 pageviews. Keep the revenue scope below; do not deduct a platform share twice. |
| Your separately supported rate assumption or measured historical sample | High scenario rate | Use per 1,000 pageviews. This is an input scenario, not a reported confidence bound. The historical-rate helper sets all three rates to one measured rate. |
Definition sources: Google AdSense: revenue per thousand impressions (RPM).
Recalculate an Example: Synthetic Data, Not Market Rates
The invented historical sample has 80 USD of earnings in the scope above and 20000 matching pageviews. Historical rate = 80 ÷ 20000 × 1,000 = 4 USD per 1,000 pageviews. No platform share is deducted a second time.
For a separate monthly scenario, enter monthly pageviews: 50000. Set low, base and high rates to 4 to represent this one historical sample.
Scenario check: 50000 pageviews × 4 ÷ 1,000 = 200 USD for the month. The three scenario amounts are equal because their rates are equal. These numbers demonstrate the formula; they do not estimate a market payout.
Ad impressions + publisher net eCPM: Report Fields to Calculator Inputs
Revenue scope: Publisher net advertising earnings and delivered ad impressions.
| Report field or calculation | Calculator input | Unit and scope rule |
|---|---|---|
| Delivered ad impressions | Monthly ad impressions | Use the monthly impression total from the same revenue scope. Requests are not delivered impressions. |
| Your separately supported rate assumption or measured historical sample | Low scenario rate | Use per 1,000 ad impressions. This is an input scenario, not a reported confidence bound. The historical-rate helper sets all three rates to one measured rate. |
| Matching reported publisher/creator rate, or earnings ÷ matching denominator × 1,000 | Base scenario rate | Use per 1,000 ad impressions. Keep the revenue scope below; do not deduct a platform share twice. |
| Your separately supported rate assumption or measured historical sample | High scenario rate | Use per 1,000 ad impressions. This is an input scenario, not a reported confidence bound. The historical-rate helper sets all three rates to one measured rate. |
Definition sources: Google AdSense: revenue per thousand impressions (RPM).
Recalculate an Example: Synthetic Data, Not Market Rates
The invented historical sample has 90 USD of earnings in the scope above and 30000 matching ad impressions. Historical rate = 90 ÷ 30000 × 1,000 = 3 USD per 1,000 ad impressions. No platform share is deducted a second time.
For a separate monthly scenario, enter monthly ad impressions: 60000. Set low, base and high rates to 3 to represent this one historical sample.
Scenario check: 60000 ad impressions × 3 ÷ 1,000 = 180 USD for the month. The three scenario amounts are equal because their rates are equal. These numbers demonstrate the formula; they do not estimate a market payout.
Derive and Apply Your Historical Rate
Use earnings and the matching denominator from one report sample. Enter the earnings in the main calculator’s selected currency; changing its currency does not convert money. Exclude advertiser spending and referral commissions. For estimated earnings, keep that estimated scope consistent rather than mixing it with a finalized payment.
Current mode: Pageviews + publisher Page RPM. Scope: Publisher website advertising earnings and matching pageviews. Currency: USD. Changing mode or currency clears historical inputs.
Keep a Comparable Test Worksheet
Download the Revenue Test Worksheet (CSV). Add one row for each comparable report segment. Record the dates, currency, geography, device, format, revenue scope and denominator definition with the totals. Keep app-level and ad-source scopes separate, and compare rates only after reconciling their definitions.
Pageviews, Ad Impressions and Your Traffic Mix
A website revenue calculator needs a traffic count and a rate that use the same denominator. Page RPM answers how much the publisher earned per 1,000 pageviews. An impression rate answers how much the publisher earned per 1,000 delivered ad impressions. One pageview can contain several ads, but that does not make the two rates interchangeable.
Choose the report you can reconcile
| Available report | Use in this calculator | Keep outside this calculation |
|---|---|---|
| Pageviews and publisher Page RPM | Page RPM mode with pageviews for the same period | An extra multiplier for ad slots, fill or viewability |
| Delivered impressions and publisher net eCPM | Impression mode with the matching delivered ad impressions | Unfilled requests and advertiser-side buying cost |
| Visitors, sessions or ad requests only | Establish matching pageviews or delivered impressions first | An assumed one-to-one conversion into ad impressions |
Historical Page RPM already summarizes the sampled ad layout and delivery. Entering three ad slots does not justify multiplying that RPM by three. If you want to model a new layout, measure its delivered impressions or choose an explicit new Page RPM assumption. The same rule prevents a second fill-rate or viewability adjustment from being applied to revenue that already reflects those effects.
Use country and industry as report segments
Country, topic, device and format help you choose a comparable historical sample. They do not provide a verified revenue rate by themselves. For a mixed audience, calculate each segment with its own volume and matching rate, then add the revenues. Derive an overall rate from total revenue divided by total matching volume; do not take an unweighted average of country RPMs.
There is no automatic country or industry benchmark in this tool. Without your own history, low, base and high rates are assumptions you choose. The network table uses that same principle: it compares the rates you enter, without presenting them as provider quotes or market averages.
After checking the arithmetic, use the publisher network shortlist and the website ad-network directory to investigate traffic eligibility, allowed formats and payment terms. A provider still needs a controlled test on your inventory before an earnings comparison can support a switching decision.
Official definitions and sources
- Google AdSense: revenue per thousand impressions (RPM)
- Google AdSense: Active View reporting definitions
- Google AdSense: Active View CPM
Frequently Asked Questions
How do I calculate website ad revenue?
Multiply pageviews by publisher Page RPM and divide by 1,000. If your report gives ad impressions instead, multiply those impressions by the publisher net impression rate and divide by 1,000.
Should I multiply Page RPM by the number of ads on a page?
No. Page RPM already expresses the publisher earnings per 1,000 pageviews in the source sample. Adding an ad-slot multiplier would count the sampled ad delivery twice.
Can I use visitors instead of pageviews?
Not directly. Visitors and pageviews are different counts. You need pageviews, or an explicit assumption about pageviews per visitor, before using a Page RPM model.
Are the example rates average network CPMs?
No. Every default is an editable arithmetic example. The tool does not assign market-average rates to networks or guarantee a payout.
Are low and high scenarios a prediction interval?
No. They are separate calculations using the rates you enter. They do not represent statistical confidence or measured platform volatility.
How does a website revenue calculator handle different visitor countries?
Use the Page RPM or impression rate measured for each country and calculate each segment separately. Add the segment revenues afterward. Choosing a country alone cannot establish a rate, and this tool does not apply an unsupported country multiplier.
Does the website topic determine the RPM I should enter?
The topic can help define a comparable report segment, but it does not supply a verified revenue rate. Use earnings and traffic from the same pages, audience and period. Do not substitute a general industry rate without evidence that its denominator and scope match.
What if I do not have any historical advertising revenue?
Enter an explicit assumption and treat the result as a planning scenario. The editable examples show the arithmetic. They do not replace a network quote, a measured benchmark or a limited test on your own inventory.
Can I compare Adsterra, Monetag, PopAds and AdMaven with this calculator?
The network table accepts your own rates for each provider. Keep dates, country, format, currency and the selected denominator comparable. Empty rates remain uncalculated. The results describe the inputs you supply, rather than expected network payouts.
Should I enter ad requests or delivered ad impressions?
The impression mode needs delivered ad impressions. Requests can go unfilled or fail to become a displayed ad. If only request counts are available, establish the corresponding delivered impressions before applying a rate defined per impression.
How should I combine rates from several pages or countries?
Calculate revenue separately and add it, or divide the combined revenue by the combined matching volume and multiply by 1,000. A simple average of segment rates is incorrect when their traffic volumes differ.
What do the daily and annual outputs mean?
The daily output divides the monthly scenario by 30. The annual output multiplies it by 12. Both keep the same input rate and traffic assumption; they do not account for calendar length, seasonality or growth.