Skip to main content

Hello,

we have noticed that starting some months ago that our reported revenue in Firebase Analytics is out of whack in such a way that Firebase shows around 3x revenue than real one for iOS app. We have enabled the Firebase integration (https://www.revenuecat.com/docs/firebase-integration) via the appInstanceID to get the revenue data in Firebase.

 

According to Firebase docs, the SDK captures purchase events automatically for StoreKit 1 and there is no way to disable it (https://firebase.google.com/docs/analytics/measure-in-app-purchases, https://github.com/firebase/firebase-ios-sdk/issues/2435). Could this be related to RevenueCat reverting back to StoreKit 1 some time ago from StoreKit 2?

 

Although even if the purchases were logged once by RC and once automatically by Firebase that still wouldn't add up to 3x the revenue.

 

Is anyone else using this setup and run into similar issues? Disabling the RC Firebase integration seems sort of like a solution but then when new version of RC starts using StoreKit 2 again we probably won't have any revenue tracked.

 

Thanks for any help!

Hi,

Happy to help here. You should be able to disable collections for Analytics like this (iOS, Android). That is the most likely source of the double-counting. Do you have this anywhere in your code?

setAnalyticsCollectionEnabled(true);

 


@Ryan Glanz right, but this will disable all analytics, which is something we don't want since we are using Firebase to track usage etc.


Gotcha. Our Firebase integration is split into two parts: Google Analytics and Firebase Extension. They can be used independently.

 

Would it suit your use-case to just use the Firebase Extension and not use our integration for analytics?


Reply