Tracking & personalization notes on what a beacon sends, what a browser reveals, and how those signals change a page. The order of this list can change from topics you have actually opened, once consent is on.
Checking this browser…
Four GA4 ecommerce events on a demo notebook: view_item, add_to_cart, begin_checkout, and purchase. What the payload has to carry, how a transaction id dedupes a replay, and why consent still comes before the holiday rush.
The Agentic column is ten simulations of a loop: read what this site already knows, pick a real page, and name the rule. The llms.txt lab is where that reading starts.
What the LinkedIn Insight Tag sends from the browser, what the Conversions API adds from your server, and how click IDs, UTMs, attribution windows, and consent fit together using first-party data you already have.
Not every visit is a person. Some are crawlers, some are headless browsers, and some are scripts firing too fast to be human. Here is how this site marks those ghosts, why it keeps the rows instead of deleting them, and how the bots lab shows the count.
Clearing cookies is like taking off a name tag at a Halloween party. A browser fingerprint recognizes the walk instead. Here is what a fingerprint reads, why it ignores a Decline, how browsers push back, and how the fingerprint lab shows it without keeping anything.
How a visit becomes a segment. Eleven rules run in this browser from the viewport, the clock, stored visits, and the URL. Two of them change the home page call to action when consent is on.
Two ways a place shows up on a request: an approximate city from the network, and a precise point only you can hand over. Here's where each one comes from and how far to trust it.
A first-party cookie written by JavaScript can still disappear after about a week in Safari. Here is how that differs from a cookie set by the server, what it does to a client id, and how the cookies lab shows it.
The same page view can go to two places. Here is how a line pushed onto window.dataLayer becomes a request to google-analytics.com, and what that request carries.
A content blocker can drop the analytics script while the page's own beacon still lands. Here's how to tell the two apart, what the gap does and doesn't measure, and why first-party isn't a loophole.
What a browser reveals in one beacon: the page view body, the consent gate it has to pass, and the record that comes back from this site. Free.
The same signals that measure a visit can also change the page. A rules engine, a consent gate, and a panel that names which rule won. Free to read.