Add a rewarded offerwall to your app in under 10 minutes

Under ten minutes for a single rewarded offerwall placement. The SDK ships a ready-made offerwall UI, so you add a dependency, initialise it with your app key, and call the show method. There is no layout or design work. A full multi-placement implementation across iOS and Android is typically an afternoon.

No, if it is placed correctly. An offerwall monetises the roughly 95% of users who never make an in-app purchase. Those users have no purchase intent to cannibalise. The users who do spend are better served by your existing purchase flow. The recommended pattern is an offerwall as an additional path to the same currency or an alternative reward, not as a replacement for a purchase prompt.

Native SDKs for Android (Kotlin/Java), iOS (Swift/Objective-C), React Native, Flutter, Unity and Web. All of them use the same server-side reward validation API, so a game shipping on several platforms validates rewards through one integration.

Rewards are credited only after server-side validation of the completed offer, using signed postbacks. Device intelligence, replay protection and rate limiting run before a reward is credited, so a reward cannot be claimed by replaying a callback or from a tampered device.

Weekly payouts, with real-time reporting in the publisher dashboard. Revenue is attributed to completed offers through server-side validation, and fraud filtering runs before the reward is credited. Minimums and payment methods are listed on the publisher terms page.

No. There is no minimum volume, no integration fee and no exclusivity requirement. The publisher terms cover the standard commercial terms and there is no minimum payout threshold documented for new accounts beyond the standard weekly schedule.

A rewarded video pays a few dollars per thousand impressions and the user watches an ad. An offerwall pays on a completed task - installing an app, finishing a survey, signing up for a service - so the payout per user is far higher. That is why offerwall eCPM benchmarks sit well above rewarded video, and why publishers pair the two: rewarded video for the cheap engagement, offerwall for the revenue.

The SDK install itself takes under ten minutes. The realistic timeline is dominated by testing: verify your reward callback fires, confirm the postback validates server-side, and check the dashboard attribution before you release. For an app that already ships, that is typically a day. The detailed timeline is covered in the offerwall SDK integration guide.