<b>Event tracking, done once and done right</b>
Six reads on the tracking plan that prevents two years of dirty data.
1. <i>The tracking plan template</i> — a Google Sheet you can copy today, with naming conventions baked in. Source: Avo open library.
2. <i>Object-action naming</i> — why "Order Completed" beats "completedOrder" forever. Source: Segment spec.
3. <i>Schema enforcement at the SDK level</i> — catch bad events before they hit the warehouse. Source: Avo blog.
4. <i>The data contract</i> — Chad Sanderson's case for treating events like APIs. Source: dataproducts.substack.
5. <i>Tracking plan governance</i> — who owns it when product and growth disagree. Source: RudderStack blog.
6. <i>Migrating a broken plan</i> — the painful but honest playbook. Source: PostHog blog.
That's the stack for this week. Forward to a teammate.
Stack Curator
@StackCurator
<b>Event tracking, done once and done right</b>
Этот пост опубликован в Telegram-канале Stack Curator. Подписаться можно по ссылке: @StackCurator.