Conversion
A conversion is the target action an advertiser or network pays a buyer for — an install, a registration, a deposit, a completed order. The exact definition of what counts as a conversion is set by the offer's terms, not by the buyer.
How conversions get confirmed
The event is usually confirmed on the advertiser's side (the offer's own server) and passed to the tracker or ad platform through an S2S postback — that's what keeps a conversion safe from client-side tampering. It's worth confirming the exact definition with the offer upfront: 'deposit,' for instance, might mean any amount or only amounts above a minimum threshold.
Conversions in PWA arbitrage
A PWA has no classic store-install event — instead, what gets tracked is the home-screen add and subsequent in-app actions (registration, deposit), confirmed by the offer via postback. APEX's postbacks/S2S pass those events to the tracker and ad platform (for example, via a Keitaro↔FB CAPI link) with the needed precision, reducing the odds of disputes with the advertiser over what counted as a conversion and when.
FAQ
- What if a buyer's and an offer's conversion counts don't match?
- Cross-check postback logs from both sides by timestamp and sub-ID — mismatches almost always come down to either postback delay or a different event definition (say, 'registration' vs. 'confirmed registration').
- Can you trust conversions counted without a postback?
- Without S2S confirmation from the offer, conversion data is provisional — final payout is almost always calculated from the advertiser's own records, not the buyer's client-side analytics.
Cloaking, anti-bot, push, split tests and your own domains — in one service.
Get started free