Mitr Analytics Documentation

Everything needed to wire up privacy-first, zero-PII analytics — whether you're integrating by hand or handing this to an AI coding assistant.

Using an AI assistant (Claude, ChatGPT, Copilot, Cursor)? Point it at the AI Integration Guide — it's written specifically to be pasted into a chat or read by an agent, and includes a plain-text version at /docs/ai-integration.md for tools that fetch raw markdown. See also /llms.txt for the full machine-readable index of this site.

Where to start

Quickstart — get a Site ID and drop in one snippet.
JavaScript SDK — for websites: plain HTML, React, Next.js, Vue, no-code builders.
Flutter SDK — for iOS, Android, desktop, and Flutter Web apps.
React Native SDK — for bare React Native and Expo dev-client apps.
Swift SDK — for native iOS, macOS, tvOS, and watchOS apps.
Kotlin SDK — for native Android apps.
Node.js SDK — for backends, webhook handlers, cron jobs, and CLI tools.
Tracking Pixel — for email and pages that can't run a script at all.
Funnels — track drop-off across a multi-step journey, even across a website and a mobile app.
Traffic Alerts — get notified by email, webhook, or Slack when your traffic spikes or drops.
Webhooks — send events to Slack, a CRM, or your own backend in real time.
AI Integration Guide — hand this to a coding assistant to do the integration for you.
API Reference — the ingestion contract, for anyone integrating without an SDK.

Design principles

Zero/low dependency — the JS, Node.js, and pixel-builder SDKs have none at all; the Flutter SDK only dio, crypto, and shared_preferences; the React Native, Swift, and Kotlin SDKs use only their platform's own frameworks and required peers.
Asynchronous — every network call is non-blocking and never throws into your app.
Resilient — events are batched, persisted locally, and retried; a reload, app kill, or offline period doesn't lose queued events.
Privacy-first — no PII collected by default; user identifiers are hashed client-side before ever leaving the device.