Add analytics to Expo.

const host = 'https://YOUR-INSTANCE';
const key = 'WRITE_KEY';

export function track(name: string, distinctId: string, properties: Record<string, unknown> = {}) {
  return fetch(`${host}/v1/events`, {
    method: 'POST',
    headers: { 'Content-Type': 'application/json', Authorization: `Bearer ${key}` },
    body: JSON.stringify({ name, distinct_id: distinctId, properties }),
  });
}

// batch on background: POST an array to the same endpoint
// import { AppState } from 'react-native';
// AppState.addEventListener('change', s => { if (s !== 'active') flushQueue(); });

No Expo config plugin needed and no native rebuild. fetch is built in, so this works in the managed workflow and in Expo Go. Call track from an Expo Router or React Navigation listener.

Drop track() into an Expo Router segment effect or a React Navigation screen listener so every screen logs a screen_view with the route name, and call it on the taps that matter (signup, purchase, invite). Use a stable distinct_id, the user id after login and a persisted install id before, so one person threads across screens without any native code.

Keep requests low on device. Queue events in an array and flush a batched JSON POST to /v1/events on an interval or when AppState leaves active. It is the identical endpoint and write key your web build and backend use, so a user who moves between mobile and web stays one profile, and you can ask in plain English which step of onboarding leaks.

Honest pricing: 14-day full trial, no credit card. Then Solo $29/mo, never metered on seats or sites. Overage is $5/million with an emailed receipt, the dashboard never locks, and self-hosting the single Go binary is free forever (MIT).

questions