Every performance campaign depends on one thing: knowing which partner caused which result. Tracking is how that link is made. When it works, advertisers pay accurately and publishers are paid fairly. When it fails, both sides lose trust quickly.
The journey of a conversion
- The click. A user clicks a publisher’s tracking link. The link carries identifiers that say which publisher, which offer and which placement sent the user.
- The click ID. The tracking platform records the click and creates a unique click ID, which travels with the user to the advertiser’s site or app.
- The conversion. When the user buys, signs up or installs, the advertiser reports the conversion back, together with the click ID.
- Attribution. The platform matches the conversion to the original click and credits the right publisher.
Two ways to report a conversion
Pixel tracking places a small piece of code on the advertiser’s confirmation page. It fires in the user’s browser when the page loads. It is quick to set up, but it depends on cookies and can be blocked by browsers and ad blockers.
Server-to-server (S2S) postback sends the conversion directly from the advertiser’s server to the tracking platform, using the stored click ID. It does not rely on the user’s browser, so it is more accurate and harder to manipulate. For most campaigns today it is the better choice.
What sub IDs are for
Sub IDs are extra labels a publisher adds to a tracking link, such as a placement name, a campaign or a member ID on a cashback site. They let publishers see which of their own sources convert, and they let advertisers and networks spot where good or poor quality traffic comes from.
Attribution windows and duplicates
The attribution window is how long after a click a conversion still counts, for example 7 or 30 days. Deduplication decides who gets credit when a user touched several channels. Both should be agreed in writing before launch, because they change what gets paid.
A pre-launch checklist
- Run a test conversion end to end and confirm it appears in reporting.
- Check that the order value and currency are passed correctly.
- Confirm that sub IDs arrive intact.
- Agree the attribution window, deduplication rule and validation period.
- Test on mobile and in the app, not only on desktop.
In short: a click ID links the click to the conversion. Use server-to-server postbacks where you can, test before launch, and write down the rules.