The tracking tax on activation work

Every property on an activation event has a cost. Someone must name it, implement it, QA it, and remember what “null” means six months later. We call that cost the tracking tax. Unpaid, it shows up as engineering quietly skipping the 30-day backlog you wrote in a workshop.

Activation KPI Design fails more often from tax than from bad theory. Teams leave a studio with a beautiful tree and a contract that asks for eighteen properties on first_value, including campaign IDs, device thermal state, and three experimental flags. No mobile squad will ship that between releases.

What belongs on the activation event

We allow a short list: user id already in the identify call, a boolean for whether the action met the inclusion rule (amount threshold, second distinct counterparty), platform, and an app version. Source or campaign can live on a user property set at install, not on every activation fire. If you cannot debug the KPI without a property, keep it. If you only want it “in case,” drop it.

QA is part of the tax

An event that cannot be verified in a staging build is not an event. In Event Taxonomy for Activation we require a test account recipe: the taps that should fire, and the taps that must not. If QA cannot run that recipe in fifteen minutes, the trigger sentence is still too vague.

Thailand adds a practical wrinkle: many apps wrap Mini Apps or WebViews. Firing the same first-value event from native and from a WebView without a surface property will double-count. That is one of the few extra properties we insist on when the architecture requires it — and we still keep the rest of the contract thin.

The 30-day backlog rule

The flagship studio ends with five events or fewer for the next thirty days. That cap exists because of the tracking tax. A longer list signals that the tree is still a wish. We would rather you ship three honest events than instrument a forest you will not look at.

If your data team wants a warehouse-perfect schema, that work can proceed in parallel. It is not the activation contract. Mixing the two is how analytics roadmaps swallow product time and still leave Friday without a number.