Click ID out, revenue back
How a tracker joins a click bought on Meta to the revenue it later earned on a search feed, and tells Meta which clicks were worth buying.
Click ID out, revenue back
1/8
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 is that join.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
Step by step
- Two systems that never meet (Problem)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 is that join.
- A click ID goes out (Click)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.
- The ID rides along (Visit)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.
- An ad click earns revenue ($0.56)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.
- Revenue comes back as a postback (Hours later)The provider sends the figure to the tracker by postback 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.
- The tracker closes the loop (Match)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.
- Meta is told what the click was worth (Signal)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.
- The algorithm hunts for more (Learn)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.