Platform · Measurement
Conversion Tracking on Reacheffect
Send the click ID out with the click and the conversion back with a postback. Reacheffect attributes every sign-up, deposit or sale to the exact source it came from, so whitelists and bids are built on conversions, not guesses. Setup steps are in the docs.
Why track conversions on an ad network
Without conversions in the platform, you can only optimize on clicks and CTR, which tells you which sources are curious, not which ones buy. With the postback live, each source ID, GEO, device and creative shows conversions and cost per conversion, and the platform can run SmartCPA toward the goal you set. On a network where you hand-pick sources, this is the data the picking is done with.
How the postback works
- Add the click ID to your URLAppend
cid=[tracking]to the campaign landing URL. Reacheffect replaces[tracking]with a unique ID on every click and your tracker or landing page stores it. - Fire the postback on conversionWhen the visitor converts, your tracker or CRM calls the Reacheffect postback URL server-side with that click ID, and optionally the payout amount.
- Read the resultsThe conversion appears against the click's source ID, GEO, device, OS, browser and creative in reports within minutes, and SmartCPA campaigns use it to optimize.
The exact postback URL, parameter names and a test procedure are in Postback setup. Because the call is server-to-server, it is not affected by ad blockers, cookie restrictions or in-app browsers.
Trackers and direct integrations
Any tracker that supports S2S postbacks works: pass the Reacheffect click ID into the tracker's own click ID parameter and map the tracker's postback template to the Reacheffect postback URL. Advertisers without a tracker fire the postback from their own backend or CRM at the moment the conversion is recorded. Managed accounts can ask their manager to verify the postback before the first campaign launches.
What to send back
| Event | Send when | Why it matters |
|---|---|---|
| Lead / sign-up | The visitor completes registration | Fast signal for source whitelisting on every vertical |
| Deposit / purchase | First payment is confirmed | The event most iGaming, betting, finance and e-commerce campaigns optimize toward |
| Install / subscription | The app installs or the subscription starts | VPN, utilities, mVAS and dating funnels |
| Payout value (optional) | With any event | Lets reports show revenue and ROI per source, not just conversion counts |
- One conversion per click by default. Repeat postbacks with the same click ID are recorded once unless your account is set to accept multiple events.
- Postbacks are attributed to the click, not the session. If your funnel spans several days, store the click ID with the user record and fire the postback when the event happens.
- Test before you scale. Fire a test postback from the docs procedure and confirm it appears in reports before raising budgets.
Conversion tracking FAQ
Does Reacheffect use a pixel or a postback?
A server-to-server postback. The click ID is passed on the campaign URL with cid=[tracking] and returned by your server when the conversion happens.
Which trackers are supported?
Any tracker or CRM that can fire a server-side URL with a click ID. Pass the Reacheffect click ID into your tracker and map its postback template to the Reacheffect postback URL.
Can I send the payout amount?
Yes. The payout parameter is optional; when it is sent, reports show revenue per source alongside conversions.
What is SmartCPA?
Is tracking extra?
No. Conversion tracking is part of every advertiser account, self-serve or managed.
Optimize on conversions, not clicks
Every account includes S2S postback tracking with source-level attribution.