React Native and Expo analytics with revenue

One TypeScript file, no native code. Screens, events and sign-ins from your app, next to your website's visitors and the money they bring.

Open the live demo Get early access

What Sumly reads

Screens, from React Navigation or Expo Router
Events with properties, such as signup or upgrade
Who the person is once they sign in
App version, platform, device and country

Good to know

A person keeps one id across launches when @react-native-async-storage/async-storage is installed.

Add it to your app

One file, no native code. Download sumly.ts into your app, and add @react-native-async-storage/async-storage so a person keeps one id across launches.

import { Sumly } from './sumly';

Sumly.init({ siteKey: 'sl_…', appVersion: '1.0.0' });   // once, at start

// React Navigation
<NavigationContainer onStateChange={Sumly.onNavigationChange}>
// Expo Router
const path = usePathname(); useEffect(() => Sumly.screen(path), [path]);

Sumly.track('signup', { plan: 'pro' });
Sumly.identify({ id: user.id, email: user.email, name: user.name });

One file, no dependencies. Add Sumly.swift to your app target.

// App.init or application(_:didFinishLaunchingWithOptions:)
Sumly.configure(siteKey: "sl_…")

// SwiftUI: counts the view as a screen each time it appears
HomeView().sumlyScreen("Home")
// UIKit
Sumly.screen("Home")

Sumly.track("signup", props: ["plan": "pro"])
Sumly.identify(id: user.id, email: user.email, name: user.name)

One file, no dependencies. Copy Sumly.kt into your app module.

// Application.onCreate; autoScreens counts every Activity as a screen
Sumly.init(this, siteKey = "sl_…", autoScreens = true)

// Compose or fragments: name the screens yourself
Sumly.screen("Home")

Sumly.track("signup", mapOf("plan" to "pro"))
Sumly.identify(id = user.id, email = user.email, name = user.name)

// Campaign links: the Play install referrer becomes the app's source
Sumly.setInstallReferrer(referrerDetails.installReferrer)

Where a checkout starts, pass the visitor so Sumly traces the payment to the visit that started it: the site's sumly_vid cookie, or the app's Sumly.visitorId. Put it in Stripe's metadata as sumly_visitor_id: on the subscription for plans, on the payment for one-off sales.

// Node
await stripe.checkout.sessions.create({
  // …your line items, success_url and so on
  subscription_data: { metadata: { sumly_visitor_id: req.cookies.sumly_vid } },
  payment_intent_data: { metadata: { sumly_visitor_id: req.cookies.sumly_vid } },
});

// Laravel Cashier (and add sumly_vid to encryptCookies except)
$user->newSubscription('default', $price)->withMetadata(['sumly_visitor_id' => request()->cookie('sumly_vid')])->checkout();

// RevenueCat, in the app
Purchases.shared.attribution.setAttributes(["sumly_visitor_id": Sumly.visitorID])