Trackers, click IDs and postbacks: joining cost to revenue

A search arbitrage business has two sets of books kept by two different companies. The traffic source (Meta, TikTok, Taboola) knows what each click cost. The feed provider knows what each visit earned. Neither knows the other half. If you cannot join them, you know your total profit for the day but not which ad, audience or keyword produced it, and you cannot improve anything.

Think of a cloakroom. You hand over your coat and get a numbered ticket. Hours later the ticket, not your face, is what gets the right coat back. A Click ID is that ticket. It is handed out when the visitor arrives, carried through every page, and presented again when money shows up, so the revenue is hung on the right click.

What a tracker actually is

A tracker is software that sits between your ad and your landing page. Every ad points at a tracker link. When someone clicks, the tracker records the visit (time, country, device, which ad and placement it came from), creates a unique Click ID, and passes the visitor on with a redirect or a small script on the page. Later it receives revenue for that same ID and shows cost and revenue side by side.

1. Two systems that never meet: Meta knows who clicked the ad and what it cost; the search feed knows what was earned; neither can see the other. Without a join, the buyer cannot tell which of 500 ads is profitable. A Tracker (campaign tracking platform) is that join.
2. A click ID goes out: When a visitor taps the ad, Meta adds a unique click ID to the link. The tracker records it with the campaign, ad and cost (say $0.20), like a cloakroom ticket stapled to the visit.
3. The ID rides along: The tracker forwards the visitor to the lander and passes its own reference in a sub ID or channel ID. Whatever the visitor does on the feed is now stamped with that reference.
4. An ad click earns revenue: The visitor clicks a sponsored result. The feed provider records about $0.56 against that sub ID. At this point it is only estimated revenue.
5. Revenue comes back as a postback: The provider sends the figure to the tracker by Postback (server-to-server tracking) or reporting API. It can arrive hours late and is often reported per channel or sub ID, not per click, so trackers estimate the split. This lag is the revenue reporting delay.
6. The tracker closes the loop: The tracker matches the reference to the original click: this ad cost $0.20 and earned $0.56. That is Attribution. It can now show profit by ad, keyword, device and hour.
7. Meta is told what the click was worth: The tracker sends a conversion event with the click ID and the value to Meta through the Conversions API. No browser cookie is needed; one server talks to another.
8. The algorithm hunts for more: With values attached, Meta’s system can favour people like those who earned money (value-based bidding). The catch: it learns from estimates. If revenue is later clawed back, the machine was trained on money that never arrived.

The round trip, step by step

1. The ad click carries details inYour ad URL contains placeholders (often called macros) that the traffic source fills in: campaign, ad set, ad, placement, and the platform's own click identifier such as Meta's fbclid. These arrive as URL parameters, much like UTM parameters.
2. The tracker issues its own click IDThe tracker stores everything it was told and creates one ID for this visit. In Voluum's documentation, for example, a {clickid} token is swapped for the real value when the visitor is sent onward.
3. The ID rides along as a sub IDThe lander URL or the feed provider's link carries the click ID in a Sub ID field. RedTrack's guide for the feed provider Tonic uses subid1={clickid}. The feed provider does not care what the value means; it just stores it next to whatever the visit earns.
4. The visitor searches and clicks a sponsored resultOn the lander the visitor clicks a related search term and then a sponsored listing. That last click is the monetised click. The feed provider records estimated revenue against the stored sub ID.
5. The postback firesThe feed provider's server calls a URL on the tracker's server with the click ID and the amount. That server-to-server call is the postback. No browser, cookie or pixel is involved, so ad blockers and closed tabs do not break it.
6. The tracker reports, and passes the news onNow the tracker can show profit per ad, placement and keyword. It can also forward the revenue to the traffic source through a Conversions API, which the next lesson covers.

The tools operators use

Four names come up most often. They overlap, but they are not the same kind of product, and many teams run a tracker plus an automation layer.

Postback or reporting API?

Not every feed sends a postback per click. Many expose an reporting API instead: the tracker asks every hour or so for a table of revenue by date, Channel ID or sub ID and keyword, and spreads it over the matching clicks. Per-click postbacks are more precise. Report pulls are more common with Google-based feeds, where revenue is reported per channel rather than per visitor. Either way, the join only works if the ID you sent out is the ID that comes back.