Sending events to Google Analytics for Firebase to support data-driven decisions
summary
Describes how Google Analytics 4 for Firebase exports events to BigQuery (one daily table) and how setting analytics_user_id allows app events to be joined with backend MySQL/Postgres records. Explains Firebase limits (500 event names and 40‑character parameter keys) that break a naive one‑event‑per‑screen approach for apps with ~400 screens, and presents a working pipeline using a single YAML source, KotlinPoet/SwiftPoet code generation, CI that opens PRs, and static checks (a detekt custom rule plus Konsist/Kosist checks) to detect missing screen events and user_id regressions.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:09Data-driven decisions
- 5:02KPIs and mobile engineer role
- 6:27Firebase basics
- 14:25Screen transition events
- 18:39User ID setup
- 21:27Event sending challenges
- 28:50Missing screen events prevention
- 32:18Summary
related talks
46mFirebase & BigQuery - Do Mobile App Analytics Easily & at Scale - Queries Included
31mAction-Packed Analytics
51mAll about Firebase and Google Analytics
24mFirebase for Games
25mGrowth Hacking with Firebase
32mTurn Your App Data into Answers with Firebase and BigQuery
08h 26mLivestream
49mWhat You Need for Logging and Log Analysis to Grow Your App