What is a tracking plan?

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.

What is analytics event management?

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.

Which languages do you support?

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.

Can I use Ordaze with my existing analytics provider?

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

How does the CI/CD integration work?

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.

Is there a free plan?

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.

How does Ordaze help with data governance?

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.

What is event coverage scanning?

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.

How does version control for tracking plans work in Ordaze?

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.

Can multiple teams collaborate on a tracking plan?

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.

Does Ordaze support mobile analytics (iOS and Android)?

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.

What analytics providers does Ordaze integrate with?

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.

How do I get started with Ordaze?

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.

What is type-safe analytics code generation?

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.

How does Ordaze handle breaking changes to events?

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.

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 counts as a tracked event?

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.

What happens when I hit the event limit?

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.

Can I switch plans at any time?

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

Is there a free trial for paid plans?

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.

Do I need a credit card to start?

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.

What happens to my data if I downgrade?

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.

Are there any long-term contracts?

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.

Do you offer discounts for annual billing or nonprofits?

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.

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.

Is Ordaze open source?

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.

Does Ordaze need an SDK?

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.

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

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.

How does Ordaze detect breaking changes?

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.

Android Quickstart

Scan your Kotlin codebase, generate type-safe event sealed classes, and wire CI so bad analytics never reach the Play Store. About 10 minutes.

Create a workspace

Sign in at https://app.ordaze.com. Create a workspace for your Android app and name it after the product (e.g. MyApp Android). New signups get 14 days of Pro access automatically, no card required.

Define your first events

In the sidebar, go to Events → Add Event. Define the events your Android app fires today. Snake-case names travel well between SDKs (purchase_completed, checkout_started). Mark properties as required where the analyst will actually use them.

Once you have 3–5 events defined, go to Versions → Publish. The scanner needs at least one published version to check your code against.

Run the scanner locally

From the root of your Android project:

# Generate an API token at app.ordaze.com/settings/tokens, then:
export ORDAZE_TOKEN=YOUR_TOKEN

npx @ordaze/scanner scan \
  --platform android \
  --dir app/src/

The scanner walks every .kt and .java file, matches analytics calls against your tracking plan, and reports matched / unmatched / missing events. Nothing is added to Gradle. Nothing runs at runtime.

Generate the typed Kotlin wrapper

In the Ordaze dashboard go to Code Generation, pick the Kotlin default template, and download. Drop the generated Analytics.kt into your Android project for a sealed-class namespace on every event:

import com.yourapp.analytics.Analytics
import com.yourapp.analytics.Currency

Analytics.PurchaseCompleted(
    amount = 9.99,
    currency = Currency.USD
).track()
// Compiler enforces required properties + enum values.

Wire the GitHub Action

Drop this workflow into .github/workflows/analytics.yml so every PR blocks merges when coverage drops:

name: Analytics Coverage
on: [pull_request]

jobs:
  scan:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: ordaze/ordaze-scanner@v1
        with:
          token: ${{ secrets.ORDAZE_TOKEN }}
          platform: android
          strict: true
          min-coverage: 80

Store your token as ORDAZE_TOKEN in Settings → Secrets and variables → Actions. With strict: true + min-coverage: 80, any PR that drops coverage below 80% or adds an unknown event will fail the check.

Next Steps

Scanner CLI

All flags, CI integrations, supported SDK patterns

Code Generation

Customize the Kotlin template with Handlebars

iOS

API Reference