Rewarded User Acquisition: How It Works in 2026

What is rewarded user acquisition?

Rewarded user acquisition (rewarded UA) is a way to get new users by offering them a reward, usually coins, gems, or points inside another app or website, for installing your app and reaching a goal in it. The reward comes from the publisher whose users see your offer, and you pay the channel a fixed amount per confirmed result, such as a finished tutorial or level 10, not per impression or click. It is also called incentivized user acquisition or offerwall user acquisition, after the most common place these offers appear.

Done well, it buys a specific in-app action from real people at a price agreed in advance. Done badly, it buys installs that vanish the next day.

Rewarded vs non-rewarded UA

In non-rewarded UA, such as search ads, social ads, or video ads in other apps, users install because the ad made them curious about your app. In rewarded UA, users start because of the reward and then decide whether they like your app.

The row that decides most campaigns is “intent after the goal.” Google said in a 2017 post on the Android Developers Blog that its research team found incentivized users generally have lower retention and make fewer in-app purchases. That finding is old and general, but it points to the right habit: judge rewarded users by what they do after the paid goal, in their own cohort. Incentivized traffic explained covers the user side in more depth.

Where rewarded users come from

Offerwalls inside publishers’ apps and sites

An offerwall is a page inside someone else’s game, app, website, or community that lists offers from many advertisers. The user picks your offer, follows the steps, and the publisher credits them when the goal is confirmed. It is the core rewarded UA channel, because the goal is spelled out in advance. How to advertise on offerwalls walks through a campaign step by step.

Rewards and loyalty apps

Some apps and websites exist mainly so that people can earn: points for surveys, games, shopping, or app offers, redeemed for gift cards or other rewards. Their users are used to multi-step offers but are also the most reward-driven audience you can buy. Google Play does not allow an app whose main functionality is rewarding users for installing other apps, so check how a partner’s own app is built before you rely on it. Google’s App Promotion policy also says you are responsible for the ad networks and affiliates that promote your app.

In-game rewarded placements

Games reward players with an extra life or a chest for watching an ad or trying an offer. The two formats behave differently. In a rewarded video, the reward is for watching your ad, so a user who then installs your app does it by choice. In an offer inside a game, the reward depends on what the user does in your app. Ask each partner which format your budget buys, because the two produce very different cohorts.

How rewarded UA is priced

Rewarded UA is sold per result, at different depths:

• Per install (CPI). You pay when the app is installed and opened. Cheap, but it buys the action that is easiest to fake and least predictive of value.
• Per engagement (CPE). You pay when the user reaches a goal in your app, such as level 5 or a finished onboarding. What is CPE? explains the model.
• Per action (CPA). You pay for a defined business event, such as a confirmed account, a first deposit, or a first purchase.
• Multi-step goals. One offer with several events, each with its own payout: a small amount for the install, more for the tutorial, the most for a deep goal. The user sees a progress path, and you pay most of the budget only for users who go far. Multi-event offers covers how to build the ladder.

Why deeper events beat installs

Paying for the install alone has three problems. An install is cheap to fake. A user who only had to install has no reason to stay, so cost per retained user is often worse than the price suggests. And installs are what store policies watch: Google said in the same 2017 post that it monitors and filters incentivized installs, including removal from the top charts. A deeper event proves real use, gives your server something to record, and moves spend toward the users you want. CPI vs CPA for apps compares the two models in full.

What Google Play and Apple allow

Both stores allow rewards inside apps, and both draw a hard line at rewards for ratings, reviews, and rank manipulation. Checked on October 20, 2026; both stores revise their text, so read the live pages before you launch.

Google Play

Google Play’s User Ratings, Reviews, and Installs policy prohibits any manipulation of ratings, reviews, or install counts. It tells developers not to offer rewards or incentives for ratings or reviews, not to use automated services to inflate installs or ratings, and not to make incentivizing installs of other apps an app’s main functionality. The 2017 blog post adds context: Google said incentivized installs can be a legitimate acquisition channel for some developers, while installs used to manipulate placement are filtered. Incentivized installs and Google Play policy goes through each relevant policy page.

Apple App Store

Apple’s App Review Guidelines (last updated October 16, 2026, at the time of writing) say in guideline 3.2.2(x) that apps must not force users to rate the app, review the app, download other apps, or take other store-related actions to access functionality or content, and that apps may otherwise incentivize users to take specific actions within apps, such as completing a level or watching an ad. The introduction to section 3 warns that Apple may expel developers who inflate chart rankings with paid, incentivized, filtered, or fake feedback, and guideline 5.6.3 says manipulating charts, search, reviews, or referrals is not permitted. For the host side of this, see offerwall rules for iOS apps.

How to measure rewarded UA with an MMP and postbacks

Rewarded UA only works if every paid event is confirmed by your systems, not by the user or the channel. The usual setup:

1. Attribution. Your mobile measurement partner (MMP) matches each install to the click on your offer’s tracking link and keeps the network’s click ID, so later events can be reported back to the right partner. What is an MMP? explains attribution on Android and iOS, including what changes when a user declines tracking on iOS.
2. Event mapping. You choose which in-app events the MMP shares with the network, such as tutorial_complete or level_10. Adjust’s help page on choosing data sharing options is explicit that data for unmapped events is not shared with your network, so a goal you forget to map never reaches the partner and never gets paid.
3. Server-to-server postback. When the event happens, your MMP or your own backend calls the network’s postback URL with the click ID and the event. The network then credits the publisher, and the publisher rewards the user. What is a postback URL? covers macros and statuses.
4. Reversals. If you later find an event was invalid, such as a refunded purchase or a fraudulent device, agree in advance how it is reversed and within what period.

Keep the rewarded cohort separate in your analytics and compare its day 7 and day 30 retention, payers, and revenue with your other channels. App retention benchmarks gives you published reference points.

Fraud risks and controls

Any channel that pays per result attracts fake results, and in rewarded traffic the user is paid too. The main risks:

• Fake completions from emulators, device farms, or scripts that fire events without a real user.
• Country spoofing through VPNs and proxies, to reach offers that pay more in richer markets.
• Multi-accounting, where one person completes the same offer many times under different accounts.
• Attribution fraud such as click injection, click spamming, and SDK spoofing, which steal credit for installs. Click injection and SDK spoofing explains how each works.

The controls stack in layers. On the measurement side, MMPs offer filters: Adjust’s fraud prevention features page describes filters for anonymous IP addresses (known data centers, VPNs, and Tor exit nodes), click injection on Android, atypical click distributions, and behavioral anomalies, as part of a paid suite. On your side:

• Fire postbacks only from your server or MMP, never from code a user can trigger.
• Validate high-value events, for example check purchase receipts before a first-purchase step counts.
• Count each goal once per account and device on your side.
• Watch time-to-goal: a level that takes real players 40 minutes but shows up in 90 seconds is a signal.
• Use daily caps per country while you learn how the traffic behaves.

Ad fraud and bot traffic lists the warning signs to look for in your own data.

How to choose events and payouts

1. Find the event that predicts value. Look at which early action your retained or paying users share: finishing onboarding, reaching a level, linking an account, or returning on day 2.
2. Check that it is reachable. A goal most users reach in one or two sessions gets completions. A goal that takes two weeks gets few, unless it is the last step of a ladder.
3. Make it checkable. The event must be recorded by your server or MMP the moment it happens, so it can fire a postback.
4. Work back from value. Estimate what a user who reaches the goal is worth over 30 or 90 days, then set the most you can pay per goal for your target return. The LTV calculator and cost per result calculator help with the math.
5. Price by country. A user is not worth the same everywhere. How to choose countries for your campaign covers picking the first markets.

Keep the first step small but not zero, so users see early progress, and describe every step in words that match exactly what your tracking reports.

When rewarded UA fits, and when it does not

Rewarded UA tends to fit when:

• You have a clear in-app event that predicts value and that your server records.
• Your app earns early, through in-app purchases or ads, so a rewarded cohort can pay back within a window you can measure.
• You need predictable volume, for example to test a new country or fill a soft launch.

It tends not to fit when:

• You cannot measure anything after the install.
• Your goal is ratings, reviews, or chart position. Both stores forbid buying those.
• Your app is aimed at children or your audience is mostly under 16.
• Your product is restricted on the channel, such as unlicensed gambling or offers that ask users for money or sensitive data. What Sharklio does not advertise lists the categories.
• A user’s value only shows after months and no early event predicts it.

Treat rewarded UA as one channel next to non-rewarded campaigns, with its own cohort, targets, and budget.

Frequently asked questions