Tracking Plan

A tracking plan is a shared specification for the events an application should collect. It connects an analytical question to an observable trigger and the fields needed to interpret it. A list of event names alone does not establish when a record should be emitted.

For checkout_started, specify whether opening the checkout again is a new attempt or the same cart. Define the cart or attempt key, amount unit and included charges, required properties, source, version, owner and known consumers. Reusing an event ID for a network retry cannot prevent a new ID created by a second screen opening.

Review changes with producers and consumers, generate or maintain validation rules, and test the deployed app. Compare expected actions with collected events and source orders. A valid record does not reveal an event that was never sent; retain ownership and monitoring after release.

Reference: Segment tracking plans.