A tracking plan can list every event and still leave the business without a useful answer. The missing part is often the decision: who will use the data, which action they can take, and what evidence would change that action. A measurement strategy connects those parts before anyone builds tags or a dashboard.
Start with an action someone can take
“Understand our customers” is too broad to guide an implementation. “Decide whether to fund a checkout repair before the next release” gives the work a boundary. Record the decision owner, the available choices, the date of the decision, and the evidence needed. Include “do nothing” and “investigate further” when both are real options.
Use that record to test each request for data. Ask which choice could change if the number changed. A field with no answer may belong in a later investigation. This keeps the strategy separate from the tracking specification: the strategy explains the decision and its limits; the specification defines events, fields and implementation rules.
Trace the business outcome to its source
An order, an invoice and a payment are different records. For this checkout decision, define success as a paid order, with cancellations and refunds treated consistently. The order system can supply order status. Payment records can confirm settlement. Finance can define contribution after the agreed variable costs. Browser events can help locate where the process fails.
Google’s ecommerce documentation defines begin_checkout, purchase and refund events for different shopping actions. That event structure helps describe behaviour, but it does not set your accounting definition. State when the website sends purchase and how refunds reach reporting. A confirmation page event cannot, by itself, prove that an order remains paid after returns.
Google defines a key event as an action important to business success. Marking an event as key changes how you report it; it does not validate the action’s commercial value. For each outcome, record the source, identifier, time zone, currency and update delay. Define how to remove duplicates and which records cannot be matched. Keep unmatched records visible rather than silently dropping them.
