<b>Event taxonomy: the schema you regret skipping</b>

<b>Event taxonomy: the schema you regret skipping</b>
Name your events badly once and you pay for years. These fix it upstream.

— <b>1. Object-action naming convention</b> — "Product Viewed," not "viewedProduct," and why consistency beats cleverness. Source: Segment spec.
— <b>2. A tracking plan template that scales</b> — the spreadsheet structure that survives a 50-person product team. Source: Avo blog.
— <b>3. Property vs event: where to put the data</b> — the decision that determines whether you can ever segment on it. Source: Amplitude docs.
— <b>4. Schema enforcement at the SDK level</b> — catching bad events before they hit the warehouse. Source: Snowplow.

Skip if your analytics is read-once dashboards. Essential before you instrument a new product.

That's the stack for this week. Forward to a teammate.