Change management

How analytics events are proposed, approved, documented, and retired.

Propose a new event

1. Submit the proposal as a ticket.
2. Include the business justification and every proposed property.

Get it approved

1. The data team reviews and approves new event proposals each sprint.
2. Engineering estimates the implementation effort.

Document it

1. Update the tracking plan before implementing. These pages are the source of truth.
2. Make every change through a pull request to this repo, and get it reviewed.

If we upgrade our Segment plan in the future, Segment's Protocols > Tracking Plans feature offers versioned technical and contextual documentation inside the Segment UI. That would help both engineers and data users, such as marketing.

Deprecate an event

1. Mark the event as deprecated: add [DEPRECATED] to its page title and a warning box explaining what replaces it.
2. Give 30 days' notice before removing the event.

Contacts

For questions about this tracking plan:

• Event strategy: Data Engineering
• Event implementation: Software Engineering

Related pages

• Analytics tracking plan
• Implementation guidelines