Neil Black · Powering Personalization through Digital Collection
Neil Black · Powering Personalization through Digital Collection
Demystify how digital metrics are collected.
A page already knows a lot before anything is sent: what the browser can see, which requests it makes, and what a first-party beacon looks like when it arrives. Those same signals can change this page, once you allow it.
Checking this browser…
Why am I seeing this?
Rules run in this browser. Consent decides whether they change the page.
Checking this browser…
Three places a metric actually lives
Notes
- What the server adds to a beaconThe body that leaves the browser is not the record that gets stored. Receipt time, a parsed user agent, and edge headers are added on the way in.serverbeacons
- Personalization from the same signalsThe signals used to measure a visit can also change the page. A small rules engine, a consent gate, and a panel that says which rule fired.personalizationconsent
- What a browser can reveal on page loadBefore a beacon is sent, the load has already produced a timeline, a request list, and a set of client signals. Here is what that record contains, and what it does not.browsercollection