Skip to content
For advertisers

Pay for the goal. Not the click, not the view.

OpusWall puts your campaign in front of people who came looking for something to do. You decide which steps are worth paying for, what each one is worth, and where the campaign may run. A payout leaves your budget only after your own systems confirm the step happened.

What you get

A campaign you can describe precisely, and a bill you can explain

Four things decide whether an offerwall is worth buying: what counts, who sees it, how it is attributed, and whether the reporting survives an argument.

Goal-based payouts

A campaign carries one goal or many: install and open, reach a level, complete a purchase. Each has its own payout in whole cents and its own optional time limit, so an early step can be cheap and a deep one can be worth real money.

Targeting you control

Countries and platforms are set on the campaign, and a wall lists it only where both match — a visitor whose country is not known is shown only campaigns open to every country. Every conversion names the placement it came from, so you know which audience delivered.

Attribution you can check

Opening an offer creates one click with one id, and that id travels into your tracking URL. A conversion exists only when your server sends that id back with a completed goal, signed with your campaign's secret, which makes every payout traceable to a single event.

Reporting on the same rows

What you spent, what the publisher earned and what we kept are three columns of one conversion. Every signed postback you send for one of our clicks is logged against the campaign with the answer it got, so a disagreement starts from the same record on both sides.

Worked example

A campaign with three goals

An illustration of the model, not a customer. A mobile game sets three goals, prices each one, and pays for the ones its own server confirms.

Vertical
Mobile game
Platforms
iOS and Android
Targeting
Three countries
Payout model
CPA — cost per action
  • Install and open

    Confirmed when the game reports first launch for the click id.

    $0.90
  • Reach level 10

    Confirmed within seven days of the click; later than that, it waits for review.

    $2.40
  • Make a first purchase

    Confirmed once the purchase has cleared on the studio side.

    $6.00

A user who finishes all three

$9.30
  • A user who installs and stops costs the first goal only.
  • A user who opens the offer and never installs costs nothing at all.
  • Each confirmation carries your own transaction id: repeating one is answered as a replay and never paid twice, so send exactly one per completed step.
Pricing model

You pay per completed goal, and nothing else

No platform fee on top of a payout, no charge for the click that led to it, no minimum monthly spend to keep a campaign alive.

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.

You fund a balance, and goals draw from it

An advertiser organization has one balance, held in whole cents. A wall lists a campaign only while that balance, less what conversions already waiting for funds are owed, covers its most expensive goal and its budget still has room, so a campaign stops being shown before it can spend what was not funded.

A click made while the campaign was listed can still convert after the balance runs low, and that goal was really completed — so it is still owed. The balance never goes below zero: the conversion waits, pending, and settles by itself, oldest first, as soon as the balance covers it. Until then nothing moves and nobody is credited for it.

Every confirmed conversion costs the goal's payout as it stood when the user clicked. There is no platform fee added on top of it and no separate charge for the click that led to it.

Four payout models, one mechanism

CPI, CPA, CPE and CPS describe what kind of step you are buying, not how billing works. Underneath they are the same thing: a goal, a payout in cents, and a confirmation from your server.

  • CPI — cost per install, for a first launch
  • CPA — cost per action, for any defined step
  • CPE — cost per engagement, for depth inside the product
  • CPS — cost per sale, for a completed purchase at the goal's fixed price

What happens to the payout after you pay it

The payout is split once, at the moment the conversion is recorded: the publisher's agreed share goes to the publisher, and the remainder is our margin. Rounding is done in whole cents and the two parts always add back up to the payout exactly.

The split is ours to manage, not yours. You are quoted and billed the goal payout, and it does not change with which publisher delivered the user.

How you confirm a conversion

Your tracking URL receives our click id through the {click_id} macro. When the goal completes, your server sends that click id, the goal's event key and your own transaction id to our postback endpoint, signed with the campaign's secret. The answer says what happened, and every postback we can attribute to the campaign is in your panel with that answer.

Before any money moves, a test click walks your real flow end to end: it is checked exactly like a live postback and records nothing.

When a conversion is not paid

A conversion is recorded only when your signed postback names a click we issued and a goal of that campaign. One that arrives after the goal's time limit, or when the budget or a cap has run out, is held for review rather than paid automatically. One your balance does not cover waits, and settles by itself once you fund it.

A conversion you have already confirmed can be reversed by postback for 30 days after it settles. A reversal takes the amount back from the publisher's side as well, and both movements stay on the record instead of quietly disappearing.

For advertisers

Bring us a product and the step that matters

Tell us what you run, which markets you want and roughly what a completed goal is worth to you. We will come back in writing with what we can do and what we cannot.