demo · v132
What ad-tech can actually attribute now
An ad-tech attribution pipeline reads four fields per beacon: timestamp, source page (Referer), event payload, joinable user id. Pre-v132 the Referer was empty, so attribution joined on the user id alone — brittle and fewer cross-publisher signals. With the Referer in place, the pipeline gets a publisher slot too.
1. fenced frame
A buyer's ad renders in a fenced frame inside news.example.
auction idPA-9921
ad creativead-banner-3
2. beacon HTTP request
window.fence.reportEvent fires; browser builds the request.
Originhttps://news.example
Referer-
body.eventData{"slot":"footer"}
3. ad-tech ingest
Beacon hits buyer.adtech.example/r. Pipeline parses each field.
host (from Referer)-
path (from Referer)-
4. attribution row
Row written to the impressions table for nightly join.
publisher_host-
publisher_page-
creativead-banner-3