Tracking requests in plain English, decided by rules and a person
Anyone on a team can ask for a new analytics event in a sentence. A model drafts the definition, fixed rules check it, a person approves it, and it joins the tracking plan with code for engineers. Every step goes into an audit trail that nothing can edit.
No sign-up. Your sandbox is private to this browser and holds 5 requests. Nothing is sent to Jira, Confluence or Notion. A sandbox unused for 7 days is deleted, with its requests and audit trail.
- Ask: in plain words
- Draft: a model writes it
- Check: fixed rules
- Approve: a person decides
- Publish: into the tracking plan
The 60-second story
Ask
Someone in marketing asks, in plain English, for something they want to measure.
Already there
The tool shows them the plan already has it. They take the existing event, no new event is made, and the audit trail records why.
Approve
When they ask for something new, the approver decides on one screen, after ticking off any personal data or likely duplicate.
Ship
Engineers get the Segment code to send it. Everyone else gets a tracking plan entry that says what it means.
New to tracking plans?
Start with what a tracking plan is and why a team keeps one. The guide also walks a request through each step and explains the words you'll meet here.
Built in the open
The code is on GitHub. Each design decision has a written record of why it was made and what it ruled out. Three to start with:
- Duplicate detection has three tiersThe same name, the same name written differently, and a different name for the same behaviour. Who catches each, and what each may ask of a person.
- Snippets are deterministic and per surfaceNo model writes code. One approved definition gives one snippet per surface, the same every time.
- A public demo gives each visitor a private sandboxStrangers draft with a paid model, so each visitor gets a separate database, with limits that keep the demo safe to host.