Design an event naming plan
Make behavioral events understandable to the team maintaining them.
The scenario
A trial funnel has sign_up, signup, and trial_start events created by three people.
A dictionary can define trial_started as one event after successful creation and reserve form_submitted for a separate stage.
Apply it to your own work
For each event document trigger, properties, deduplication key, owner, and a test. Keep a change log when event definitions evolve.
What to watch for
Avoid recording sensitive form inputs as analytics properties. An event's usefulness depends on its business meaning, not the amount of data it carries.
Test the event where it can fail
For a trial event, test a successful account creation, a validation failure, and a reload of the confirmation page. Only the first should count as a new trial under the proposed definition.
Record expected properties and actual output alongside each test. Keep the dictionary short enough for someone new to implement the event from scratch. If a name changes, annotate the date and retain a mapping for historical reports.
Try a related tool
Find the share of eligible visits that completed a defined action. Count at most one conversion per visit for this calculation.
