Event Catalog & Wiring Spec

0How to use this catalog

• The event names are the contract. Fire these exact strings — don't invent new names. Amplitude, RevenueCat and AppsFlyer already expect them, and Claude verifies against them.
• Status column: LIVE = firing (mostly from web); WEB-ONLY = fires on web but not native; DORMANT = defined, never fires — these are the ones to wire.
• Priority: P0 money/attribution (do first — T5), P1 retention/activation core (T7), P2 depth & nice-to-have.
• Every event carries the canonical user_id from T4 (see §6). That's what makes them attributable. Set identity before any event fires.
• Props matter as much as the event. Where a property is listed, include it — it's what makes the event useful (revenue, source, level, etc.).

1💰 Conversion & money — P0 (Task T5)

These make paid acquisition measurable. Drive them off the RevenueCat purchase callback so they can't drift from the source of truth. Include revenue + currency on every one.

// On the RevenueCat purchase/trial callback, fan out to all trackers.
// This guarantees AppsFlyer + Amplitude never disagree with RevenueCat.
function onRcEntitlementChange(info) {
  if (info.isTrial)   { appsFlyer.logEvent('af_start_trial', { af_currency }); }
  if (info.isNewPaid) { appsFlyer.logEvent('af_purchase', { af_revenue, af_currency });
                        amplitude.track('purchase', { revenue, currency, product_id }); }
  if (info.isRenewal) { appsFlyer.logEvent('af_subscribe', { af_revenue, af_currency }); }
}

2🔑 Auth & identity — P0 (anchors Task T4)

These are where you set the canonical user_id (§6). auth_register_succeeded and auth_login_succeeded are the moments identity gets established — wire identity here first, then everything downstream attributes.

3🏋️ Workout lifecycle — P1 (Task T7 · retention core)

This is the behaviour that drives retention (the #1 revenue leak). The full workout journey is defined but silent — wiring it unlocks D1/D7/D30 retention and activation analysis.

4🧭 Onboarding & assessment — P1 (Task T7 · activation)

5🏠 Today screen, profile & settings — P2 (depth)

Engagement depth on the home screen and profile. Wire after the P0/P1 sets are proven. The today_* family is a rich home-screen interaction map — useful for engagement analysis but not blocking the core funnel.

6🔑 The canonical user_id — the keystone (Task T4)

Everything above is only attributable if it carries one consistent identity. This is the single most important decision in the project — agree it with TMA before wiring, so the web side threads the same value.

// Set at auth_register_succeeded AND auth_login_succeeded:
await Purchases.logIn(APP_USER_ID);            // RevenueCat appUserID
amplitude.setUserId(APP_USER_ID);              // Amplitude
appsFlyer.setCustomerUserId(APP_USER_ID);      // AppsFlyer

// On auth_logout, reset all three:
await Purchases.logOut();
amplitude.reset();
appsFlyer.setCustomerUserId(null);

// Decisions to confirm with TMA before you start:
//  1. What IS the canonical id?  (app user id recommended)
//  2. Same id used by the WEB checkout so web lead == app subscriber?
//  3. Pre-auth fallback (email hash) — needed to attribute quiz leads?

7Definition of done (per group)