Bonds Analytics Catalog

Comprehensive reference for all Mixpanel tracking in the Bonds app. Module: src/utils/analytics.js.

For product: This document lists every event, property, user attribute, and funnel tracked in the app. Use the table of contents to navigate.

For developers: When adding or changing events, update this document in the same PR. See the Developer Checklist at the bottom.

Table of Contents

1. Conventions
2. Identity & Properties
3. Screens
4. Domain Events
5. Element Clicked Reference
6. Funnels
7. Recommended Mixpanel Reports
8. Developer Checklist

1. Conventions

Naming Rules

When to Use Which Event Type

Property Value Enums

2. Identity & Properties

2a. Identity Lifecycle

┌─────────────────┐     identifyUser()      ┌──────────────────┐
│    Anonymous     │ ─────────────────────→  │   Authenticated  │
│  (random ID)     │                         │  (Bubble user ID) │
│  user_type:      │                         │  user_type:       │
│   'anonymous'    │     resetIdentity()     │   'authenticated' │
│                  │ ←─────────────────────  │                   │
└─────────────────┘                          └──────────────────┘

2b. Super Properties

Auto-attached to every event. Set by initAnalytics(), updated by identifyUser().

2c. People Properties (User Profile)

Stored on the Mixpanel user profile. Visible in the People section.

Cohort tag: the A/B/C payments cohort's source of truth is the Bubble User field payment_variant (Statsig only seeds it once — see docs/statsig-experiments.md). It's written to the Mixpanel user profile as the payment_variant People property (the effective value incl. admin overrides, set by <PaymentVariantSeeder>) — use this for all cohort filtering and breakdowns. It's a People (not super) property because the cohort is sticky and server-owned: a profile property survives reset(), is queryable on the user level, and is still segmentable in event reports, with no need for an at-event snapshot. The raw Statsig bucket is not mirrored to Mixpanel as experiment_payments (kept to one property to avoid confusion); Statsig retains the exposure for experiment analysis on its side.

3. Screens

All values used with Screen Viewed. Fired via screen(name) helper which calls track('Screen Viewed', { screen: name }).

4. Domain Events

App Lifecycle

App Opened

Fires once on app launch after analytics initialization.

Source: App.jsx

App Backgrounded

Fires when the app moves to the background (Natively lifecycle hook).

Source: App.jsx

App Foregrounded

Fires when the app returns to the foreground (Natively lifecycle hook).

Source: App.jsx

Logged Out

Fires when user logs out. Identity is reset after this event.

Source: App.jsx

Session Force Logout

Fires when Bubble force-logs the user out via setLoginState(false) while they were in an authenticated phase (no React-initiated logout pending). Most likely cause is the WebView losing its session cookie (_u2main) across a process restart, which triggers Bubble's "User is logged out" event server-side. Tracked into Mixpanel so we can monitor frequency and surface in retention/funnels alongside other auth events.

Source: App.jsx (in setLoginState(false) handler when source === 'bubble')

Deep Link Opened

Fires when a deep link is processed. Attribution params (if present in the URL) are spread into the event properties.

Source: MainTabs.jsx

Attribution Captured

Fires when a URL with attribution params is opened (cold start or warm start), regardless of whether a deep link route is present. Independent of Deep Link Opened.

Source: analytics.js via captureAttribution()

Authentication

Sign In Started

Fires when user initiates sign-in (OAuth or email).

Source: SignInScreen.jsx

Sign In Completed

Fires on first successful identity merge (anonymous → authenticated). Reads bonds_auth_method from localStorage to detect email auth; defaults to "oauth" for SSO.

Source: UserContext.jsx

Sign In Failed

Fires when sign-in fails (wrong password, Bubble error).

Source: App.jsx (via setSignInError)

Sign In Blocked

Fires when sign-in detects a non-existing account (UID comparison or Bubble search).

Source: App.jsx (via onSigninComplete)

Onboarding

Onboarding Step Completed

Fires after each onboarding question is answered.

Source: OnboardingFlow.jsx

Onboarding Completed

Fires when user finishes all onboarding steps.

Source: OnboardingFlow.jsx

Onboarding Abandoned

Fires when user exits onboarding via back button on step 0.

Source: App.jsx

Onboarding Resumed

Fires when onboarding session is resumed, either automatically on app reload (source: 'auto') or when user chooses to continue via the resume dialog (source: 'dialog').

Source: App.jsx

Onboarding Intro Viewed

Fires when the one-time intro video screen is mounted.

Source: OnboardingIntro.jsx

Onboarding Intro Completed

Fires when user taps the CTA after the intro video has finished playing.

Source: OnboardingIntro.jsx

Onboarding Intro Skipped

Fires when user taps the CTA before the intro video finishes (skips remaining video).

Source: OnboardingIntro.jsx

Onboarding Intro Replayed

Fires when user taps replay to watch the intro video again.

Source: OnboardingIntro.jsx

Onboarding Intro Backed Out

Fires when user navigates back from the intro screen to welcome.

Source: OnboardingIntro.jsx

Two Last Questions Shown

Fires when the "Two last questions" popup appears just before the first open question (Groups A & C only — gated by useOnboardingCoinsHidden()). PRD UI Outputs #2. The CTA emits Element Clicked { screen: 'onboarding', element: 'two_last_questions_continue' }.

Source: OnboardingFlow.jsx

Onboarding Insight Started

Fires when insight generation begins after all questions answered.

Source: OnboardingInsight.jsx

Onboarding Insight Generated

Fires when insight data is received from Bubble.

Source: OnboardingInsight.jsx

Onboarding Insight Prewatch Shown

Fires when the before-watching screen appears ("This insight usually uses 3 coins, but this one's on us" for Groups A & C; coin line hidden for Group B). PRD UI Outputs #4.

Source: OnboardingInsight.jsx

Onboarding Insight Watch Tapped

Fires when the user taps "Watch" on the before-watching screen, starting insight playback.

Source: OnboardingInsight.jsx

Onboarding Insight Playback Completed

Fires when TTS playback finishes and user taps Continue.

Source: OnboardingInsight.jsx

Onboarding Insight Playback Skipped

Fires when user taps Continue before TTS playback finishes.

Source: OnboardingInsight.jsx

Onboarding Insight CTA Tapped

Fires when user taps "Create Your Account" after insight playback.

Source: OnboardingInsight.jsx

Onboarding Insight Timed Out

Fires when insight generation exceeds the 90s timeout.

Source: OnboardingInsight.jsx

Onboarding Data Connected

Fires after signup when onboarding data is sent to Bubble for the new user.

Source: App.jsx

Onboarding Step Back

Fires when user navigates backward during onboarding.

Source: OnboardingFlow.jsx

Onboarding Mic Permission Denied

Fires when microphone permission is denied during onboarding open question.

Source: OpenQuestion.jsx

Onboarding Mic Unavailable

Fires when microphone/speech recognition is unavailable for a non-permission reason.

Source: OpenQuestion.jsx

Onboarding Speech API Unavailable

Fires when SpeechRecognition API doesn't exist on the device and dialog auto-switches to text mode.

Source: InsightOtherDialog.jsx

Signup

Sign Up Started

Fires when user initiates sign-up (OAuth or email).

Source: SignUpScreen.jsx

Sign Up Completed

Fires on successful signup. Detects email vs OAuth via bonds_auth_method localStorage flag.

Source: App.jsx

Sign Up Failed

Fires when sign-up fails (Bubble error).

Source: App.jsx (via setSignUpError)

Sign Up Blocked

Fires when sign-up detects an existing account (UID comparison or Bubble search).

Source: App.jsx (via onSignupComplete)

Email Authentication

Email OTP Sent

Fires when an OTP code is successfully sent to the user's email.

Source: SignUpScreen.jsx, SignInScreen.jsx

Email OTP Verified

Fires when user successfully verifies the OTP code.

Source: SignUpScreen.jsx, SignInScreen.jsx

Email OTP Failed

Fires when OTP verification fails (wrong or expired code).

Source: SignUpScreen.jsx, SignInScreen.jsx

Email OTP Resent

Fires when user taps resend code.

Source: SignUpScreen.jsx, SignInScreen.jsx

Password Reset Completed

Fires after a successful password reset + auto sign-in.

Source: SignInScreen.jsx

Sharing

Share Created

Fires when user creates a shareable link.

Source: InsightPlayback.jsx, SimulatorResults.jsx, ActivityView.jsx

Share Viewed

Fires when someone views a shared link.

Source: ShareViewer.jsx

Account

Account Deleted

Fires when user confirms account deletion.

Source: MainTabs.jsx (AccountInfoPage)

Onboarding Question Skipped

Fires when user skips an open-ended onboarding question.

Source: OpenQuestion.jsx

Journey

Chapter numbering convention. Two property names coexist for historical reasons, both 1-based:

• chapter — used by step-level events (Chapter Started, Chapter Completed, Journey Step Started/Completed/Abandoned, Journey Video Watched, Journey Practice Started/Completed). Value is the chapter's index from Bubble (the temp_index field).
• chapter_number — used by chapter-level / UI events (Chapter Confirmation *, Chapter Start Tapped, Chapter Step Start Tapped, Chapter Paused State Shown, Chapter Menu Opened, Chapter Menu Chapter Selected).

They agree numerically. When building a funnel across both groups, Mixpanel's "formula" column can alias one to the other.

dynamic segmentation. Every chapter-scoped event carries a boolean dynamic property (Phase 2 dynamic chapters vs predefined). Use it to split funnels and retention by chapter kind. Predefined chapters report dynamic: false; LLM-generated 3-node chapters report dynamic: true. For Simulator Session * events the property is present only when mode === 'journey'.

Chapter Started

Fires when the user pays the chapter cost (10 coins per the Coin Economy price card) via the coin gate and a new chapter begins. Not tied to a specific step — mirrors Chapter Completed.

Source: JourneyPath.jsx

Journey Step Started

Fires when a journey step begins (learn, practice, insight, or act).

Source: ChapterFlow.jsx

Journey Step Completed

Fires when a journey step finishes successfully.

Source: ChapterFlow.jsx

Journey Step Abandoned

Fires when user exits a journey step without completing it.

Source: ChapterFlow.jsx

Journey Video Watched

Fires when the learn video finishes playing.

Source: LearnStep.jsx

Journey Practice Started

Fires when user starts a practice simulator session from the journey.

Source: PracticeStep.jsx

Journey Practice Completed

Fires when practice simulator session ends with a score.

Source: PracticeStep.jsx

Chapter Completed

Fires when all steps in a chapter are done.

Source: ChapterFlow.jsx

Chapter Start Tapped

Fires when the user taps the external "START CHAPTER · N COINS" button on the journey map. This button replaces the in-bubble START for the first step of a chapter (PRD Phase 1, page 2).

Source: JourneyScreen.jsx

Chapter Step Start Tapped

Fires when the user taps the in-bubble START button on a non-first step (Practice/Insight/Act) on the journey map.

Source: JourneyScreen.jsx

Chapter Paused State Shown

Fires when the paused view is rendered the day after a chapter is completed (PRD Phase 1, page 4). Deduped by completed → next pair so a single paused session fires the event once.

Source: JourneyScreen.jsx

Chapter Confirmation Shown

Fires when a predefined confirmation card is shown. Two sources — when building the Confirmation → Start → Complete funnel, union screen ∈ { ch1_predefined_confirmation, chapter_predefined_confirmation }:

• Ch1 — embedded as the last FTUE walkthrough slide (PRD Phase 1, page 5) with screen: "ch1_predefined_confirmation".
• Ch2 / Ch3 — standalone bottom sheet shown at session start if the active chapter is an unstarted Ch2 or Ch3 and the user hasn't yet responded (PRD Phase 1, page 8 — Figma 1590:1791). Evaluated once per session; not re-triggered on chapter scroll. Uses screen: "chapter_predefined_confirmation".

Source: DrLeoWalkthrough.jsx (Ch1), JourneyPath.jsx (Ch2 / Ch3).

Chapter Confirmation Accepted

Fires when the user taps "Start Chapter" on the predefined confirmation card (Ch1 FTUE or Ch2/Ch3 standalone sheet).

Source: DrLeoWalkthrough.jsx (Ch1), JourneyPath.jsx (Ch2 / Ch3).

Chapter Confirmation Dismissed

Fires when the user taps "No thanks, later" on the predefined confirmation card.

Source: DrLeoWalkthrough.jsx (Ch1), JourneyPath.jsx (Ch2 / Ch3).

FTUE First Slide Shown

Fires when the FTUE first slide ("Generating your chapter…") is shown (PRD Phase 1, page 5).

Source: DrLeoWalkthrough.jsx

FTUE Skipped

Fires when the user taps Skip on any FTUE step. Per PRD §6, Skip now jumps to the last FTUE step instead of closing the walkthrough.

Source: DrLeoWalkthrough.jsx

Chapter Menu Opened

Fires on the OPEN transition of the chapter-list dropdown (chevron tap when the menu was closed). Does not fire on close — use the companion Element Clicked { element: 'chapter_menu_chevron' } event for bi-directional tap counts.

Source: JourneyScreen.jsx

Chapter Menu Chapter Selected

Fires when the user picks a chapter from the chapter-list dropdown. Funnels dropdown engagement → scroll navigation.

Source: JourneyPath.jsx

Insight

Insight Flow Started

Fires when an insight generation flow begins.

Source: InsightFlow.jsx · InsightStep.jsx

Insight Question Answered

Fires per insight question response.

Source: InsightFlow.jsx · InsightStep.jsx

Insight Generated

Fires when all insight questions are answered and generation is triggered. Currently only fires for type: 'learn'.

Source: InsightFlow.jsx

Insight Generation Timed Out

Fires when insight generation exceeds the timeout.

Source: InsightFlow.jsx (learn/activity) · InsightStep.jsx (journey)

Insight Playback Completed

Fires when TTS playback finishes and user taps Continue.

Source: InsightFlow.jsx · InsightStep.jsx

Insight Playback Skipped

Fires when user taps Continue before TTS playback finishes.

Source: InsightFlow.jsx · InsightStep.jsx

Insight Flow Closed

Fires when user exits the insight flow without completing playback.

Source: InsightFlow.jsx

Simulator

Simulator Session Started

Fires when a simulator session begins (freeform or journey practice).

Source: SimulatorSection.jsx

Simulator Session Completed

Fires when AI evaluation is received and results are shown.

Source: SimulatorSection.jsx

Simulator Session Closed

Fires when user manually ends a session (via close dialog).

Source: SimulatorSection.jsx

Simulator Session Retried

Fires when user retries the session from the results screen.

Source: SimulatorSection.jsx

Simulator Session Error

Fires on unrecoverable session error. For the JSON-extraction boundaries (Stage 1, Stage 3), this only fires after parse retries are exhausted — see Simulator Issue Retry / Simulator Eval Retry below for the per-attempt signal.

Source: SimulatorSection.jsx

Simulator Eval Retry

Fires per attempt when the Stage 3 evaluation JSON fails to parse and we re-fire the silent response.create on the same session. After today's tool-calling change this should be near-zero in production — the model is structurally forced into schema-valid JSON. Kept as belt-and-suspenders.

Source: SimulatorSection.jsx

Simulator Eval Retry Recovered

Fires once when a Stage 3 eval succeeds after at least one retry. Lets analytics distinguish first-try clean sessions from "drift caught and recovered" sessions, both of which otherwise look identical at Simulator Session Completed.

Source: SimulatorSection.jsx

Simulator Issue Retry

Stage 1 (issue-extraction) counterpart to Simulator Eval Retry. Same shape, same near-zero post-tool-call expectation.

Source: SimulatorSection.jsx

Simulator Issue Retry Recovered

Stage 1 counterpart to Simulator Eval Retry Recovered.

Source: SimulatorSection.jsx

Coins Deducted

Fires when coins are spent to unlock stage 2 of a freeform simulator session.

Source: SimulatorSection.jsx

Coins Gifted

Fires when the user receives a one-time coin gift (e.g. from the "Not Enough Coins" dialog).

Source: NotEnoughCoinsDialog.jsx

Activities

Activity Create Started

Fires when user initiates creating a new activity.

Source: ActivityView.jsx

Activity View Completed

Fires when user finishes viewing/listening to an activity.

Source: ActivityView.jsx

Activity View Closed

Fires when user closes an activity without completing it.

Source: ActivityView.jsx

Daily Question

Daily Question Viewed

Fires when the daily question appears on screen.

Source: DailyQuestion.jsx

Daily Question Voted

Fires when user selects an answer.

Source: DailyQuestion.jsx

Partner

Partner Connected

Fires when a partner is connected for the first time (partner_connected transitions false → true).

Source: UserContext.jsx

Payments

All payment events run on the React side via the Natively RevenueCat bridge and a direct RC REST read for entitlement state — Bubble is uninvolved.

Removed: Paywall Viewed / Paywall Dismissed — these only fired from RC's hosted paywall (EntitlementContext.showPaywall()), which has been removed. The app uses a single custom paywall (PlansScreen), tracked via Plans Screen Shown (see below).

Purchase Started

Fires when buy(packageId) is called.

• package_id (string)
• source (string)

Purchase Completed

Fires when the purchasePackage callback returns status: 'SUCCESS'.

• package_id (string)
• transaction_id (string|null)

Purchase Failed

Fires when the purchasePackage callback returns a non-SUCCESS status.

• package_id (string)
• reason (string) — error message from RC
• user_cancelled (bool) — true if reason looks like a user cancel

Purchase Restore Tapped

Fires when the user taps Restore Purchases.

• source (string)

Purchase Restore Completed

Fires after the post-restore entitlement refresh.

• became_subscribed (bool) — true if restore flipped state from non-paying → paying

Plans screen events

Custom in-app paywall at PlansScreen.jsx. Pushed from Profile → Subscription.

• Screen Viewed { screen: 'plans' } — on mount.
• Element Clicked { screen: 'plans', element_type: 'card', element: 'plan_<label>' } — when a plan row is selected (<label> = key from APP_CONFIG.purchases.packages, e.g. monthly).
• Element Clicked { screen: 'plans', element_type: 'button', element: 'subscribe' } — Subscribe CTA tapped (followed by the standard Purchase Started/Purchase Completed/Purchase Failed chain).
• Element Clicked { screen: 'plans', element_type: 'link', element: 'restore' } — Restore link tapped (followed by Purchase Restore Tapped/Purchase Restore Completed).
• Element Clicked { screen: 'profile', element_type: 'button', element: 'subscription' } — Subscription row in Profile tapped (entry into the plans screen).

Purchase Started/Purchase Completed/Purchase Failed/Purchase Restore Tapped/Purchase Restore Completed already fire from EntitlementContext.buy/restore; the plans screen passes source: 'plans_screen' so the funnel can be segmented by entry point.

Entitlement Changed

Fires whenever isSubscribed flips on EntitlementContext (renewal, expiry, cross-device sync).

• is_subscribed (bool)

Also: is_subscribed is set as a Mixpanel People property every time EntitlementContext resolves, so the latest known state lives on the user profile for funnel segmentation.

Cohort coin-gate events

Fired by the shared useCoinGate hook (src/hooks/useCoinGate.js), which funnels every coin-spending action (chapter start, simulator session, activity creation, etc.) through one cohort-aware path. Replaces the legacy local if (coins < N) checks scattered across feature files.

Cohort ('A' | 'B' | 'C') is not encoded on these events — it lives on the Mixpanel user profile as the payment_variant People property (the effective value incl. admin overrides, set by <PaymentVariantSeeder>). Segment/break down any coin-gate event by payment_variant for cohort funnels. (The raw Statsig bucket is intentionally not mirrored to Mixpanel — Statsig keeps the exposure for experiment analysis.)

What these events add instead is gate_outcome — which branch the gate took, orthogonal to cohort:

• premium — subscribed, gate bypassed (no variant consulted).

• sufficient — enough coins, gate passed (no variant consulted).

• insufficient — balance short, the cohort drove the decision (A → auto-refill, B/C → paywall). Combine with payment_variant to see the A-vs-B/C split.

• Coin Gate Triggered — every time gate.request() or gate.requestAccess() fires. Properties: source, cost, coins_before, gate_outcome, is_subscribed. Use this as the top of any coin-gate funnel.

• Coin Gate Blocked — fires when the user is short on coins (always the insufficient branch). Properties: source, cost. Segment by payment_variant for the cohort.

• Coin Auto Refill Granted — Group A path (also fires for unbucketed users who fall through to A). Properties: source, amount (30).

• Coin Grant Dialog Shown — the visible "You're out of coins / it's your lucky day / +N coins" grant notice (CoinGrantDialog, a bottom-sheet) that accompanies a Group-A auto-refill. Properties: amount (30). Its feedback link fires Element Clicked { screen: 'coin_grant', element_type: 'link', element: 'give_feedback' } (→ profile feedback).

• Insufficient Coins Paywall Shown — Group B / C path. Properties: source. Segment by payment_variant for the cohort. Followed by the standard Purchase Started chain when the user taps Go Premium.

  • The paywall is a bottom-sheet (InsufficientCoinsPaywallDialog) with three CTAs, each firing Element Clicked { screen: 'insufficient_coins_paywall', element_type, element }: element: 'go_premium' (→ PlansScreen), 'daily_questions' (→ Fun Zone tab), 'give_feedback' (→ profile feedback).
  • Insufficient Coins Paywall Dismissed — fires when the sheet is closed without picking a CTA (backdrop tap), closing the Insufficient Coins Paywall Shown → CTA / dismiss funnel. Properties: source. A CTA-driven close does not fire this (the Element Clicked already records that outcome).

• Coin Balance Panel Shown — fires when the non-premium user taps the coin counter and the "Your coins" sheet (CoinBalancePanel) opens. Properties: coins. The counter tap itself fires Element Clicked { screen, element_type: 'button', element: 'coin_counter' } (screen ∈ the surface: home / journey / daily_question); the sheet's CTA fires Element Clicked { screen: 'coin_balance_panel', element: 'go_premium' }.

• Payment Variant Stamped — fires once when <PaymentVariantSeeder> seeds the Bubble payment_variant field on a fresh server-empty report. Properties: variant ('A' | 'B' | 'C'), source ('statsig' for a real assignment, or 'unbucketed_default' when the user is unbucketed and gets control 'A'). Does not fire for users who already have a value (Bubble source of truth / admin override) or when Statsig is unavailable (outage → retries next session).

Premium-user surfaces

• Premium Badge Tapped — fires when a subscriber taps the top-bar premium badge. Properties: surface ('home' | 'daily_question').
• Premium Status Viewed — fires when the PremiumStatusDialog opens. Properties: subscription_type, expires_at.
• Manage Subscription Tapped — fires when the user taps "Cancel subscription" in the status dialog (deep-links to the OS subscription manager). Properties: platform ('ios' | 'android' | 'web').

Subscription lifecycle screens

• Plans Screen Shown — fires every time the redesigned PlansScreen mounts or is surfaced as an overlay. Properties: source ('profile' | 'post_onboarding_b' | 'insufficient_coins' | 'coin_panel' | 'expired_modal' | 'badge_tap'). Coexists with the older Screen Viewed { screen: 'plans' } event for back-compat; new funnels should use Plans Screen Shown to segment by entry point.
• Plans Screen Dismissed — fires when the user leaves PlansScreen without converting (closes the Plans Screen Shown → subscribe / restore / dismiss funnel). Properties: source (same enum as Plans Screen Shown), reason ('back' = back chevron on the normal plans view; 'already_subscribed' = back chevron or Continue on the "You're Premium" state). Does not fire on the mandatory Group-B gate (back is hidden — the only exits are subscribe or restore).
• Subscription Success Shown — fires when the post-purchase celebration screen mounts. Properties: package_id, subscription_type. The Continue button that exits the screen fires Element Clicked { screen: 'subscription_success', element_type: 'button', element: 'continue' }.
• Subscription Expired Modal Shown — fires when the expired-notice dialog appears (RC entitlement flipped subscribed → not since last session). Properties: last_type ('yearly' | 'quarterly' | 'monthly' | null).
• Subscription Expired Action — fires when the user resolves the expired notice. Properties: last_type, action ('renew' | 'continue'), bonus_granted (bool — true if Bubble was expected to grant 10 welcome-back coins).

People + super properties

subscription_type is pushed as a Mixpanel People property by EntitlementContext on every entitlement refresh — RevenueCat is the source of truth (yearly/quarterly/monthly, null when not subscribed), set alongside is_subscribed. It is not sourced from Bubble/UserContext (that field was never reliably pushed).

The cohort variant is carried by a single People (user-profile) property:

• payment_variant: "A" | "B" | "C" — the effective variant (Bubble source-of-truth field, including admin overrides), people.set by <PaymentVariantSeeder> (src/hooks/usePaymentVariant.js). It's a profile property (not a super property) because the cohort is sticky and server-owned: it survives reset(), is queryable on the user level, and remains segmentable in event reports.

Use payment_variant for all cohort-segmented funnel analysis — break events down by it in reports; it reflects the experience the user actually got. The raw Statsig assignment is not mirrored to Mixpanel as experiment_payments (the payments experiment is suppressed in attachMixpanelMirror, src/utils/experiments.js, to keep one cohort property); use Statsig's own exposure data for randomized (intent-to-treat) experiment analysis.

System

Report Submitted

Fires when a bug report is sent (via clipboard copy or Slack relay).

Source: logCapture.js

Profile Photo Updated

Fires when user crops and saves a new profile photo.

Source: MainTabs.jsx

FTUE Walkthrough Completed

Fires when the user finishes all steps of the first-time user experience walkthrough.

Source: DrLeoWalkthrough.jsx

TTS Error Occurred

Fires when TTS streaming fails (network error, proxy down, etc.). Centralized in useTTS hook — all TTS consumers get tracking automatically.

Source: useTTS.js

Push Notification Prompt

Push Prompt Shown

Fires when the pre-permission dialog appears.

Source: MainTabs.jsx, useNotificationGate.jsx

Push Prompt Accepted

Fires when user taps "Enable notifications" in the pre-permission dialog. Tracked BEFORE the native OS prompt.

Source: MainTabs.jsx, useNotificationGate.jsx

Push Prompt Dismissed

Fires when user taps "Not now" in the pre-permission dialog.

Source: MainTabs.jsx, useNotificationGate.jsx

Push Settings Redirect Shown

Fires when the "previously denied" dialog appears in Profile.

Source: MainTabs.jsx

Push Settings Redirect Accepted

Fires when user taps "Open Settings" from the profile notification dialog.

Source: MainTabs.jsx

5. Element Clicked Reference

All Element Clicked events. Properties always include screen, element_type, and element. Extra context properties listed in the last column.

Welcome & Auth

FTUE Walkthrough

Main Navigation

Onboarding

Journey

Learn Video

Practice

Act

Chapter Celebration

Step Review

Insight Questions

Insight Other Dialog

Insight Playback

Fun Zone

Activity View

Type Detail

Simulator Results

Profile & Settings

Account Info

Name Prompt

Partner Name Prompt

Profile Save (Account Info)

Daily Question

Share Viewer

Push Notifications

6. Funnels

Onboarding → Insight → Signup Funnel

1. Screen Viewed { screen: 'welcome' }
2. Element Clicked { element: 'lets_go' }
3. Onboarding Intro Viewed              ← one-time only
4. Onboarding Intro Completed           ← if video finished
   OR Onboarding Intro Skipped          ← if CTA tapped before video ends
5. Screen Viewed { screen: 'onboarding' }
6. Onboarding Step Completed  ← repeats per step
7. Onboarding Completed
8. Onboarding Insight Started
9. Onboarding Insight Generated
10. Onboarding Insight Playback Completed / Skipped
11. Onboarding Insight CTA Tapped
12. Screen Viewed { screen: 'signup' }
13. Sign Up Started { method }
14. Sign Up Completed
15. Onboarding Data Connected
16. Screen Viewed { screen: 'ftue_walkthrough' }
17. FTUE Walkthrough Completed

Drop-off: Onboarding Abandoned (back on step 0)
          Onboarding Intro Backed Out (back from intro to welcome)
Resume:   Onboarding Resumed { phase, step, source }
Replay:   Onboarding Intro Replayed (user replays intro video)
Timeout:  Onboarding Insight Timed Out
Back:     Onboarding Step Back { from_step, to_step }
Mic err:  Onboarding Mic Permission Denied / Onboarding Mic Unavailable
No API:   Onboarding Speech API Unavailable
Skip:     Element Clicked { screen: 'ftue_walkthrough', element: 'skip' }

Authentication Funnel

1. Element Clicked { element: 'sign_in' }
2. Screen Viewed { screen: 'signin' }
3. Sign In Started { method }
4. Sign In Completed { method }

Journey Chapter Funnel

Each chapter follows this step sequence:

0. Chapter Started { chapter, chapter_title, coin_cost: 10 }  ← fires on coin-gate confirm

1. Journey Step Started { step_type: 'learn' }
2. Journey Video Watched
3. Journey Step Completed { step_type: 'learn' }

4. Journey Step Started { step_type: 'practice' }
5. Journey Practice Started
6. Simulator Session Started { mode: 'journey' }
7. Simulator Session Completed
8. Journey Practice Completed
9. Journey Step Completed { step_type: 'practice' }

10. Journey Step Started { step_type: 'insight' }
11. Insight Flow Started { type: 'journey' }
12. Insight Question Answered  ← repeats
13. Insight Playback Completed / Skipped
14. Journey Step Completed { step_type: 'insight' }

15. Journey Step Started { step_type: 'act' }
16. Element Clicked { element: 'accept' or 'decline' }
17. Journey Step Completed { step_type: 'act' }

18. Chapter Completed

Drop-off at any stage: Journey Step Abandoned { step_type }

Simulator Funnel (Freeform)

1. Screen Viewed { screen: 'simulator' }
2. Simulator Session Started { mode: 'freeform' }
3. Coins Deducted { amount, context: 'simulator' }  ← fires at stage 2 start
4. Simulator Session Completed { score, skill_level }

Alt exits:
  - Simulator Session Closed (user quits mid-session)
  - Simulator Session Error { code, message }

Loop: Simulator Session Retried → back to step 3

Insight Funnel (Standalone)

1. Insight Flow Started { type: 'learn' or 'activity' }
2. Insight Question Answered  ← repeats
3. Insight Generated
4. Insight Playback Completed / Skipped

Timeout: Insight Generation Timed Out
Drop-off: Insight Flow Closed

Daily Question Funnel

1. Daily Question Viewed { question_id, category }
2. Daily Question Voted { question_id, index }

Partner Connection

1. Partner Connected

Note: Partner invitation is handled in Bubble, not tracked with Element Clicked in the React UI.

Push Notification Permission Funnel

Triggers: post_signup (MainTabs startup), session_start (7-day re-prompt), reinstall (fresh install), act_reminder (journey act reminder gate)

1. Push Prompt Shown
2. Push Prompt Accepted (vs Push Prompt Dismissed = drop-off)
3. Push Permission Requested
4. Push Permission Responded { granted: true }
5. Push Player ID Obtained

7. Recommended Mixpanel Reports

8. Developer Checklist

When adding or changing analytics tracking:

• Event name is Title Case, Object-Action, past tense
• Property names are snake_case
• Import track from src/utils/analytics.js (never import mixpanel-browser directly)
• UI interactions use Element Clicked with screen, element_type, element
• Business/funnel actions get their own domain event name
• Update this document — add the event to the appropriate section
• Update funnels section if adding a new step to an existing flow
• If adding a new people property, add it to the People Properties table

Code patterns

Track a UI interaction:

import { track } from '../utils/analytics';

track('Element Clicked', {
    screen: 'screen_name',
    element_type: 'button',  // button | tab | banner | card | toggle | link
    element: 'element_name',
    // ...extra context
});

Track a domain event:

track('Feature Action', { property: value });
// e.g. track('Partner Connected');

Track a screen view:

import { screen } from '../utils/analytics';

screen('screen_name');