Firebase Analytics is the default product-analytics provider for most mobile apps. Connecting it to VibesFlyer lets your agent auto-discover your Firebase apps, map canonical lifecycle events, and pull normalized mobile metrics — without you copy-pasting app IDs.
Before you start
- A Firebase project with an app registered (iOS and/or Android).
- Your VibesFlyer project already created (see Getting Started).
Connect
Have your agent call connect_provider with provider firebase for your project. VibesFlyer auto-discovers the apps available in your Firebase project.
Integration path
The contract picks the right setup for your stack:
- Expo — use a development build (not Expo Go) with the native Firebase Analytics SDK via a config plugin.
- Bare React Native — add the native SDK directly.
It then specifies the canonical lifecycle events to log and the FIREBASE_APP_ID (and related) env vars to inject.
Event mappings
Canonical events map to Firebase events:
signup_completed→sign_uptrial_started→ a customtrial_startedeventpurchase_completed→purchase(withvalueandcurrency)
Verify
Enable Firebase DebugView and test on a real device — DebugView can lag and the simulator behaves differently. Confirm the lifecycle events arrive, then call validate_tracking in VibesFlyer.
Attribution is separate
Firebase tells you what happens inside the app. It does not tell you which campaign drove the install — that's attribution. Connect AppsFlyer for that, and keep your event taxonomy shared across both.