A code-level information to the combination patterns that maintain gamers — and income — intact.
| TL;DR
A clear rewarded video integration hits 5 marks: express opt-in, a reward gated on a verified completion sign, a sleek no-fill fallback, frequency and placement self-discipline, and consent-aware loading. Most damaged integrations fail on the second — they hand out the reward when the advert closes as a substitute of when it really completes. The seven examples beneath present the incorrect sample, the correct sample, and what each prices you in retention. |
Rewarded video is the highest-earning format on the net, and likewise the best to interrupt. The advert unit itself is never the issue. The mixing round it’s. A reward that fires on the incorrect occasion, a no-fill that freezes the sport, a consent gate that by no means resolves — these are code selections, not media selections, they usually quietly bleed retention lengthy after the eCPM report appears to be like effective.
This information is about these selections. Not a gallery of video games, however a set of concrete patterns you possibly can test your personal construct towards. Every instance pairs the anti-pattern most integrations ship with the sample they need to ship as a substitute. The whole lot right here is framed for the net stack — HTML5, WebGL, and the JavaScript SDK layer — as a result of that’s the place the callback contracts really dwell.
Net rewarded video additionally behaves otherwise from its cell cousin. There isn’t a app-store SDK doing the heavy lifting for you, no native lifecycle to lean on. The browser is your runtime, the JavaScript callback is your supply of reality, and consent state is one thing you resolve your self earlier than the primary request. That shifts extra accountability onto the combination layer — which is strictly why getting these seven patterns proper issues extra on the net than anyplace else.
| The advert unit is never the issue. The mixing round it’s. |
The Clear Integration Scorecard
Earlier than the examples, right here is the rubric they map to. 5 marks. A rewarded integration that misses any one in all them is leaking both income or gamers, normally each. Rating your personal construct towards it earlier than you ship.
| Mark | What it means | Failure symptom |
| 1. Specific opt-in | The participant chooses to look at — by no means auto-played or compelled. | Rage quits, damaging evaluations, low completion. |
| 2. Verified completion | Reward fires on a confirmed completion sign, not on ad-close. | Reward exploits, or gamers who really feel cheated. |
| 3. Swish no-fill | No advert obtainable? The sport continues with out penalty. | Frozen UI, caught loading spinners, laborious locks. |
| 4. Frequency & placement self-discipline | Affords seem at pure resolution factors, capped per session. | Fatigue, churn, banner-blindness to the supply. |
| 5. Consent-aware loading | Init respects TCF / GDPR state earlier than requesting an advert. | Compliance threat, empty fills within the EU. |
The 7 Examples
1. Gate the reward on completion, not on ad-close
That is the only most typical integration bug, and the costliest. A participant opens the advert, the advert renders, and the developer wires the reward to the ‘advert closed’ occasion. The issue: a participant can open and instantly dismiss the advert, or a community hiccup can shut it early, and the reward nonetheless fires. Worse, some builders do the alternative — they solely reward on shut and miss reliable completions.
The appropriate sample keys the reward to an express standing object. Within the AppLixir v6.1.0 contract, which means checking standing.kind === “full” contained in the callback earlier than granting something. Advert-close is a UI occasion. Completion is a enterprise occasion. By no means conflate them.
2. Deal with no-fill with out punishing the participant
There is not going to at all times be an advert. Fill charges on the net are wholesome however by no means 100%, and a participant who opts in anticipating a reward ought to by no means be left worse off when no advert returns. The damaged sample exhibits a spinner that by no means resolves, or blocks the reward solely whereas providing no path ahead.
The appropriate sample treats no-fill as a first-class consequence. Detect it within the callback, restore the sport state immediately, and — the place your design permits — grant a small fallback reward or just let the participant proceed. The participant opted in good religion. Don’t tax them to your advert server’s stock.
A helpful design precept: the no-fill path and the completion path ought to each return the participant to a playable state throughout the identical body price range. In case your success path is instantaneous however your failure path stalls, gamers be taught to mistrust the button solely, and your opt-in fee erodes throughout the entire session — not simply the second that didn’t fill.
3. Place the opt-in at a pure resolution level
The place you supply the advert issues as a lot as the way you wire it. The anti-pattern interrupts lively play with an unprompted supply. The appropriate sample surfaces it at a second the participant already needs one thing: a revive after loss of life, a foreign money top-up at a retailer, a bonus at level-end. This ties on to the six placement zones within the Rewarded Video Advert Placement Playbook — the combination code is barely pretty much as good because the second it fires in.
4. Cap frequency in code, not in hope
An unbounded reward supply trains gamers to grind advertisements as a substitute of enjoying, and it flattens your eCPM as impressions inflate. The damaged sample depends on the participant to self-limit. The appropriate sample enforces a per-session and per-placement cap in your personal state layer, tracks presents proven, and hides or greys the button as soon as the cap is hit. Frequency self-discipline is a code accountability. Don’t outsource it to participant restraint.
Caps additionally defend the worth of every impression. Advertisers pay extra for engaged, non-saturated audiences, so a disciplined cap tends to elevate eCPM reasonably than depress whole income. The counterintuitive result’s that exhibiting fewer, better-placed presents ceaselessly earns greater than exhibiting each give you technically can.
5. Initialize consent-aware, particularly within the EU
On the net, a rewarded request that ignores consent state is each a compliance threat and a income leak. The anti-pattern requests an advert earlier than the TCF string is resolved, producing empty fills or non-compliant impressions in GDPR areas. The appropriate sample reads consent state first, initializes the SDK as soon as it’s identified, and solely then requests. Privateness-first isn’t a tax on income right here — a clear consent move is what unlocks premium European demand within the first place.
6. Preload intentionally — don’t lazy-load on the faucet
When you request the advert solely on the instantaneous the participant faucets the button, you’ve gotten designed a delay into your greatest monetization second. The participant waits, momentum dies, some stroll away. The damaged sample lazy-loads on demand each time. The appropriate sample preloads the subsequent advert within the background after the earlier consequence resolves, so the supply is prepared the second the participant needs it. Preloading is the distinction between an instantaneous reward and a clumsy pause.
7. Restore sport state cleanly after the advert returns
A rewarded advert arms management to a different floor after which arms it again. The whole lot the participant left — audio, physics loop, enter focus, pause state — should return precisely because it was. The anti-pattern resumes with muted audio, a caught pause overlay, or a dropped enter handler. The appropriate sample snapshots state earlier than the advert, and restores it contained in the completion callback. The reward is the purpose, however a damaged return is what the participant remembers.
This issues extra on the net as a result of the advert typically takes over the identical tab and shares the identical audio context as your sport. Pausing the sport loop and suspending audio earlier than the request, then resuming each as soon as the callback fires, isn’t optionally available polish — it’s what makes the advert really feel like a seamless a part of the sport reasonably than a jarring detour. Take a look at the return path on the completion, no-fill, and early-close outcomes individually; they don’t at all times resume identically.
What Every Anti-Sample Really Prices
Integration bugs hardly ever present up as errors. They present up as retention drift and income that underperforms the format’s potential. Right here is the mapping.
| Anti-pattern | Instant value | Retention value |
| Reward on ad-close | Reward exploits or cheated gamers | Belief erosion; loop feels rigged |
| Ungraceful no-fill | Frozen UI, caught classes | Session abandonment |
| Interruptive placement | Low opt-in fee | Fatigue-driven churn |
| No frequency cap | Inflated, low-value impressions | Grind fatigue, eCPM decay |
| Consent-blind init | Empty EU fills, compliance threat | Misplaced premium demand |
| Lazy-load at faucet | Latency on the reward second | Drop-off earlier than completion |
| Soiled state restore | Damaged audio / enter on return | Perceived instability |
Retrofitting an Present Integration
Most groups studying this have already got rewarded video dwell and can’t rebuild it from scratch. You don’t want to. Work the scorecard in precedence order, as a result of the marks aren’t equally costly to get incorrect.
Begin with verified completion. Audit precisely which occasion grants the reward, and transfer it onto the completion sign whether it is anyplace else. It is a small code change with the most important payoff, as a result of it closes each the exploit path and the cheated-player path directly. Subsequent, harden the no-fill and state-restore paths — these are the 2 failure modes gamers really feel most straight, and they’re normally a number of traces of callback dealing with. Solely then tune placement and frequency, that are design selections you possibly can iterate on with dwell information. Consent-aware init ought to already be in place for EU compliance; if it isn’t, deal with it as pressing reasonably than optionally available.
The Sample Behind the Patterns
Look throughout all seven and one theme repeats: the reward have to be earned by an actual, verified sign, and the sport should survive each path round it. That’s the reason the completion callback is the backbone of a clear integration. An internet-first SDK like AppLixir exposes an express standing contract exactly so the reward will be gated on full and nothing else — the remainder of the scorecard falls out from getting that one contract proper.
When you construct towards the scorecard, most of those bugs by no means ship. When you retrofit an current integration, begin at mark two — verified completion — and work outward. It’s the one which quietly prices essentially the most.
FAQ
How do I confirm a rewarded video was really accomplished?
Gate the reward on the SDK’s completion sign, not on the ad-close occasion. Within the AppLixir contract, which means confirming standing.kind === “full” contained in the callback earlier than granting something. Advert-close means the floor went away; completion means the participant earned it.
What ought to occur if there’s no advert to point out?
Deal with no-fill as a traditional consequence. Detect it within the callback, restore sport state instantly, and let the participant proceed — ideally with a small fallback or a retry choice. By no means go away the participant on a spinner that can’t resolve.
The place ought to I place the rewarded video supply?
At a pure resolution level the place the participant already needs one thing: a revive, a foreign money top-up, or a level-end bonus. Keep away from interrupting lively play with an unprompted supply, and cap how typically the supply seems per session.
Does consent dealing with scale back my rewarded income?
The alternative. A consent-aware init that resolves the TCF/GDPR state earlier than requesting an advert is what unlocks premium European demand. Requesting earlier than consent is understood produces empty fills and compliance publicity.
Ought to I preload the rewarded advert or load it on demand?
Preload. Request the subsequent advert within the background as soon as the earlier consequence resolves, so the supply is instantaneous when the participant faucets. Lazy-loading on the faucet builds a delay into your highest-value second.
| Construct rewarded video the correct method
AppLixir is a web-first rewarded video platform constructed for HTML5, WebGL, and browser-based video games — with an express completion contract, privacy-first consent dealing with, and clear no-fill conduct baked in. See the combination reference and begin monetizing with out breaking retention. |
