Start free trial

Integration · Firebase Analytics

Connect Firebase and denominate confidence in revenue — natively for Google Play.

Firebase Analytics is the native Google-Play attribution surface. ASOLOOP reads Firebase cohort metrics on Google-Play apps and will denominate them in revenue: the workspace revenue band on the Teams-tier stakeholder dashboard is computed from connected AppsFlyer revenue today, so the Firebase revenue path is in progress, as is translating each experiment's CVR posterior into a revenue range with every assumption disclosed. You connect Firebase; ASOLOOP pulls from it. Live today.

Start 7-day free trial What ASOLOOP pulls from it
Cohortmetrics
Pulled into the loop
Range
Revenue, not a point
Live
Connector status

What ASOLOOP pulls from it

Feeds: Revenue range

Firebase feeds the loop.

For Google-Play-first portfolios, Firebase is the attribution surface you already run. ASOLOOP reads its cohort metrics as a revenue-denomination signal, so confidence on Google-Play experiments will be expressed in dollars from native data once the Firebase revenue path is wired.

  • Firebase cohort metrics

    ASOLOOP reads Firebase cohort metrics for Google-Play apps — the native attribution data, used as a signal rather than a separate report; feeding them into every confidence surface is in progress.

  • Per-hypothesis revenue ranges — in progress

    Today the revenue band renders only on the Teams-tier stakeholder dashboard, as a workspace-level figure computed from connected AppsFlyer revenue. Translating each hypothesis's CVR posterior into a revenue range on the card — using your Firebase-derived inputs once that revenue path is wired — is in progress. No point estimates — a fabricated figure would fail claim-safety.

  • Connector parity today, revenue parity next

    Firebase connects and syncs cohort data at the same precision as AppsFlyer, Adjust, and Branch — the native fit for Google-Play-first stacks. Revenue denomination is AppsFlyer-derived today; the Firebase revenue path is not yet wired.

Source, not surface

Firebase is something ASOLOOP pulls signal from— not a place ASOLOOP runs experiments. ASOLOOP runs the loop on the stores and measures the paid surfaces; integrations like this one feed the brain behind those moves.

Common questions

Questions about Firebase.

What does ASOLOOP pull from Firebase?

Cohort metrics, read as the signal that will denominate Google-Play experiment confidence in revenue once the Firebase revenue path is wired. ASOLOOP reads Firebase; it doesn't change your Firebase setup.

Is Firebase the right MMP for my Google-Play apps?

If Firebase Analytics is already your Google-Play attribution surface, yes — ASOLOOP reads it natively for cohort sync, at connector parity with AppsFlyer, Adjust, and Branch. Revenue denomination is AppsFlyer-derived today.

Is the Firebase connector live?

Yes — Firebase is one of four live MMP connectors. Revenue inputs (ARPU, install-to-paid, lifespan) are AppsFlyer-derived today; the Firebase revenue path is not yet wired.

Other integrations

Other tools advise · ASOLOOP operates

Stop running ASO by hand.

Point ASOLOOP at your app, set your autonomy level, and read the receipts. Seven days, your apps, real experiments running on both stores.

Start 7-day free trial

Credit card required to start · Not billed during the trial · Cancel anytime

Your store credentials and your own AI-model keys — inspectable, revocable any time.