Offerwall advertising network

Where studios meet the audiences that finish what they start.

Advertisers publish campaigns with the goals that matter to them — an install, a level, a first purchase — and pay only for the ones their own systems confirm. Publishers put those offers in front of their own users and keep an agreed share of every conversion.

Apply to join How it works

Accounts are opened by application. Every application gets a written answer.

Two sides, one ledger

Whichever side you arrive from, you are looking at the same conversion

An advertiser buys a completed goal. A publisher sells the audience that completes it. Both read the same row afterwards.

For advertisers

Buy the action, not the impression

Describe the campaign once: where it may run, which platforms it supports, and which steps count as success. Each goal carries its own price, and your budget moves only when your server confirms one.

Goals priced one by one, in whole cents
Country and platform targeting on every campaign
Each conversion tied to exactly one click

How advertising works

For publishers

Give your users something worth their time

Point your reward site, app or game at a placement and the wall appears with the offers that user may complete. You keep an agreed share of every conversion and credit your users in your own currency.

A hosted wall that needs a signed URL and your user id
A revenue share fixed per publisher, applied per conversion
A signed server callback when a conversion settles, retried until you answer

How monetizing works

How it works

One click, one conversion, one row both sides can read

Nothing is credited on a guess. This is the whole path, from the offer a user opens to the money that lands on either side of it.

1
User
Opens the wall
A member of a publisher's site or app opens their placement. The wall loads the campaigns that are live for that user's platform — and for their country, where the deployment can locate it — priced in the publisher's own currency.
2
User
Picks a campaign
Choosing an offer records a click and issues a click id. That id is carried into the advertiser's tracking URL through its macros, so the visit can be recognised again later.
3
User
Completes a goal
A campaign is a set of goals — install, reach a level, finish a purchase. Each goal carries its own payout and, where the advertiser sets one, its own time limit.
4
Advertiser
Confirms the goal
The advertiser posts back the completed goal against the click id. Nothing is owed and nothing is credited until that confirmation arrives.
5
OpusWall
Splits the payout
We attribute the conversion to its click, price it in integer cents, and split it into the publisher's revenue share and the OpusWall margin. The share lands on the publisher's balance.
6
Publisher
Rewards the user
Our server-to-server postback reaches the publisher's endpoint, signed with the placement secret. It already carries the amount in the publisher's own currency, converted at the rate on the placement, so the publisher verifies the signature and credits the user.

Every amount is an integer number of cents from end to end, so nothing drifts on the way through. The publisher's share is rounded down to the whole cent and the remainder stays in our margin, which means a split can never pay out more than came in. A confirmed conversion can still be reversed later — the same amount comes back off both sides, as its own movement rather than a silent correction.

Where the platform stands today

Applications are open and read by a person, and an approved account opens a working panel. The hosted wall, the click redirect and both server-to-server postbacks are running: a publisher's members open the wall, an advertiser's server confirms completed goals to our endpoint, and every settled conversion is signed and delivered to the publisher's server, retried until it is acknowledged. What is not built is marked Planned where it is described — today, the mobile SDK and the Offers API. The network is new, so there are no customer figures to quote, and this site quotes none.

Integrations

Four ways in, one ledger behind them

Two are running today: the hosted wall, and the signed postbacks between our servers and yours. The mobile SDK and the Offers API are specified and not built, and each page says exactly where it stands.

Read the specs

Hosted offerwall

A URL you open in an iframe, a new tab or a webview, signed on your server. Nothing to compile.

Mobile SDK

Planned

A thin wrapper for iOS and Android that opens the wall and carries your user id.

Offers API

Planned

The offer list as JSON, so the wall can be rendered inside your own design.

Server postbacks

Signed server-to-server calls in both directions: the advertiser's confirmation to us, our credit or reversal to the publisher.

Why OpusWall

Built around the thing everyone argues about: the conversion

Most disputes in this industry come down to whether something happened and what it was worth. The platform is designed so both are a matter of record.

Direct campaigns only

We take campaigns from the studio that owns them and nowhere else. No resold inventory passed along a chain, so both sides always know who is on the other end of a payout. This is a rule we are starting with, not a catalogue we have built up.

A revenue share written down

A publisher's share is set on the publisher, not negotiated per campaign, and applied to every conversion payout in whole cents. The split is frozen onto the conversion when it is recorded, not buried in a monthly total.

One set of numbers

Advertiser spend, publisher earnings and our margin are three views of the same conversion row, with its click id and its timestamp. Reports reconcile because there is nothing else to reconcile them against.

Start with a URL

The hosted wall needs a placement id and your own user id, signed on your server with your wall key. A native SDK and an Offers API, for teams that want the wall inside their own interface, are specified and not yet built.

Applications are open

Tell us what you run

Publishers and advertisers both start the same way: a short application, read by a person, answered in writing. Approval creates your organization and sends the invitation that opens your sign-in.

Apply to join Ask a question first

No public sign-up, no self-serve account, no card required to apply.