Event tracking plan

Each row is one event. Name it using your event naming conventions (object then action, past tense: Product Viewed). List each property inside the cell, one per line, and keep Prop name, Type, and Prop description in the same order so the rows line up. See the event tracking plan overview for how to add a new row.

Name	Fires when…	Additional notes	Relevant?	Biz goal	Prop name	Type	Prop description
Product Viewed	A user opens a product detail page	Fires once per page load, not on every scroll	Yes	Drive sales	product_id sku name price currency	String String String Number String	Unique product identifier Public-facing stock code Product display name Price in smallest currency unit ISO currency code

Column reference

Use this to fill each column consistently.

Column	What goes in it
Name	The event name, from your naming conventions: object then action, past tense, Title Case (`Cart Viewed`).
Fires when…	The exact user action or system condition that triggers the event, in plain language.
Additional notes	Edge cases, dedup rules, aliases, or anything a developer needs to implement it correctly.
Relevant?	Whether this event is in scope for your plan: `Yes`, `No`, or `Maybe`.
Biz goal	The business outcome the event supports (for example, `Drive sales`, `Reduce churn`).
Prop name	Each property sent with the event, one per line.
Type	The data type for each property, in the same order: `String`, `Number`, `Boolean`, `Array`, `Object`.
Prop description	What each property means, in the same order as the names above it.

Event naming conventions The pattern each event name follows.
Event library Where the finished plan is filed.
Set up tracking The full tracking path.
UTM standards The other half of the tracking setup.
Data dictionary Where these events become defined metrics.

Overview

Registers

Column reference

​Column reference

​Related resources

Column reference

Related resources