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

All 13 of Swift, Kotlin, TypeScript, Python, Java, JavaScript, C#, Go, Rust, Ruby, PHP, Dart, and React Native ship with default codegen templates. Each output matches the idioms and patterns native to that language and is fully customizable via Handlebars.

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, unlimited team 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.

Question 17

What counts as a tracked event?

Accepted Answer

A tracked event is any unique analytics event defined in your tracking plan. For example: ButtonClicked, PageViewed, or PurchaseCompleted. The limit applies to the total number of distinct event definitions, not to the number of times an event fires in production.

Question 18

What happens when I hit the event limit?

Accepted Answer

You can still view and manage your existing events. Adding new event definitions will require upgrading to a higher plan. Your existing code generation and CI/CD integrations continue to work uninterrupted.

Question 19

Can I switch plans at any time?

Accepted Answer

Yes. You can upgrade instantly and the new limits take effect immediately. Downgrades take effect at the end of your current billing cycle.

Question 20

Is there a free trial for paid plans?

Accepted Answer

Yes. New signups get 14 days of full Pro access automatically, no credit card required. After the trial, you continue on the Free plan (1 workspace, unlimited members, 100 events) with no time limit unless you choose to upgrade.

Question 21

Do I need a credit card to start?

Accepted Answer

No. The Free plan requires no credit card and has no time limit. You only enter payment details if you choose to upgrade to Pro or Team.

Question 22

What happens to my data if I downgrade?

Accepted Answer

Your events and tracking plans are never deleted. If you exceed the lower plan's event limit, existing events stay intact but you will not be able to create new ones until you reduce usage or upgrade again.

Question 23

Are there any long-term contracts?

Accepted Answer

No. Both Pro and Team are billed monthly with no annual commitment required. You can cancel at any time and your plan stays active through the end of the billing period.

Question 24

Do you offer discounts for annual billing or nonprofits?

Accepted Answer

Annual billing and nonprofit discounts are not available yet, but both are on our roadmap. Contact us at hello@ordaze.com and we will notify you when they launch.

Question 25

What is Ordaze?

Accepted Answer

Ordaze is an analytics event registry for product and engineering teams. It gives you a versioned tracking plan, type-safe code generation for Swift, Kotlin, TypeScript, and Python, and a static source-code scanner that runs in CI to catch drift before it ships.

Question 26

Is Ordaze open source?

Accepted Answer

The Ordaze app is proprietary, but the scanner is published as an open-source npm package and a GitHub Action at @ordaze/scanner. The scanner is what runs in your CI pipeline and on your developers' machines, so the piece that interacts with your source code is fully auditable.

Question 27

Does Ordaze need an SDK?

Accepted Answer

No. Ordaze is SDK-free. The scanner reads your source code statically on any git branch — nothing ships to production, no third-party JavaScript runs on your site, and no user data leaves your servers. You keep using whichever analytics SDK you already have; Ordaze just generates the typed wrappers you call into it.

Question 28

Does Ordaze work with Segment, Amplitude, Mixpanel, PostHog, and Firebase?

Accepted Answer

Yes. Ordaze is analytics-provider agnostic. The code generator ships default templates for Swift, Kotlin, TypeScript, and Python that you can shape around any SDK — Segment, Amplitude, Mixpanel, PostHog, Firebase, RudderStack, Snowplow, or a custom wrapper. The scanner detects analytics calls regardless of which SDK you use.

Question 29

How does Ordaze detect breaking changes?

Accepted Answer

The scanner parses your source code, matches call sites against the published schema, and flags every mismatch: missing required properties, renamed events, deprecated events still in use, and type drift. In CI, the scanner fails the pull request when a breaking change appears, so the broken event never reaches production.

Language	Output
Swift	`AnalyticsEvents.swift` — extension on `Analytics` with a static func per event
Kotlin	`AnalyticsEvents.kt` — sealed `AnalyticsEvent` class with a data object/class per event
TypeScript	`AnalyticsEvents.ts` — typed `Properties` interface + constructor function per event
Python	`analytics_events.py` — `TypedDict` properties + module function per event
Java	`AnalyticsEvents.java` — final class with a static method returning `Event` (boxed primitives, `Map<String, Object>`)
JavaScript	`analyticsEvents.js` — `module.exports` of per-event factory functions with JSDoc-typed parameters
C#	`AnalyticsEvents.cs` — static class + `readonly record struct AnalyticsEvent` envelope (C# 10+)
Go	`analytics_events.go` — package-level PascalCase exported functions returning `AnalyticsEvent`
Rust	`analytics_events.rs` — `#[derive(Serialize)] pub struct AnalyticsEvent` + snake_case `pub fn` per event
Ruby	`analytics_events.rb` — module with `self.` class methods using keyword args + YARD type comments
PHP	`AnalyticsEvents.php` — `declare(strict_types=1)` final class with static methods returning typed arrays
Dart	`analytics_events.dart` — class with named required/nullable parameters (Dart 2.12 null safety)
React Native	`AnalyticsEvents.ts` — same output as TypeScript (RN projects run V8/Hermes with TS tooling)

Variable	Description
{{today}}	Current date (YYYY-MM-DD)
{{eventCount}}	Total number of events
{{categories}}	Array of destination names
{{allProperties}}	Array of all property names across events

Variable	Description
{{category}}	Destination name
{{name}}	Event name in snake_case
{{camelCase}}	Event name in camelCase
{{pascalCase}}	Event name in PascalCase
{{description}}	Event description text
{{deprecated}}	Boolean, true if event is deprecated
{{hasProperties}}	Boolean, true if event has properties

Variable	Description
{{name}}	Property name in snake_case
{{camelCase}}	Property name in camelCase
{{upperSnake}}	Property name in UPPER_SNAKE_CASE
{{swiftOptionalType}}	Swift type with optional marker (e.g. String?)
{{kotlinOptionalType}}	Kotlin type with nullable marker (e.g. String?)
{{required}}	Boolean, true if property is required

Helper	Description
{{toCamelCase name}}	Convert to camelCase
{{toPascalCase name}}	Convert to PascalCase
{{toUpperSnakeCase name}}	Convert to UPPER_SNAKE_CASE
{{swiftType type required}}	Map to Swift type (String, Int, Bool, etc.)
{{kotlinType type required}}	Map to Kotlin type (String, Int, Boolean, etc.)
{{#if (eq status "deprecated")}}	Equality comparison helper
{{#if (hasItems properties)}}	Check if array has items
{{@first}} / {{@last}}	Loop boundary checks
{{@index}}	Current loop index (0-based)

Code Generation

Default Templates (13 languages)

Template System

Handlebars

Context Variables

Iterating Events

Property Fields

Helper Functions

Full Example

Complete Swift Template

Customizing in Settings