The wall
One embeddable page carrying 10,327 offers, targeted to each user's country and device, priced in your own currency.
What your user sees
Your page, your currency, and nothing they cannot finish.
Only offers they can do
Country and device targeting are applied in the query, not hidden after the fact. Nobody spends ten minutes on something that was never going to pay them.
The reward in your coins
Your coin name, singular and plural, at the rate you set — written the way your players write numbers, 1,250.50 or 1.250,50, chosen per placement.
Their own reward history
What they earned, what is pending, and a button to report a reward that never arrived. The claim reaches us with the click attached, so it is not a screen you have to build or a ticket you have to answer.
The whole ladder, before they start
A multi-step offer is where most walls lose people. Ours shows every milestone and what each pays before a user commits, so nobody finds out at step two that step three was the real reward.
- Every step and its payout, up front
- Each milestone credited on its own, as it lands
- Partial progress still earns
- 1 Install and open the app+400
- 2 Reach level five+1,200
- 3 Play on three separate days+3,400
An example ladder, drawn the way the wall draws one.
What you control
All of it is a setting. None of it is a support request.
It looks like your app, not like ours
Edited beside a live preview, so you see it before your users do. The only thing that stays ours is a line of attribution in the footer.
- Dark, light, or follow the device
- Your accent colour, your logo, your heading
- A grid of cards or a list of rows, comfortable or compact
- Custom CSS for when the options run out
You decide what is on it
Set per placement, so a children's game and a cashback site run from one account without sharing a rule.
- Block whole categories or whole countries
- Hide anything paying under a floor you set
- Require a signed wall URL, so a user id cannot be swapped in the address bar
- Or skip the wall entirely and build your own front end on the JSON API
What your users will find on it
Every kind of offer the wall carries. Turn off the ones that are wrong for your audience and they are never shown again.
The unglamorous half
This is what an offerwall is judged on after week one.
Screened before it is written
Bots, blocked IPs, blocked users and click-velocity limits are checked before a click row exists. Nothing that fails a gate reaches your ledger.
A rejection is recorded, not dropped
A conversion we refuse is still stored, with the reason. When a user swears they finished something, support can say what arrived and why it was not paid.
No cookies. No session. At all.
The wall runs inside your page, so a cookie on it would be a third-party cookie: blocked by most browsers, worth nothing in the rest. We set none — a promise you can check with your developer tools open. The one third party on it is the ZerAds banner at the bottom, in its own frame.
Integration
A URL and an endpoint
Paste the iframe with your own user id and the wall is live. When somebody finishes an offer we call your server with a signed postback and you credit them. Reversals, duplicates and retries are handled on our side.
<iframe
src="https://offerwall.gg/wall/YOUR_PUBLIC_KEY?userId=USER_ID"
width="100%" height="720"
style="border:0"></iframe>
Put it in front of your users
Create a placement, paste one line, and the wall is live on your site this afternoon.