Skip to main content
Menu
Solved

in_app_purchase event not showing in Firebase after successful subscription on Android

S
Forum|alt.badge.img

I'm encountering an issue where the in_app_purchase event does not show up in Firebase Analytics, even though the user successfully completes a subscription using RevenueCat on Android.

 

Purchases.configure(PurchasesConfiguration.Builder(context, apiKey).build())

Firebase.analytics.appInstanceId.addOnSuccessListener { appInstanceId ->
    Purchases.sharedInstance.setFirebaseAppInstanceID(appInstanceId)
}

Other details:

  • I’m using Firebase SDK directly (no third-party wrappers).

  • appInstanceId logs successfully.

Best answer by chris_perriam

Setting the $firebaseAppInstanceId customer attribute is required for sending events to Google Analytics. If you are using Google Analytics, then the code you provided above would be relevant.

The guide for sending analytics events to Google can be found here: https://www.revenuecat.com/docs/integrations/third-party-integrations/firebase-integration#3-send-analytics-events-to-google-analytics

The Google Analytics portion of the Firebase integration tracks the following events (depending on the store):

  • purchase
  • rc_trial_start
  • purchase
  • rc_cancellation
  • rc_uncancellation
  • purchase
  • rc_subscription_paused
  • rc_expiration
  • rc_billing_issue
  • rc_product_change
  • rc_transfer_event

Note that there is no in_app_purchase event sent by RevenueCat’s integration with Firebase.

It’s also worth mentioning the portion of these docs which mentions setting the RevenueCat user ID:

You should make sure to use the Firebase UID as the RevenueCat app user ID when setting the Firebase user identity in RevenueCat. This step is optional, but highly recommended as a best practice for the Google Analytics portion of this integration. The Firebase Extension portion requires this step to be completed.

View original
Did this post help you find an answer to your question?
This post has been closed for comments

3 replies

chris_perriam
RevenueCat Staff
Forum|alt.badge.img+5
  • chris_perriam
  • RevenueCat Staff
  • 76 replies
  • June 30, 2025

The in_app_purchase event is a Firebase SDK event that's automatically collected, unrelated to RevenueCat's implementation.

I’d recommend reviewing the documentation on this page (specifically relating to the in_app_purchase row in the event table): https://support.google.com/firebase/answer/9234069?hl=en

S
Forum|alt.badge.img
  • syedowaisali
  • Author
  • New Member
  • 1 reply
  • July 8, 2025

I had made the code change with this doc https://www.revenuecat.com/docs/integrations/third-party-integrations/firebase-integration is it required or not relevant to my case.

chris_perriam
RevenueCat Staff
Forum|alt.badge.img+5
  • chris_perriam
  • RevenueCat Staff
  • 76 replies
  • Answer
  • July 11, 2025

Setting the $firebaseAppInstanceId customer attribute is required for sending events to Google Analytics. If you are using Google Analytics, then the code you provided above would be relevant.

The guide for sending analytics events to Google can be found here: https://www.revenuecat.com/docs/integrations/third-party-integrations/firebase-integration#3-send-analytics-events-to-google-analytics

The Google Analytics portion of the Firebase integration tracks the following events (depending on the store):

  • purchase
  • rc_trial_start
  • purchase
  • rc_cancellation
  • rc_uncancellation
  • purchase
  • rc_subscription_paused
  • rc_expiration
  • rc_billing_issue
  • rc_product_change
  • rc_transfer_event

Note that there is no in_app_purchase event sent by RevenueCat’s integration with Firebase.

It’s also worth mentioning the portion of these docs which mentions setting the RevenueCat user ID:

You should make sure to use the Firebase UID as the RevenueCat app user ID when setting the Firebase user identity in RevenueCat. This step is optional, but highly recommended as a best practice for the Google Analytics portion of this integration. The Firebase Extension portion requires this step to be completed.

Most helpful members this week

Terms & ConditionsCookie settingsAccessibility statement

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings