Initial integration with Google Play
Connect your Google Play account to Adapty so that our servers can read your Play Store products, validate your purchases, and receive Android subscription events.
Each store is connected separately, and these connections are independent. If your app also ships on the App Store, configure the App Store Connect integration.
The setup takes about an hour. The built-in onboarding in the Adapty Dashboard covers the same ground if you prefer to stay in one window.
Before you start
Unlike Apple, Google splits its developer ecosystem across two separate products — Google Play Console and Google Cloud Console — and this setup touches both.
What’s involved
- Service account: A Google account for machines rather than people. You need to create a new service account to grant Adapty access to your Google Cloud and Google Play consoles.
- Google Cloud Console: Google’s general-purpose infrastructure platform. Play Store has no API credentials of its own, so you create them here. Use the Cloud Console to enable the Developer APIs, create the service account, and grant it some of the necessary permissions. Adapty needs them to receive renewals, cancellations, and refunds. The service account key file, which allows Adapty to authenticate with Google, can be downloaded from here.
- Google Play Console: Where you publish your app and sell subscriptions. Use the Play Console to grant the service account the rest of the necessary permissions. Adapty needs those to read your products and validate purchases. Additionally, this is where you switch on real-time developer notifications (RTDN) to set up a line of communication between the Play Store and Adapty.
Required access privileges
| Console | What you need |
|---|---|
| Google Cloud Console | Project Creator (roles/resourcemanager.projectCreator) to create a project, if you don’t have one. Service Account Creator (roles/iam.serviceAccountCreator) to create the service account, and Project IAM Admin (roles/resourcemanager.projectIamAdmin) to give it project permissions. Owners can do all three out of the box. |
| Google Play Console | Admin (all permissions), which includes the right to invite users — you need this permission to invite the service account. |
Google grants Project Creator to everyone in a new organization by default, so you probably already have it. A locked-down corporate organization may have taken it away.
Required resources
A Google Cloud project. Create one if you don’t have one, or reuse a project you already run something on. You use the project to enable the Developer APIs and create the service account for Adapty.
A project is independent from your Play Console app. A single project can control the communications of multiple apps. Each app gets its own topic — a communication queue — inside the project.
When you’re connecting Google’s services to Adapty, you need to use the same project from start to finish. Prefer a project your team owns over a personal one — the key and the topic live there for as long as the app does.
Checklist for the initial integration
- Enable the Developer APIs in Google Cloud Console.
- Create a service account in Google Cloud Console.
- Grant the service account the necessary permissions in Google Play Console.
- Generate the service account key file in Google Cloud Console.
- Upload the key file and package name to Adapty in the Adapty Dashboard. A new service account takes at least 24 hours to activate, and Adapty can’t read your products until it does — to skip that wait, edit and save any product description in Google Play Console.
- Enable Real-time developer notifications (RTDN) in Google Play Console, using the topic name Adapty generates.
- Install the Adapty SDK for each framework your app uses:
- Test your in-app purchases on a real device before you release.
Next steps
Once the integration is in place, you can start using Adapty’s features.
Showing paywalls takes app code on top of the integration: at minimum display the paywalls, and handle the purchase process if you render paywalls yourself.
Before you release your app, work through the Release checklist.