Expo analytics with session replay and heatmaps

Vexo records screens, taps, crashes, network requests, and session replays in Expo apps on iOS and Android. Install the vexo-analytics SDK, call vexo() once in your root layout, and rebuild your app. Vexo tracks Expo Router screens automatically, with no config plugin.

Vexo is an independent product. It isn't made by, affiliated with, or endorsed by Expo.

What Vexo records in your Expo app

Once vexo() runs, Vexo records the following with no more code, and shows it in the Vexo dashboard.

FeatureWhat Vexo recordsDocs
Product analyticsSessions, screens, taps, and navigation, with no tracking code. Add your own events with customEvent().Custom events
Session replayA replay of each session, up to 5 minutes on the free plan and 15 minutes on paid plans. Vexo blurs every replay frame on the device by default.Session replays
HeatmapsVexo's heatmaps show taps, per screen, app version, and device model.Heatmaps
Crash reportingVexo reports JavaScript crashes and JS-thread stalls, and links each crash to its session replay.Error triage
Network monitoringThe URL, method, status, and duration of each fetch, XHR, and axios request.Network stats
PerformanceApp start time, slow and frozen frames, and how long each screen takes to render.Performance
Release healthAdoption and crash-free sessions for each app version, or for each EAS Update.Release health

Set up Vexo in an Expo app

Before you begin, check that your app meets Vexo's requirements:

  • React Native 0.74 or later, on the New Architecture or the old architecture.
  • iOS 15.1 or later as the minimum deployment target.
  • Expo Router or React Navigation, for automatic screen tracking.
  • A development build. Vexo includes custom native code, so it doesn't run in Expo Go.
  1. Create a Vexo account and an app, and copy the app's API key.
  2. Install the SDK:
    npx expo install vexo-analytics
  3. Call vexo() at module scope of your root layout, before the layout component. The root layout is app/_layout.tsx, or src/app/_layout.tsx in the Expo SDK 58 template. On Expo SDK 58, use vexo-analytics 1.14.0 or later.
    // app/_layout.tsx
    import { vexo } from 'vexo-analytics';
    
    vexo('YOUR_API_KEY');
    
    export default function RootLayout() { /* unchanged */ }
  4. Rebuild the app, because vexo-analytics includes native code. Run npx expo run:ios or npx expo run:android, or make a new development build with eas build --profile development. A JavaScript reload or an EAS Update isn't enough.
  5. Open the app, move between two screens, and wait about 5 seconds. Then open your app in the Vexo dashboard: your device is listed under People.

For troubleshooting and every SDK call, see the Vexo quickstart, React Native integration, and Upgrading to Expo SDK 58.

Vexo in managed and bare Expo workflows

Vexo works the same way in both workflows, with no config plugin. What differs is how you install the iOS pods and build the native app. In either workflow, Vexo doesn't run in Expo Go.

StepManaged workflowBare workflow
Installnpx expo install vexo-analyticsnpx expo install vexo-analytics, then pod install in the ios folder
Config pluginNone neededNone needed
Native buildA development build or EAS Build. Expo generates the native projects, with Vexo in them, when it builds.Rebuild your native projects, for example with npx expo run:ios and npx expo run:android.
EAS UpdateShip JavaScript changes as usual. Installing or upgrading vexo-analytics needs a new build.Ship JavaScript changes as usual. Installing or upgrading vexo-analytics needs a new build.

Expo Router screen tracking with Vexo

Vexo records each Expo Router screen automatically when vexo() runs at module scope of your root layout. How Vexo follows screens depends on your Expo SDK:

Expo SDKWhat you needHow Vexo tracks screens
57 and earlierCall vexo() at module scope.Vexo attaches to Expo Router's navigation container automatically.
58 and latervexo-analytics 1.14.0 or later, with vexo() at module scope of the root layout.Vexo follows Expo Router's screen-tracking API. vexo-analytics 1.12.x and earlier record nothing on SDK 58.

To avoid relying on Expo Router's experimental or private APIs, use Vexo's explicit setup on any Expo SDK: wrap your root layout in VexoProvider and pass it useNavigationContainerRef(). It needs vexo-analytics 1.14.0 or later.

import { Slot, useNavigationContainerRef } from 'expo-router';
import { vexo, VexoProvider } from 'vexo-analytics';

vexo('YOUR_API_KEY');

export default function RootLayout() {
  const navigationRef = useNavigationContainerRef();
  return (
    <VexoProvider navigationRef={navigationRef}>
      <Slot />
    </VexoProvider>
  );
}

On Expo SDK 58 and later, Vexo records taps for heatmaps through native tap capture, which needs a native rebuild. An EAS Update alone falls back to JavaScript tap capture. See the explicit setup and Upgrading to Expo SDK 58.

Vexo with EAS Build and EAS Update

  • EAS Build. Make development and production builds of an app with Vexo in EAS Build, as you would for any app with native code.
  • Releases. On Vexo's Releases page, click Expo updates to see each EAS Update as a release, with its adoption and crash-free sessions compared with the update before it. See Release health.
  • Source maps. Upload a source map for each EAS Update with vexo-upload-sourcemaps --dist, so that crash stack traces in Vexo point at your code. See Source maps.

What to know before you add Vexo

  • Masking is whole-frame. Vexo blurs every replay frame on the device by default. No published release masks individual views yet, so keep blur on if your app shows sensitive content.
  • Crash reporting covers JavaScript. Vexo reports JavaScript crashes and JS-thread stalls; to see native crashes in Vexo, import them from Firebase Crashlytics through its BigQuery export. See Crashlytics.

Vexo pricing for Expo apps

Vexo's free plan includes 500K events and 1,000 session replays a month, with no credit card. Past the free events, you pay from $30 per additional million events, scaling down to $12/M at higher volume. For paid plans and how long each plan keeps your data, see Vexo pricing.

Frequently Asked Questions

Does Vexo work with Expo?

Yes. Vexo's SDK, vexo-analytics, records Expo apps on iOS and Android in a development build or an EAS Build, with no config plugin. On Expo SDK 58, use vexo-analytics 1.14.0 or later.

Can I use Vexo in Expo Go?

No. vexo-analytics includes custom native code, which Expo Go can't load. Use a development build instead: run npx expo run:ios or npx expo run:android, or make one with eas build --profile development.

Does Vexo need an Expo config plugin?

No. Install vexo-analytics with npx expo install, call vexo() with your API key, and rebuild the app. Vexo needs no config plugin in managed or bare apps.

Does Vexo track Expo Router screens automatically?

Yes. When vexo() runs at module scope of your root layout, Vexo records each Expo Router screen with no other code. On Expo SDK 58 and later, this needs vexo-analytics 1.14.0 or later; earlier versions record nothing on SDK 58. For a setup that doesn't rely on Expo Router's experimental or private APIs, wrap your root layout in VexoProvider and pass it useNavigationContainerRef().

Does Vexo work with EAS Build and EAS Update?

Yes. Build your app with EAS Build, and ship JavaScript changes with EAS Update as usual. Installing or upgrading vexo-analytics needs a new build, because it includes native code. On Vexo's Releases page, click Expo updates to see each EAS Update as a release, with its adoption and crash-free sessions.

How does Vexo protect sensitive data in Expo session replays?

Vexo blurs every replay frame on the device by default. No published release masks individual views yet, so keep blur on if your app shows sensitive content. You can also turn replay off with vexo('YOUR_API_KEY', { sessionReplay: false }), or let users opt out with disableTracking().

Is Vexo part of Expo?

No. Vexo is a separate product, and it isn't made by, affiliated with, or endorsed by Expo. You see your Expo app's sessions, replays, and analytics in the Vexo dashboard.

How much does Vexo cost for an Expo app?

Vexo's free plan includes 500K events and 1,000 session replays a month, with no credit card. Past the free events, you pay from $30 per additional million events, scaling down to $12/M at higher volume.

More about Vexo for Expo and React Native

Start today for free

Our free tier is the perfect starting point to try vexo. You can upgrade at any time!