By Ryan Richardson · Published 8 October 2026
First-party event tracking is step 43 (Part VII, Instrument it), marked hard difficulty and almost nobody does this in the matrix, the strongest coverage flag in this whole part of the book.
A pixel is the platform's own code on a page, reporting what its own clicks did. It's their instrument, not the business's, and it is blocked by many browsers by default. An event log is a different object entirely: an append-only table the business owns, independent of any platform, one row per event.
Twelve events answer almost any question asked of a funnel later: landing view, call-to-action click, engagement, scroll depth, checkout mounted, checkout step, bump toggled, exit intent, upsell viewed, upsell declined, thank-you reached, download taken. The first four to build, before the rest, are page view, checkout start, purchase and upsell purchase.
The collector accepts a short, fixed list of event names and is loud whenever it rejects one. An event added to a page but not to that accepted list gets dropped silently, which is a month of missing data nobody notices until someone goes looking.
Every new meaning gets a new field name, which is why the log is append-only rather than edited in place.
An independent, append-only event log running the first four events, each one carrying a session identifier, a timestamp, and (where relevant) the variant assignment. The collector rejects anything off its accepted list loudly rather than silently.
Adding an event to a page without adding it to the collector's accepted list first, which drops it with no warning. Firing events on page exit and relying on them arriving, when exit events often never do.
| Claim | Value | Source |
|---|---|---|
| Full event set vs. starting set | twelve target events; first four to build are page_view, checkout_start, purchase, upsell_purchase | Measured in Real Money, Field Manual |
| Matrix status for this step | Hard difficulty, almost nobody does this, automated tooling | The Sixty Steps matrix |