Question 1

What is a tracking plan?

Accepted Answer

A tracking plan is a document that defines which analytics events your product tracks, what properties each event includes, and which platforms implement them. Ordaze replaces messy spreadsheets with a living, validated registry.

Question 2

What is analytics event management?

Accepted Answer

Analytics event management is the process of defining, versioning, and governing the events your product sends to analytics platforms. It covers naming conventions, property schemas, ownership, and implementation coverage, ensuring every team ships consistent, trustworthy data.

Question 3

Which languages do you support?

Accepted Answer

We generate type-safe tracking code for Swift, Kotlin, TypeScript, Python, and more. Each output matches the idioms and patterns native to that language.

Question 4

Can I use Ordaze with my existing analytics provider?

Accepted Answer

Yes. Ordaze works alongside Segment, Amplitude, Mixpanel, and any custom analytics setup. It generates the tracking calls, and your existing providers receive the data.

Question 5

How does the CI/CD integration work?

Accepted Answer

Add our GitHub Action to your pipeline. It validates that your code matches the tracking plan schema on every pull request, catching mismatches before they reach production.

Question 6

Is there a free plan?

Accepted Answer

Yes. The Free plan includes up to 100 events, 2 members, and full code generation. It's perfect for side projects and trying Ordaze before committing.

Question 7

How does Ordaze help with data governance?

Accepted Answer

Ordaze centralises your event definitions and enforces them at the code level. Every event has an owner, a schema, and a version history. Breaking changes require a new version, creating an audit trail that satisfies data governance requirements.

Question 8

What is event coverage scanning?

Accepted Answer

Coverage scanning analyses your codebase to check which events from your tracking plan are actually implemented, and which are missing or mismatched. The Ordaze scanner runs in CI or locally and reports results directly to your dashboard.

Question 9

How does version control for tracking plans work in Ordaze?

Accepted Answer

You publish immutable versions of your event registry, just like software releases. Each version snapshots all event definitions and properties. Teams can compare versions, see what changed, and roll back if needed, giving product and engineering a shared source of truth.

Question 10

Can multiple teams collaborate on a tracking plan?

Accepted Answer

Yes. Ordaze supports role-based access with Owner, Admin, Editor, and Viewer roles. Product managers can define event requirements, engineers can review and implement them, and analytics teams can audit coverage, all within the same workspace.

Question 11

Does Ordaze support mobile analytics (iOS and Android)?

Accepted Answer

Yes. Ordaze generates native Swift files for iOS and Kotlin files for Android, with the same event definitions. The coverage scanner auto-detects your platform and scans the appropriate source files.

Question 12

What analytics providers does Ordaze integrate with?

Accepted Answer

Ordaze is provider-agnostic: it generates the tracking calls and your existing provider (Segment, Amplitude, Mixpanel, Firebase, or custom) receives the data. There is no vendor lock-in.

Question 13

How do I get started with Ordaze?

Accepted Answer

Sign in with Google at app.ordaze.com, create a workspace, and define your first events. Then publish a version, generate an API token, and run the scanner CLI in your repository. The quickstart guide walks you through each step in under 10 minutes.

Question 14

What is type-safe analytics code generation?

Accepted Answer

Type-safe code generation produces tracking helper files (Swift enums, Kotlin data classes, TypeScript interfaces) directly from your event registry. Because the types are derived from the schema, the compiler catches mismatched property names or types before the code ships.

Question 15

How does Ordaze handle breaking changes to events?

Accepted Answer

Adding or removing required properties is a breaking change. Ordaze flags these when you publish a new version and the CI scanner blocks merges that would violate the current schema, so downstream consumers always know what to expect.

Question 16

Who is Ordaze for?

Accepted Answer

Ordaze is built for product teams, engineering teams, and analytics teams that need to collaborate on analytics event tracking. It's especially useful for companies with multiple platforms (iOS, Android, web, backend) where inconsistent event naming creates data quality problems.

What is a Super Properties?

Related terms