The question behind “do rewarded ads make money” is almost never about the format itself. It is about whether a studio should spend an afternoon integrating a rewarded video ads SDK instead of shipping a feature. That decision needs a number you can forecast, not a benchmark table copied from mobile app inventory. This page gives you the arithmetic, the deductions that eat into a quoted rate, and an honest read on when rewarded video is not worth your time.

Do rewarded ads make money on web games?

Rewarded video makes money on web games, and it is the highest-paying ad format most browser titles can run. On AppLixir’s web inventory, rewarded video delivers $4+ CPM, against roughly $0.50–$2 CPM for standard web display. That is a multiple, not a rounding difference, and it comes from a format players opt into rather than tolerate. The answer is conditional, though, and the conditions matter more than the rate. Rewarded ads revenue is meaningful for a web game with enough daily traffic to generate volume, a reward that players genuinely want, and a demand stack that fills requests on browser inventory. It is disappointing for a game with a few hundred daily players, a reward nobody values, or an ad setup that was designed for mobile apps and does not run in a browser at all. Same format, opposite outcome. The practical floor is traffic. AppLixir’s minimum publisher threshold is 5,000 daily active users, and that number exists because rewarded video is a volume business: the CPM is a rate per thousand impressions, so a game producing a few thousand impressions a month will see a revenue line too small to justify the integration, no matter how strong the rate.

What is rewarded ads revenue, and how is it calculated?

Rewarded ads revenue is the money a publisher earns from players who voluntarily watch a video ad in exchange for an in-game benefit — extra lives, a currency grant, a revive, a skin unlock, a hint. Unlike display or interstitial inventory, a rewarded impression only exists when a player chooses to create it, which is why the format commands higher CPMs and why its revenue is partly a design output rather than purely a traffic output. The calculation is simple enough to run on a napkin: Daily rewarded revenue = (rewarded impressions per DAU × CPM ÷ 1,000) × DAU Work it forward with AppLixir’s $4 CPM floor on web rewarded video. A game at 5,000 DAU where the average player watches two rewarded videos a day produces 10,000 impressions daily. At $4 CPM that is $40 a day, roughly $1,200 a month. Take the same game to 50,000 DAU and the line is about $12,000 a month. Keep the traffic flat and lift views per player from two to four — a second well-placed reward moment in the core loop — and the revenue doubles without the CPM moving at all. That is the part most teams miss. Two of the three inputs in the formula are under your control. You do not need a higher rate to earn more; you need more willing views per player, delivered without nagging. If you want the per-player version of this metric, ARPDAU is the standard way to express it, and our guide to ARPDAU and how to improve it covers the measurement discipline.

Why a quoted CPM is not the rewarded video revenue you keep

Any rewarded video CPM you read in a benchmark table is a gross, best-case rate. Four things happen between that quote and the number on your statement, and they compound. Name them and you can forecast; ignore them and you will plan around a figure that was never yours.

Geo mix

Benchmarks quote tier-1 rates because tier-1 advertisers pay most. Web games distributed across open portals tend to skew global, with a heavy tail of lower-rate regions. A blended audience earns a blended rate, and the spread between top and bottom geos is large enough to dominate every other variable in your model. [DATA NEEDED: AppLixir web rewarded CPM by geo tier, with reporting window.]

Opt-in rate

Rewarded video is opt-in by definition. A player who never taps “watch” generates no impression and no revenue. Opt-in is a function of reward value and prompt placement, which means it is a design metric sitting inside a revenue formula — and the one you can change fastest.

Fill rate

Not every ad request returns a paying ad. Fill depends on how much demand is competing for your specific geos and on the depth of the demand stack your SDK can reach. An unfilled request pays zero regardless of the CPM on the requests that do fill, so fill rate and CPM have to be read together.

Revenue split

If your game runs on a distribution platform, the ad revenue on that platform’s inventory is shared on that platform’s terms. That is a normal and often excellent trade for the traffic it brings. It does mean the headline rate and your take-home rate are different numbers, and that the same game can earn at two different effective rates depending on where a session happens. For the full rate-level breakdown — what the format pays, how eCPM is derived and what moves it — see how much rewarded video ads pay on web games and the companion piece on what counts as a good eCPM for web rewarded video.

Rewarded video CPM vs other web ad revenue sources

Rewarded video earns more per impression than any other format a browser game can run, and it is the only one players actively choose. The comparison below covers what is actually available to a web or HTML5 game, which is a shorter list than most monetization articles suggest.

Revenue source	Serves browser and HTML5 games?	Web rate context
AppLixir rewarded video	Yes — built for web, HTML5 and WebGL	$4+ CPM delivered on web rewarded inventory
Standard web display and banners	Yes	Roughly $0.50–$2 CPM
Interstitial video on web	Yes	Between display and rewarded; non-opt-in, so retention cost is higher
Unity Ads, AdMob, AppLovin, ironSource rewarded	No — these are mobile app SDKs	Not applicable to browser inventory
Portal distribution (Poki, CrazyGames and similar)	Yes, on their own properties	Set by each platform; complementary to your own-domain revenue
In-app purchases	Yes	Monetizes the paying minority; runs alongside rewarded, not against it

The practical takeaway: if a web game is running display only, the gap between $0.50–$2 and $4+ is the size of the opportunity, and it is available on the same traffic you already have. The rewarded vs interstitial comparison goes into what each format costs you in session length and retention.

Where web rewarded ads revenue actually comes from

Web rewarded ads revenue comes from advertisers buying browser-based video inventory through demand sources that bid on it. The reason this matters is structural: the largest rewarded networks by spend — Unity Ads, AdMob, AppLovin, ironSource — are built around mobile app SDKs and do not serve browser games. A studio that assumes its mobile monetization partner will cover its WebGL build will find there is nothing to integrate. We walk through exactly where the attempt breaks down in Unity rewarded ads and AdMob on WebGL. Distribution platforms are a different thing entirely. Poki, CrazyGames and similar portals bring audiences to your game and monetize the sessions that happen on their sites. That is distribution, and it is additive. AppLixir sits alongside it: the portal monetizes portal traffic; AppLixir monetizes the sessions on your own domain, your embeds, your Telegram mini app, your itch page. Most studios earning meaningfully from web run both, because they cover different traffic. The compliance layer is part of the revenue picture rather than a separate chore. AppLixir ships TCF 2.3 and GDPR compliance built in via Didomi, which means European sessions arrive with a valid consent signal. A clean consent string is what lets advertisers bid at all on those impressions; a missing one quietly suppresses both fill and rate.

The three levers that move rewarded video revenue

Rewarded video revenue moves on three levers: how many players opt in, how often they can, and how reliably requests fill. Studios tend to over-focus on the rate, which is the lever they control least.

Reward value

A reward has to be worth sitting through a video. Continues after a loss, a doubled run reward, a timed boost, a currency top-up at the exact moment the player wants currency — these convert because the player already feels the need. Generic “watch for coins” buttons parked on a menu screen convert poorly and drag your impressions-per-DAU toward zero. Placement is the same lever viewed from the other side. The prompt has to appear where intent already exists, not where there was room in the UI.

Frequency without fatigue

Large studios raise rewarded ads revenue by adding reward moments, not by making one moment more aggressive. Two or three distinct, genuinely optional offers across a session — a revive, a daily bonus multiplier, an end-of-run doubler — raise views per player while keeping the format voluntary. Because nothing is forced, retention stays intact, which is the whole reason enterprise teams accept rewarded video where they reject interstitials.

Demand depth and consent quality

Fill and rate both depend on how many buyers can see your impression and whether they are allowed to bid on it. That is a function of your ad partner’s demand stack and your consent implementation, not of your game. It is also the part you solve once at integration and then leave alone.

When rewarded video does not pay on web

Rewarded video is not universally worth integrating, and pretending otherwise wastes your afternoon. There are four situations where the revenue will not justify the work.

• • Traffic below the threshold. Under roughly 5,000 DAU, impression volume is too thin for a per-thousand rate to produce a line item that matters. Grow the audience first; the ad stack will still be there.

• • No natural reward moment. Some games — narrative pieces, tools, linear experiences without a fail state or an economy — have nowhere to put a reward that players want. Forcing one produces low opt-in and an awkward UI.

• • The reward breaks the game. If watching a video trivializes progression, you will see opt-in spike and retention fall. The reward has to help without removing the reason to keep playing.

• • An audience concentrated in low-rate regions with no monetization alternative. Rewarded video will still outperform display, but the blended rate will sit well below benchmark figures, and your planning should reflect that rather than the headline.

Three of those four are design and distribution problems, not ad problems. That is the argument of this page: web rewarded ads revenue is mostly won or lost before any CPM is quoted.

What the integration actually costs you

Adding a rewarded video ad to a web game is a front-end integration, not an app build. You load the AppLixir SDK, configure your zone, call the ad at the reward moment, and grant the reward in the completion callback. There is no store submission, no native build, no review cycle — which is the reason the format is cheap to test on web relative to what it pays. Our HTML5 rewarded video SDK guide has the step-by-step version with the callback handling. Budget your time for the design decisions rather than the code: which moments get a reward prompt, what each reward is worth in your economy, and how the offer reads to a player who has just lost a run. Those choices determine your impressions per DAU, and impressions per DAU determines your revenue. If you are also running in-app purchases, the two streams are complementary rather than competing — rewarded video monetizes the large majority of players who will never buy anything, and the hybrid monetization playbook covers how to structure both without one undercutting the other. [DATA NEEDED: AppLixir-sourced figure on IAP conversion among rewarded-ad viewers vs non-viewers.]

FAQ

What is a typical rewarded video CPM on web games?

AppLixir delivers $4+ CPM on web rewarded video inventory, compared with roughly $0.50–$2 CPM for typical web display. Your own effective rate will depend on your geo mix, your fill rate and any platform revenue share that applies to the traffic in question. Treat $4+ as the web rewarded baseline rather than a ceiling, and measure your own blended rate in reporting before forecasting from it.

Do rewarded video ads cannibalize in-app purchase revenue?

Rewarded video and in-app purchases generally behave as complementary revenue streams rather than competing ones. Rewarded video monetizes the large share of players who will never make a purchase, while the reward moment familiarizes non-payers with the in-game economy. The risk to watch is reward value: if a free reward fully replaces something you sell, you will see substitution, so keep rewarded grants useful but bounded.

Do Unity Ads or AdMob work for WebGL and browser games?

No. Unity Ads, AdMob, AppLovin and ironSource are mobile app SDKs and do not serve browser-based inventory, including Unity WebGL builds running in a browser. A web game needs a rewarded video ads SDK built for the browser, which is what AppLixir provides for HTML5, WebGL and browser-based titles. If you ship to both mobile and web, you will run different ad partners on each.

Are rewarded video ads GDPR compliant for players in Europe?

They can be, provided consent is collected and passed correctly to demand partners. AppLixir includes TCF 2.3 and GDPR compliance built in via Didomi, so European sessions carry a valid consent signal without the publisher building a CMP integration. That matters commercially as well as legally: advertisers bid on impressions with a clean consent string and skip ones without.