Tapjoy, RevU, adjoe and ironSource Offerwall appear in many publisher shortlists, but the names no longer describe four equivalent choices. Tapjoy and RevU offer rewarded marketplaces. adjoe Playtime centers on rewarded game discovery and engagement. The legacy ironSource Offerwall requires a migration discussion, with Unity publishing a transition path to Tapjoy.
For 2027 planning, compare the active products on audience fit, reward delivery, integration work and incremental revenue. Keep the ironSource name in the checklist if your app still has legacy offers or callbacks. Removing it from an article would hide a real operational dependency for publishers already using it.
The right decision also depends on your virtual economy. An offerwall gives users another way to earn currency or benefits. That can support engagement and advertising revenue, but the reward value must make sense beside purchases, existing rewards and the effort required to complete an offer.
How an offerwall differs from rewarded video

A rewarded video typically grants a benefit after the user completes the specified ad experience. An offerwall presents a choice of advertiser tasks. The user may need to install a game, reach a milestone, make an eligible purchase or complete another defined action. Completion can happen outside your app and much later than the initial click.
That delayed journey makes attribution, user identity and reward handling central to the integration. A user can finish an offer after a promotion ends or after your app releases a new version. Your support and reward systems need to recognize that activity without crediting the same completion twice.
Compare offerwalls using revenue per eligible user, engagement, completion and support outcomes. A provider’s advertised eCPM can use a different denominator from your rewarded video report. A large headline number is therefore insufficient evidence that one format or partner will earn more in your app.
At a glance: four names, different decisions
| Option | Role in a 2027 decision | Integration consideration | What to validate |
|---|---|---|---|
| Tapjoy Offerwall | Active rewarded offerwall and Unity migration destination | Supported SDK and reward configuration | Offer availability, reward flow and migration requirements |
| RevU | Active offerwall for apps, games and websites | Hosted, iframe and API options without a native SDK | Server postbacks, interface fit and negotiated terms |
| adjoe Playtime | Rewarded game discovery and engagement | Platform and SDK compatibility for your app | Audience appetite for trying other games |
| Legacy ironSource Offerwall | Migration and in-progress reward obligations | Existing client or server callback path | Continuity of rewards after new offers stop |
The comparison below describes product capabilities from official sources. The evaluation guidance is a publisher decision framework. It is not a claim that we tested these providers on the same live game or found a universal revenue winner.
1. Tapjoy Offerwall

Tapjoy Offerwall is Unity’s rewarded marketplace product. It is relevant to a publisher adding an offerwall and to a team transitioning from a legacy ironSource Offerwall integration. Use the current Tapjoy or Unity Offerwall documentation for the exact SDK and platform being shipped.
For a game with an established currency economy, begin by mapping how an earned reward reaches the player’s balance. Decide which system is authoritative, how user identifiers are mapped and how the team will investigate a disputed completion. The user sees the missing currency inside your game, even when the underlying investigation involves several partners.
Best reason to evaluate it: you want a conventional rewarded offerwall and can support the required integration and economy design. Ask for actual eligible offers in your main countries and operating systems. A demonstration account’s catalogue may differ from the production experience available to your users.
Before launch: validate placement access, currency conversion and the complete reward journey. Include an interrupted session, a returning user and a duplicate completion notification in testing. Set up a support path that collects the offer reference and relevant timestamps without asking players to provide unnecessary personal information.
2. RevU

RevU’s publisher page describes an offerwall with hosted, iframe and whitelabeled API options, without a native SDK. It also describes a server-side postback endpoint for reward crediting and payment terms agreed during onboarding. That makes it relevant when a team wants to assess an offerwall without adding another native advertising SDK.
SDK-free delivery still requires implementation work. Your app or website needs an appropriate entry point, safe user identification, a working crediting integration and a support workflow. A hosted interface can simplify the front end while the publisher continues to own its account balance and economy rules.
Best reason to evaluate it: the available integration paths suit your technical constraints, or your product spans web and app environments. Ask which approach is recommended for the current app store and device requirements that apply to your product.
Before launch: confirm the postback contract, authentication, retry behavior and the information returned for reversals or disputed events. Agree on operational and payment terms in writing. Vendor-managed offer support is helpful, but your own player support team still needs to explain where users should go and how unresolved cases will be escalated.
3. adjoe Playtime

adjoe Playtime describes a journey in which users discover games through a host app, install them, engage with them and earn the host app’s rewards. Its publisher proposition is closely tied to that game discovery experience. Avoid reducing every campaign to one fixed rule about minutes played: available requirements and reward events must be confirmed for the implementation.
Playtime deserves consideration when trying other games fits the user’s reason for earning rewards. A loyalty app and a highly competitive strategy game may have very different appetites for that journey. Traffic volume alone does little to explain whether the experience will feel relevant.
Best reason to evaluate it: your audience has a natural incentive to explore advertised games and return to redeem benefits. Ask about device and operating system support, catalogue availability and the information users see before starting an offer.
Before launch: review the complete discovery-to-redemption flow on supported devices. Measure the return to your app after off-app engagement. Include reward cost and support work in the economics. Revenue growth from an additional activity is more useful when users also continue using the product they originally installed.
4. Legacy ironSource Offerwall: plan the transition

Unity’s Offerwall migration checklist explains how to transition an ironSource Offerwall setup to Tapjoy. It covers dashboard setup, replacing offerwall code and preserving rewards for in-progress offers. The legacy integration should therefore be treated as a migration dependency in this comparison.
For server-to-server completions, Unity instructs publishers to continue listening for ironSource callbacks and rewarding users for 90 days after they stop showing new offers. For client-side crediting, it calls for retaining the required SDK credit-checking flow for at least 90 days. The exact code path matters, so follow the checklist for your implementation.
LevelPlay mediation is a separate product role. Review whether the SDK is still required for mediation before removing a dependency used by the old offerwall. Also review privacy flags when configuring Tapjoy independently. A migration checklist should name the actual components rather than assigning one retirement date to everything carrying an ironSource or Unity label.
Before launch: inventory active offers, record when new legacy offers stop and assign an owner for the callback overlap. Keep a reconciliation report for late completions. A successful transition includes users receiving rewards they already earned, as well as new users being able to open the replacement wall.
Which option fits these five publisher situations?
A small team adding its first offerwall
Choose one provider for the first controlled launch. Document your economy and reward handling before discussing extra demand. Ask for a working implementation plan, realistic support ownership and a sample of available offers in your main markets. A manageable launch gives you a baseline for later comparisons.
An established game with meaningful purchases
Measure total monetization, including purchases, alongside offerwall revenue. Segment the experiment by existing payer status where your analytics and privacy setup allow it. Rewards that are too generous can change purchasing behavior or progression. Treat those effects as test questions rather than assuming every offerwall dollar is incremental profit.
A loyalty or rewards app
Evaluate redemption cost, user eligibility and fraud controls as part of the core model. Playtime-style discovery may fit the product, while broader offer catalogues may serve different needs. Confirm which reward forms are permitted and financially sustainable. A virtual point and a cash-equivalent benefit have different operating implications.
A publisher with limited native engineering capacity
Review RevU’s hosted, iframe and API options against your actual constraints. Count backend work and interface testing, even when a native SDK is unnecessary. Before choosing, have the person responsible for release approval inspect how users enter the wall, return to the app and receive their rewards.
A publisher still using ironSource Offerwall
Prioritize the migration inventory and in-progress rewards first. Then compare the replacement product with your wider monetization plan. Keep old and new transaction references traceable during the overlap. Avoid changing the currency conversion, offer entry point and reward backend simultaneously unless you can independently verify each change.
How to test incremental offerwall revenue
Use comparable audiences and decide what counts as success before launch. A useful primary outcome is total revenue per eligible user over a defined observation period. Add purchase revenue, reward cost where relevant, retention and support volume. Show offerwall engagement separately so a small group of highly active users does not obscure the wider audience outcome.
Record the funnel from eligibility to entry, offer start, completion and successful crediting. Each stage answers a different question. Low entry can indicate poor placement or weak relevance. Strong starts with few credited completions require a different investigation. Aggregate revenue alone will not show where the journey breaks.
For delayed tasks, let the observation window cover the activity being measured. A short launch report can be useful for technical health while remaining incomplete as an economic assessment. Label provisional revenue and later adjustments clearly. Reconcile transaction-level records with provider reports before changing the reward rate.
If you add a second offerwall later, test the combined setup against the existing one. Catalogues and audiences can overlap. More entry points can also divide attention or confuse users. The result to evaluate is the publisher’s total outcome after additional maintenance and support, rather than the sum of two sales forecasts.
Reward reliability and operating costs
Build duplicate protection into the reward ledger. Store a stable completion reference, user mapping, reward amount and processing status so retries can be handled safely. The precise implementation belongs to the provider’s current documentation, but the operating goal is straightforward: each valid completion receives the intended reward once.
Keep a visible route for missing-reward cases. Tell users which partner handles offer-specific claims and what evidence is useful. Track unresolved cases and their age. A support queue is part of the product’s monetization cost, and a good revenue experiment should expose that cost rather than bury it in another team’s workload.
Review promotions against your economy before scheduling them. A currency multiplier changes the benefit the user receives and can alter offer participation. Record the funded reward rate, promotion dates and eligibility. Compare the outcome with a suitable baseline after late rewards have arrived.
Frequently asked questions
Which offerwall pays the most?
No universal ranking is supported by equivalent public tests across all audiences. Compare actual offers, credited revenue, total app monetization and user experience for your countries and operating systems.
Are Tapjoy and ironSource Offerwall interchangeable?
Unity provides a migration path from the legacy ironSource Offerwall to Tapjoy. Migration includes dashboard, code and in-progress reward work. The names should not be substituted without checking those dependencies.
Does RevU require a native SDK?
RevU advertises SDK-free hosted, iframe and API delivery. Publishers still need the appropriate interface, user identification and server-side crediting setup.
Is adjoe Playtime the same as a video ad?
Playtime’s documented journey involves discovering and engaging with advertised games to earn host-app rewards. It differs from completing a single rewarded video inside your app.
Should publishers run two offerwalls?
Consider a second provider after establishing a reliable baseline. Test whether it adds useful offers and incremental revenue after overlap, reward economics and operational work are considered.
Can an offerwall reduce purchase revenue?
It is a possibility to measure, especially when rewards substitute for purchased currency. Assess purchases and total revenue within the same experiment instead of treating the offerwall dashboard as the complete result.
Choose a wall your team can operate
Review the wider offerwall network shortlist and the purchase and advertising monetization guide alongside this comparison. For help reviewing the reward flow and the rest of your ad setup, start with UndrAds and describe the audience, platforms and current implementation.



