The event registry your whole team will actually use
Ordaze's tracking plan gives every analytics event a structured schema, full version history, and a single authoritative source of truth, keeping product, engineering, and data teams are always aligned.
Structured Event Schemas
Define every event with name, description, properties, types, enums, and required flags. No free-form text fields.
Full Version History
Every schema change is recorded. See who changed what, when, and why, and roll back to any previous version.
Team Collaboration
Product, engineering, and data teams all work from the same registry. Everyone sees the same schema, always up to date.
Connected to Code Gen
The tracking plan feeds directly into code generation. Change a schema, regenerate your SDK - always in sync.
Define events with structure, not a spreadsheet
Every event in Ordaze has a machine-readable schema. Properties are typed: string, number, boolean, or enum with explicit valid values. Required fields are marked required, not just described as such in a comment.
This structure is what enables everything else: type-safe code generation, schema validation in the scanner, and reliable downstream data in your warehouse.
- Event name, slug, and description
- Properties with names, types, and descriptions
- Required vs optional field markers
- Enum types with explicit valid values
- Platform scope: iOS, Android, web, backend
- Owner and category metadata
Track every change to every event
Every time a schema is updated (a property added, renamed, or removed), Ordaze records who made the change, when, and what changed. You always have a complete audit trail.
When a data analyst asks “when did the amount field change?” or “why is this property missing from older data?”, you'll have the answer in the version history.
One registry, used by everyone
The tracking plan in Ordaze is the canonical reference for your analytics. Product managers define events here. Engineers generate code from it. The scanner validates against it. Data analysts look it up when they need to understand a property.
No more hunting through old Notion docs, asking Slack channels, or hoping the README is current. The tracking plan is always the most accurate source.