Before you start
Name the event first, using the event naming conventions: object then action, past tense, Title Case (Product Viewed). If the name isn’t right, fix it there before it reaches the plan.
Add an event
- Add a row at the bottom of the table.
- Name the event exactly as the naming conventions produce it. Reuse an existing name if the event already exists; don’t create a second name for the same action.
- Fires when…: describe the one action or condition that triggers the event, in plain language. “A user opens a product detail page,” not “product page stuff.”
- Additional notes: add anything a developer needs to implement it, such as dedup rules, aliases, or edge cases. Leave blank if there’s nothing to add.
- Relevant?: mark
Yes,No, orMaybe. - Biz goal: name the outcome the event supports, such as
Drive sales. - Properties: list each property in
Prop name, its data type inType, and its meaning inProp description. Keep all three columns in the same order so each property lines up across them.
Keep it consistent
- One event, one row, one name. If two rows describe the same action, merge them.
- Use the same property name everywhere it appears.
product_idin one event andproductIdin another are two different properties to your analytics tools. - When an event changes, update its row in the same edit. A plan that lags the code is worse than no plan.
Event names come from the event naming conventions. Define the naming rules there, not in the plan.
Related resources
MCP wiring
MCP wiring
Type: process
Domains: tracking
Provides:
Uses:
Domains: tracking
Provides:
process:event-trackingUses:
library:event, naming-conventionTriggers: “add an event to the tracking plan” · “track a new conversion”Asks, in order:- What object and action (past tense)? Options:
naming-convention(event naming). Skip when: name given. - What exactly triggers it? Options: your answer. Skip when: given.
- Which business goal does it support? Options: your answer. Skip when: given.
- Properties (name, type, description)? Options:
options:property-type. Skip when: existing event reused.
Get the complete Marketing OS
Subscribe to Snow Doughnut, our free weekly newsletter, and get the Notion workspace where you do the work: tasks, a marketing calendar, name generators, briefs, and more.
Have us run it for you
We implement this system, use it to help you grow and scale, then hand it all off to you when you’re ready.