
Consent Mode
Consent mode explained — the mechanism that communicates a user's consent state to tags, and why one vendor's flag does not control every platform.
2 min readBlog
Field notes and research on paid media, memory, and the difference between a number and a decision.
124 posts in Reference

Consent mode explained — the mechanism that communicates a user's consent state to tags, and why one vendor's flag does not control every platform.
2 min read
Server-side conversion tracking explained — sending authoritative outcomes from your server or CRM, and why it does not mean sending everything twice.
3 min read
Conversion event explained — the specific action an ad platform records as a tracked outcome, and how it differs from a page view.
2 min read
Standard event explained — the predefined conversion events each ad platform supports, and why they are usually safer than custom names.
2 min read
Custom event explained — a non-standard event name for a genuinely distinct action, and where platforms limit what it can optimize.
2 min read
Custom conversion explained — a rule that classifies received activity into a conversion definition for reporting and, where supported, optimization.
2 min read
Website pixel explained — the browser tag that observes page context and events, and what it can and cannot prove on its own.
2 min read
Conversion value explained — the monetary value attached to a conversion for value-based bidding, and why arbitrary values mislead the algorithm.
2 min read
Conversion counting explained — the once-per-interaction vs every-occurrence setting that decides how many conversions one action produces.
2 min read
Transaction ID explained — the stable, unique order identifier that prevents purchases from being double-counted on reload.
2 min read
Event ID explained — the value that lets platforms recognize the same conversion across browser and server delivery for deduplication.
2 min read
Event deduplication explained — how shared event names and IDs stop one business action from being counted twice across the Pixel and server.
2 min readThe record
Stop running an account that forgets.
Bring captured changes, performance, and business context together for the next review.