A more private way to measure ad conversions
summary
Chrome builds an Event Conversion Measurement API that attributes ad clicks to purchases locally in the browser instead of using third‑party cookies, limiting conversion info to a small enum, adding randomized noise, and inserting a two-day delay before reports are sent. The demo uses anchor attributes plus a reporting pixel that responds with an HTTP redirect to a special URL, visible in chrome://conversion-internals, supports click‑through only today, offers local testing via flags, and runs via Origin Trials and the GitHub repo.
AI-written summary · about
chapters (6)
- 0:00Introduction to sandbox
- 1:26Current attribution flaws
- 2:55New privacy-safe approach
- 5:12API technical overview
- 7:21Demo and reporting flow
- 9:07Getting started and feedback
related talks
29mPrivacy Sandbox
27mTracing Information Flows Between Ad Exchanges Using Retargeted Ads
21mOptimising the website with Google Tag Manager
37mA Developer's Guide to Advertising
30mMeasurement in a Privacy First World
14mGustav Ernberg von Heijne at performance.sync()
49mWhat Lies Beneath: What are they really tracking and how?
15mDrive engagement and boost performance in your app with deep links