Most ad formats interrupt the user. Rewarded ads are different because the user asks for them: they choose to watch an ad and get something in return. Because of that, rewarded ads are often the easiest format to add without making people resent your app. They are also easy to get wrong. If the offer is unclear, the reward goes missing, or the economy gets thrown off balance, a format users would happily choose turns into one more reason to uninstall.
This post covers patterns that work for small teams: where to put offers, how to make sure rewards actually arrive, how to limit how often ads show, and how to check that the whole thing helps you.
The three rules underneath every pattern
Every pattern below follows from three rules:
- Opt-in is real. The user starts the ad by tapping a clear offer. They are never pushed into one. Ad network policies generally require this for the rewarded format, and users notice when you blur it.
- The offer is explicit. Before tapping, the user knows exactly what they will get: "Watch a short ad for 50 coins," not "Get a bonus."
- The reward is reliable. If the user finishes the ad, they get the reward, even if the app crashes, the network drops, or the ad SDK fires its callbacks in an odd order.
Breaking any one of these costs you trust, and players don't easily give it back.
Where to place rewarded offers
Pattern 1: The moment of need
The strongest placement is right where the user wants something they don't have yet. That might be one more life after a failed level, a hint on a hard puzzle, or one more export in a utility app with a daily free limit. The offer sits next to the paid path or the waiting path, never in place of them.
- Show the three options side by side: wait, pay, or watch.
- Keep the free path (waiting) visible so the ad feels like a shortcut, not a toll.
- Don't show the offer if no ad is loaded. A button that spins and then fails is worse than no button.
Pattern 2: The multiplier
At the end of a level or session, offer to double what the user just earned. This works because the user has already got their reward, and the ad only adds to it. If they say no, they lose nothing. Keep the decline button the same size and contrast as the accept button. A tiny grey "no thanks" link is a dark pattern, and users can tell.
Pattern 3: The opt-in shelf
Put a small, persistent spot in a shop or menu, such as a "free daily coins" tile, where users can watch an ad whenever they like, up to a cap. It doesn't interrupt anyone, and it serves the users who like rewarded ads without bothering everyone else.
Placements to avoid
- Offers that pop up during active gameplay or in the middle of a task.
- Offers on the first screen of the first session, before the user knows what the reward is worth.
- "Rewarded" ads that start on their own after a countdown with no real choice. If you use a rewarded interstitial format, give it a proper intro screen with an obvious way to skip, as the network's policy requires.
Granting rewards reliably
This is where most problems show up. The usual bug is granting the reward when the ad closes instead of when the SDK reports that the user earned it. Or the app grants it twice when both callbacks fire. Keep the earned event and the dismissed event separate:
// Pseudocode, adapt to your ad SDK
fun showRewarded(placement: String, reward: Reward) {
val token = ledger.createPending(placement, reward) // persisted
ad.onUserEarnedReward = {
ledger.markEarned(token) // idempotent
}
ad.onDismissed = {
if (ledger.isEarned(token)) {
ledger.grant(token) // idempotent, applies once
ui.showRewardToast(reward)
} else {
ledger.cancel(token)
}
preloadNextAd(placement)
}
ad.show()
}A few details matter here:
- Persist the pending reward before showing the ad. If the app is killed while the ad is playing, the next launch can check the ledger and settle anything that was earned but never granted.
- Make grants idempotent. Each token is applied once at most, no matter how many times the callback fires.
- Show the reward after dismissal. Animate the coins landing once the user is back in your UI, so they see that it happened.
Server-side verification
If rewards have real value, such as currency that can buy premium items, a client-side callback can be faked. Several networks, including AdMob, offer server-side verification: the network calls your server with a signed request when a reward is earned. Your backend checks the signature, records the transaction ID so the same reward can't be granted twice, and credits the account. For a single-player game with nothing to trade, client-side granting is usually fine. Decide based on what a cheater could gain.
Caps, cooldowns and economy balance
A rewarded ad is a faucet in your in-app economy. If it has no limit, it can make your paid items pointless or let a few users grind through all your content in one sitting.
- Daily caps per placement. For example, "3 free hints per day." Show what's left ("2 of 3 left today") so the limit feels fair and predictable.
- Cooldowns. A short wait between views on the opt-in shelf keeps it from becoming an ad-watching loop.
- Reward sizing. Set rewards against your earn rates, not against how much the ad pays you. A good starting point is a reward roughly equal to a short stretch of normal play. Then adjust using real data.
Keep caps and reward amounts in remote config so you can change them without shipping a new build:
{
'rewarded': {
'hint': { 'amount': 1, 'daily_cap': 3, 'cooldown_sec': 0 },
'shop_coins': { 'amount': 50, 'daily_cap': 5, 'cooldown_sec': 300 },
'level_x2': { 'enabled': true }
}
}Rewarded ads and subscribers
If you also sell a subscription or an ad-free purchase, decide on purpose what paying users see. A common, user-friendly approach: paying users get the reward straight away with no ad, so the button reads "Claim" instead of "Watch." They keep the benefit, and you're not showing ads to people who paid to avoid them. Don't hide the reward from subscribers entirely. That makes paying feel like losing something.
Handling the unhappy paths
- No ad available: hide the offer or switch it to a disabled state with a short explanation. Preload ads early and again after each view.
- User leaves early: no reward, and no guilt-trip message. A neutral "Ad closed early, no reward this time" is enough.
- Offline: don't show offers that can't load.
- Consent: rewarded ads still go through your consent and ATT flow. Requests made without personalization consent may earn less, but the format should still work. Test both states.
Measuring whether it works
Don't just look at ad revenue. Log a small set of events for each placement and compare groups:
- Offer shown, offer tapped, ad completed, reward granted. The gap between completed and granted should be zero. If it isn't, you have a bug.
- Opt-in rate per placement: taps divided by offers shown. A low rate usually means the reward is too small or the moment is wrong.
- Retention and session length for users who engage with rewarded ads compared with those who don't. This alone doesn't prove the ads cause anything, since engaged users watch more of everything.
- Purchase conversion, to see whether the faucet is eating into paid items.
To get a real answer, run a holdout test. Turn off one placement for a random share of users through remote config, then compare retention and total revenue (ads plus purchases) per user over a few weeks. Let your own numbers decide whether a placement stays.
Wrapping up
Rewarded ads earn their place when they feel like a fair trade the user picked. Put offers where the user needs something, say exactly what they'll get, record the reward before the ad plays, and only apply it once. Cap the faucet so your economy holds up, treat paying users generously, and check the effect on retention with a holdout instead of guessing. Get those basics right and rewarded ads can bring in revenue without driving users away.