Answers for developers, publishers and site owners on monetizing and distributing web games.
337 posts
Place an in-page video player on the page around the game, not inside it: beside or below the game frame, visible without scrolling and never over game controls. It plays muted by default, and on mobile it usually goes below the game or in a sticky slot. It runs alongside gameplay, so unlike interstitials and rewarded ads it needs no break points.
Compare retention (D1, D7), session length and cumulative revenue per user between a group seeing your current ad load and a group with fewer or no interstitials, over at least two weeks. If retention drops more than a few points while session RPM barely moves, the ad load is too aggressive for that placement or geo.
ARPDAU is a day's revenue divided by that day's active users. ARPDAU usually includes all revenue (ads and in-game purchases) per daily active user; ad-only ARPDAU is a common sub-metric for ad-monetized web games. For ads it equals ad requests per user per day ร fill rate ร eCPM / 1000, and there is no single benchmark because each factor varies by geo, format and device.
Revenue per 1,000 sessions (session RPM) = ad requests per session x fill rate x eCPM. There is no single figure for game portals: full-screen formats usually earn several times more per impression than banners, and Tier-1 traffic several times more than the rest. Model it per geo, device and format with your own numbers rather than one borrowed benchmark.
No, if the SDK loads ads asynchronously with events for ready, reward and no-fill, instead of blocking the render loop while it waits for a response. Playgama Ad's window.pgAds uses this pattern; Unity WebGL needs a .jslib bridge to call it, and Godot uses its JavaScript singleton.
Yes. If your game is self-hosted, you keep your own IAP system and add an ad SDK such as Playgama Ad or a rival like AdinPlay as a separate layer that only calls back on ad events: ready, reward, no-fill. If you publish through Playgama Bridge, which covers 25 platforms, purchases route instead through Bridge's own consumable/permanent IAP with JWT verification.
There is no fixed hours-to-revenue number: what determines speed is how many placements you wire up and how much testing you run before launch. The path is the same across Playgama Ad, Google AdSense H5 Games Ads, and portal-native SDKs like Poki's: add the SDK, connect placements, test on a traffic segment, then go live.
It depends less on your judgement than on whose deal you sign: with Poki, web exclusivity is the default - its preferred deal runs five years and the alternative is a flat fee with no revenue share - while CrazyGames pays extra for launch exclusivity but doesn't require it. Everywhere else on this list, including Playgama, publishing is non-exclusive, so the question is whether one portal's promotion is worth giving up every other channel.
GameDistribution publishes an exact figure in its developer agreement - 33% of net revenue, with a โฌ100 payout threshold - while Poki publishes deal types rather than percentages and CrazyGames publishes its โฌ100 payout minimum but no split. Playgama publishes a ladder: 70% net to $1,000, then 80%, then 90% above $3,000 on partner-site revenue, and a fixed 50% on plays on playgama.com itself.
Poki, CrazyGames, GamePix, Famobi and itch.io are the usual named alternatives to GameDistribution, each with its own SDK and submission process. Playgama Bridge is an open-source (LGPL-3.0) SDK that integrates once and publishes to 25 platforms - including Poki, CrazyGames, GameDistribution, YouTube Playables and Discord - instead of building a separate integration for each.