Android Subscription Revenue Reporting in Open Beta, Included in Every Tenjin Plan

Tenjin’s native Subscription Revenue Report now supports Android. Connect trials, subscriptions, renewals, cancellations, and revenue to the campaigns that acquired each user. 

We’ve just released the open beta of Subscription Revenue Reporting for Android. When we launched the iOS subscription report in August, we said Android was up next. Today, subscription app teams can measure the full value of their Google Play acquisition campaigns, from new trials and paid subscriptions to renewals, cancellations, and revenue.

For mobile apps and teams that publish on both platforms, this means iOS and Android subscription performance now sit side by side, next to your attribution, spend, and user acquisition data in Tenjin. No separate dashboards, no manual exports, and no stitching store data together in a spreadsheet.

Like the iOS report, Android subscription reporting is part of every Tenjin plan, including our all-inclusive free plan, with no add-ons or premium tiers.

One Subscription View Across iOS and Android

Cross-platform subscription apps often end up with two versions of the truth: App Store data in one place, Google Play data in another, and campaign data somewhere else. That makes it hard to answer a simple question: which campaigns bring in subscribers who actually pay and renew?

Android subscription data now flows into the same Subscriptions report as iOS. You get the same metrics, and you can break them down by campaign, ad network, country, Product ID, and the other dimensions available in Tenjin reporting.

The report includes:

• New Trials
• New Subscriptions
• New Subscriptions Revenue
• Renewals
• Renewal Revenue
• Subscription Cancellations
• All Subscriptions Revenue, combining new subscription and renewal revenue

Because Product ID is available as a dimension, you can compare individual plans and offers on Google Play the same way you already do on the App Store.

How It Works on Android

Tenjin reads subscription details, including price, trial status, renewals, and cancellations, directly from Google Play. You connect your app by uploading a Google Play service account key in Tenjin. The Tenjin SDK then links each subscription to the install and the campaign that brought the user in.

The service account only needs two permissions in Google Play Console: View app information and View financial data. Nothing else is required.

SDK subscription guides are available for Android, Unity, React Native, and Flutter. If your developers use an AI coding assistant, they can also use our LLM integration guide to add subscription tracking for their platform.

Optimize Campaigns With Subscription Callbacks

Measurement is only half of the picture. Ad networks also need the right signals to find better users. Tenjin includes two built-in subscription callbacks, so you don’t need to create or maintain custom events:

• Trial Start:helps networks find users who start trials.
  On Android, this is currently available for Meta.

• Subscription Revenue: helps networks find users who pay and keep renewing.
  This is available across most major ad networks, including Meta, Google Ads, TikTok, AppLovin, Unity Ads, Mintegral, Moloco, and ironSource.

You can turn on each callback per channel in a few clicks.

A Quick Note on RevenueCat and Duplicate Revenue

Many subscription teams use RevenueCat alongside Tenjin. To keep your numbers clean, we’ve added automatic deduplication for iOS.

When you add your App Store credentials in Tenjin and also send purchases through RevenueCat, Tenjin verifies every RevenueCat subscription purchase with Apple and counts it once under Subscriptions Revenue. One-time purchases stay under IAP Revenue. Your “All” revenue and LTV metrics count each transaction once, so nothing is double counted. If you’d prefer RevenueCat to stay your only subscription source, simply don’t add store credentials.

Deduplication for Android is coming soon. Until then, for Android apps (and for third-party purchase integrations other than RevenueCat), turn on either the Subscription Revenue callback or the In-App Purchase callback for a network, not both.

Getting Started on Android Beta

Setup takes four steps, and only one needs a developer: 

1. Add your Google Play credentials.
   In Configure → Apps, select your Android app and upload your service account key (.json) in the Subscriptions Tracking section. Note: Google can take 24 to 36 hours to activate new Play Console permissions, so plan ahead.
2. Add the subscription method to the Tenjin SDK. Share the guide for your platform with your developer.
3. Check your Subscriptions report. Once trials and revenue appear, your setup is working.
4. Turn on subscription callbacks for the channels you want to optimize. If your organization already uses Tenjin’s iOS subscription reporting, Android access is already turned on for you. 

If not, email support@tenjin.com and we’ll enable the beta for your app.

For step-by-step instructions, see our Subscription Revenue documentation.

Already Included, Not an Upsell

Tenjin has always run on flat, transparent, all-inclusive pricing: sign up for any plan, every feature, no long-term commitment necessary. Access to Android Subscription Revenue Reporting features follow the same model. There’s no higher tier to move to and no second product to manage. It’s already included in the plan you use today.

Help Us Shape the Beta 

Android subscription reporting is in open beta, and your feedback directly shapes what we build next. If you have questions, need help with setup, or want to share what’s working (or what isn’t), contact support@tenjin.com. We’re here to help.