Fire one event per step completion — tutorial_step_1_complete, tutorial_step_2_complete, etc. — and a final tutorial_complete. Don't pass step numbers as parameters. The pattern matches onboarding-completion intentionally; the two events serve different products but the funnel discipline is identical.
▸Install the React Native SDK
npm install @respectlytics/react-native
# or
yarn add @respectlytics/react-nativeJavaScript-only — no native modules, no auto-linking, no New Architecture migration concerns. Bundle size: ~14KB minified+gzipped. Works in any Expo project (managed or bare) without expo prebuild.
▸Initialize Respectlytics in React Native
// App.tsx (or App.js)
import { useEffect } from 'react';
import Respectlytics from '@respectlytics/react-native';
export default function App() {
useEffect(() => {
Respectlytics.configure({ appKey: '<YOUR_APP_KEY>' });
}, []);
return <YourApp />;
}Initialize once in your top-level component. No native config; no Info.plist or AndroidManifest changes. The SDK is Hermes- and JSC-compatible.
▸Track the event in React Native
import Respectlytics from '@respectlytics/react-native';
export function reportTutorialStep(step) {
Respectlytics.track(`tutorial_step_${step}_complete`);
}
export function reportTutorialFinish(skipped) {
Respectlytics.track(skipped ? 'tutorial_skipped' : 'tutorial_complete');
}For SaaS apps with a feature-tutorial flow, this complements (not replaces) your onboarding-completion events — the two answer different product questions.
✦Privacy & implementation notes
Common confusion: "tutorial" and "onboarding" are different events. Onboarding is account / profile setup (sign in, opt in, give consent, verify email); tutorial is feature instruction (how to play the game, how to navigate the app). Most apps have both, with different drop-off patterns. Instrument them as separate funnels.
First-day retention from tutorial completion is the most actionable single metric a games team can read — it tells you whether the introduction is doing its job. Session-grouped Respectlytics events give you the rate; per-player retention curves live in your game backend if you need them at the individual level.
The React Native SDK is JavaScript-only — no Objective-C/Swift bridging on iOS, no Java/Kotlin bridging on Android. Side effects: no react-native link, no auto-linking, no New Architecture migration concerns, no platform-channel exception surfaces. Trade-off: no access to platform-only metadata (which we don't want to collect anyway).
Works in Expo managed workflow without expo prebuild. No config plugin is required. EAS Build users: nothing to configure. This is the smoothest integration path on RN — most analytics SDKs require ejecting from managed.
⇋How this compares to other analytics SDKs
| Tutorial finish event | Firebase Analytics | Mixpanel | Respectlytics |
|---|---|---|---|
| Step number as parameter | Recommended | Recommended | Use distinct event_name |
| Time-on-step in seconds | Recommended | Recommended | Server-side derivation |
| Skip-tutorial as parameter | Recommended | Recommended | Use distinct event_name |
| Per-user tutorial completion history | Yes | Yes | Out of scope |
| Step-by-step funnel rate | Per-user | Per-user | Session-grouped |
❓Frequently asked questions
Should we differentiate skipped vs completed?
Yes, distinct event names: tutorial_complete, tutorial_skipped. The ratio is product information — a high skip rate may mean the tutorial is redundant or annoying; a low skip rate may mean it's actually useful. Either interpretation needs the two signals separated.
What about tutorials with branches (gameplay style choice, e.g. easy vs hard)?
Distinct event names per branch: tutorial_complete_easy, tutorial_complete_hard. Per-branch retention curves come from comparing subsequent retention events across the two cohorts.
Do we measure D1 retention from tutorial finish?
Session-scoped, yes — the rate of sessions emitting any meaningful event in the 24-hour window after a session that emitted tutorial_complete is your D1-from-tutorial signal. Country / platform breakdowns surface the variation.
How is this different from `onboarding-completion`?
Onboarding is account-level setup (email verification, push opt-in, profile creation). Tutorial is gameplay/feature-level instruction. Most apps have both — a sign-in flow + a how-to-use-the-app flow. Treat them as distinct, and instrument both.