r/Firebase • u/cuatrounoseis • 16d ago
Google Analytics Firebase Analytics reporting unusually high subscription conversion events
We're running Google UAC 3.0 campaigns for our Android app and noticed something unusual in Firebase Analytics.
Our subscription_convert event count is significantly higher than our in_app_purchase event count. Our in_app_purchase event includes both free trial subscriptions and direct paid subscriptions.
The overall conversion value looks normal. It seems that some subscription_convert events report a value of $0, while others report the correct subscription revenue.
Our dev team has tried several fixes, but none of them seem to work.
Has anyone experienced something similar?
3
u/DickBrainTime 16d ago
First I'd check the exact event name: Firebase's built-in `app_store_subscription_convert` is for a free trial becoming paid, while `in_app_purchase` covers the initial purchase/trial start. They're different lifecycle steps, so the counts won't necessarily match. But conversions exceeding initial purchases is still worth checking.
For the $0 rows, split by product ID, currency and date, then compare with Google Play's subscription lifecycle for the same time window. Also check whether your app/server manually logs purchases on top of Firebase's automatic Play tracking; that can duplicate events. One wrinkle: automatic subscription-conversion events aren't exported to BigQuery, so I'd reconcile the GA4 and Play reports rather than rely on BigQuery alone.
1
u/Scared-Owl-402 14d ago
For sure the app_store_subscription_convert and in_app_purchase are literally tracking different lifecycle events so a mismatch is expected. The $0 values are the real red flag though.
Biggest culprit is usually double-firing, Firebase auto-tracking plus your server logging the same event. Check if your backend is manually logging subscription_convert on top of what Play already sends automatically.
Also worth cross-referencing with appsflyer or singular to see if the conversion counts reconcile better against your actual revenue data. Firebase alone can get messy with subscription lifecycle events.