Onboarding Funnel
PRODUCTION SUITE · MIXPANEL JQL (ID: 4015502), APPSFLYER UNIFIED LTV & POSTGRES DB
to
Onboarding Starts
--
Mixpanel: onboarding_started
Account Signups
--
Mixpanel: signup_completed
Onboarding Completions
--
Mixpanel: onboarding_completed
Total Conversion Rate
--
Signed up vs Completed onboarding
Onboarding V5 Conversion Funnel
Sequential per-user deduplicated funnel starting at Onboarding Started (App launches excluded). Includes explicit skips ⚙️.
Production Postgres DB vs Mixpanel Audit
Comparative audit showing stages tracked in both Postgres Production DB and Mixpanel.
| Metric / Stage | Mixpanel Unique Users | Postgres Production DB Count | Status / Variance |
|---|
▶
AppsFlyer Unified LTV In-App Events (Live API)
LIVE APPSFLYER LTV
Real-time in-app event counts and unique user metrics from AppsFlyer Unified LTV Dashboard (iOS & Android). Click header to expand.
AppsFlyer Clicks
--
OneLink & Campaign Clicks
AppsFlyer Installs
--
Attributed Installs
AppsFlyer Loyal Users
--
High Engagement Users
Click → Install Rate
--
AppsFlyer Conversion Rate
AppsFlyer In-App Event LTV Breakdown
| AppsFlyer In-App Event | Unique Users (LTV) | Total Event Occurrences | Avg Events / User |
|---|
AppsFlyer Campaign & Media Source Attributions
| Media Source | Campaign Name | App Platform | Clicks | Installs | Loyal Users |
|---|
DASHBOARD FILTER · INVITE_TYPE
Vouch converts at every stage and propagates deepest — but volume is low, so K sits just under 1. This is the loop worth growing.
HEADLINE K-FACTOR
0.92
below 1 — the deep loop
K = i × c
i = 1.8 invites / activated user
c = 0.51 invite→activated
Viral cycle time
2.1 days
install → first invite sent
K TREND · WEEKLY
dashed line = K threshold 1.0
INVITES SENT (SHARES)
--
DB event (created)
LINK CLICKS (CTR)
--
CTR --
SOCIAL AUTH TAPS
--
Google / Apple taps
ACTIVATED USERS
--
DB activated
CONVERSION DECOMPOSITION · C = CLICK × INSTALL × SOCIAL AUTH TAP × ACTIVATE
where the invite chain leaks, by stage (100% Postgres DB Grounded)
ANALYSIS GUARDRAILS & QUALITY GATES
D1 RETENTION · INVITED VS ORGANIC
44%
vs 52%
Invited traffic starts weaker on day 1.
D7 RETENTION · INVITED VS ORGANIC
19%
vs 31%
Gap widens by day 7 — quality problem.
REINVITE RATE · GEN 1 (QUALITY GATE)
29%
The K multiplier only holds if this holds.
INVITE → CHURN WITHIN 7 DAYS
61%
of invited
Most invited users churn in a week.
CHART
Metabase dashboard: a big-number scorecard (K), a line "trend" question, scorecards, and a bar question for the decomposition. All wired to one dashboard filter.
SOURCE
SQL over warehouse. K = count(activated users attributed to cohort) ÷ cohort size. 100% grounded in Postgres
referral_invite_events (created, clicked, signup_button_clicked, activated).SPLIT BY
Dashboard filter →
WHERE invite_type = {{invite_type}}. Never ship a single blended K — always expose vouch vs public_share.
DASHBOARD FILTER · EDGE TYPE (HOW THEY WERE INVITED)
Did the invited also invite?
Headline tile
Reinvite rate by generation
users in gen who sent ≥1 invite ÷ users in gen — the anti-growth-theater metric
seed
Gen 0
n = 500
34%
Gen 1
n = 2,300
9%
Gen 2
n = 720
2%
Gen 3
n = 90
Blended, reinvite rate collapses from 34% → 9% → 2% after Gen 1. Split by edge type to see it is the public-share path dragging it down.
GENERATION WATERFALL
activated users per hop · Gen 0 = seeds
CHAIN DEPTH DISTRIBUTION
how many hops the longest chains reach
Amplification / seed
7.2
avg downstream per Gen-0
Median / seed
2
most seeds barely amplify
METRICS PER GENERATION
| GENERATION | USERS ACTIVATED | REINVITE RATE | INVITES / USER | CONVERSION OF THEIR INVITES | EFFECTIVE K (GEN N→N+1) |
|---|
REFERRAL LINK & USER ATTRIBUTION EXPLORER
click any invite code to view its 7-stage chronological story timeline
| INVITE CODE | TYPE | INVITER | INVITEE | GEN | INVITEE STAGE | DOWNSTREAM INVITES | ATTRIBUTED AT | ACTION |
|---|
ANALYSIS GUARDRAILS & QUALITY GATES
CHART
Metabase dashboard: a big-number scorecard (K), a line "trend" question, scorecards, and a bar question for the decomposition. All wired to one dashboard filter.
SOURCE
SQL over warehouse. K = count(activated users attributed to cohort) ÷ cohort size. 100% grounded in Postgres
referral_invite_events (created, clicked, signup_button_clicked, activated).SPLIT BY
Dashboard filter →
WHERE invite_type = {{invite_type}}. Never ship a single blended K — always expose vouch vs public_share.