Firebase in-app purchase integration
Firebase gives you a database, serverless functions, and analytics under one roof.
This integration connects a subscription and purchase-management layer to those Firebase services so purchase state can drive premium access, real-time reactions, and analytics — without you standing up and operating the infrastructure yourself.
What the integration connects
The extension treats Firebase services as the backend for in-app purchases across the Apple App Store, Google Play Store, and Amazon Appstore. Two jobs sit at the center: gating access to premium content, and syncing customer purchase information into Firestore. The practical appeal is that Firebase teams can implement purchases, control entitlements, and analyze purchase data without managing their own infrastructure for it.
Firestore as the shared purchase record
Storing purchase data in Firestore lets you read and display it for customers across both mobile and web apps. That matters when the same account is used on more than one surface: the purchase record lives in one place rather than being reconstructed per client. A useful way to think about it is that Firestore becomes the read layer for entitlement and purchase state, while the purchase-management layer remains the source of truth for transactions.
Reacting to purchase events with Cloud Functions
Firebase Cloud Functions can listen for purchase and subscription changes and respond in real time. Typical events include a trial starting or a subscription being canceled. From there you can drive marketing tactics, CRM campaigns, and similar follow-ups. The design question is which events deserve an automated reaction versus a dashboard view — start with the handful that change what the customer can access or what your team should do next.
Sending lifecycle events to Google Analytics for Firebase
Lifecycle events can be forwarded to Google Analytics for Firebase to understand purchase behavior and improve retention. Because delivery is server-side, events such as renewals or cancellations reach Analytics in real time even when the customer does not open the app. That closes a common gap: client-side analytics misses anything that happens while the app is closed, which is exactly when many renewals and cancellations occur.
Choosing which Firebase piece to use
Use this checklist to map each monetization need to the right Firebase service:
- Need a shared, queryable record of purchase state across mobile and web? → Firestore.
- Need to run logic the moment a trial starts, renews, or cancels? → Cloud Functions listeners.
- Need renewals and cancellations visible in analytics even when the app is closed? → Google Analytics for Firebase, fed server-side.
- Need to avoid operating your own purchase backend? → the integration's managed backend role.
If a need falls outside these, it is not covered by this integration's described scope and should be evaluated separately.
A worked example: a renewal while the app is closed
Suppose a subscriber's plan renews on a Tuesday while they never open the app. With server-side delivery, the renewal event is sent to Google Analytics for Firebase in real time, so retention reporting reflects it without waiting for the next session. In parallel, a Cloud Function listening for subscription changes can trigger a CRM follow-up. Firestore holds the updated purchase record so a web surface can show the correct entitlement. Each Firebase service plays a distinct role in the same event.
Beyond Firebase: connecting other tools
No-code integrations can route real-time events and revenue data to other tools in the stack. Examples include Adjust, Apple Search Ads, Singular, Branch, SplitMetrics Acquire, Meta Ads, Tenjin, and AppsFlyer. These are separate connections from the Firebase services above; treat them as additional destinations rather than part of the Firebase backend itself.
Frequently asked questions
Which app stores does this integration cover?
It covers in-app purchases on the Apple App Store, Google Play Store, and Amazon Appstore.
Why store purchase data in Firestore?
So purchase data can be accessed and displayed for customers across both mobile and web apps from a single shared record.
Do renewals and cancellations show up in Analytics if the app is closed?
Yes. Lifecycle events are sent server-side to Google Analytics for Firebase, so events like renewals or cancellations arrive in real time even when the customer does not open the app.
Do I still need to manage my own purchase backend?
The integration is designed so Firebase users can implement purchases, control premium access, and analyze purchase data without managing that infrastructure themselves.