← Everyone's take

TAKES · Alex answers

What should we track?

What should we track?“One typed tracking plan. Every event generated from the schema.”Alex Chen, The Architect

💡 WHY ALEX IS RIGHT

Most analytics rot starts with event names typed by hand in four clients: checkout_started, checkoutStarted, Checkout Started. A single versioned tracking plan, with types and owners, generated into web, iOS and backend code, makes every event mean the same thing everywhere. It turns analytics from a pile of strings into a contract, which is the only form that survives the third team and the second vendor migration.

✅ RIGHT WHEN

Several clients and teams send events, and decisions already depend on the numbers.

🚩 TOO FAR WHEN

Adding one button needs a schema PR, a data-team review and a codegen release.

See all 12Alex's profile