BigQuery SQL
Queried retention, onboarding, match, extraction, and session events.
I used SQL-led product analytics to identify why early players were dropping before their first PvP match and where the game experience needed tuning.
My role
Data analytics, BigQuery SQL, funnel diagnosis, retention analysis, insight storytelling

Project setup
This project analyzed an anonymized closed alpha game launch across retention, onboarding, first PvP entry, match progression, and extraction behavior.
BigQuery SQL
Queried retention, onboarding, match, extraction, and session events.
Funnel + behavior
Mapped where players left and how skill, risk, and extraction shifted.
Slides + Granola
Turned the analysis into a concise readout with P0/P1 actions.
Metric snapshot
23%
7 points below the 30% launch target.
43%
57% of players dropped before the core loop.
-12%
Largest onboarding friction point.
11%
Steep decline after early match exposure.
Early journey funnel
Install cohort
Baseline
100%
Drop before PvP
Onboarding loss
57%
First PvP start
Core loop entry
43%
Third match start
Early decline
18%
Fifth match start
Retention risk
11%
Diagnosis to decision
What mattered most
Recommended actions
Engagement signal
Across the first ten matches, kills improved and deaths declined, while extraction rate trended down. That points to a risk/reward issue, not only an onboarding issue.

Skill trend
Kills rise and deaths fall across early matches.
Risk signal
Extraction rate declines as confidence grows.
Product implication
Reward extraction more clearly mid-game.
Reflection
This project helped me practice the analytics skill that matters most in product work: turning behavioral signals into a clear decision.
Privacy note
Company and dataset details are anonymized; the page focuses on method, interpretation, and recommendations.