> For the complete documentation index, see [llms.txt](https://docs.devtodev.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devtodev.com/3rd-party-sources/app-marketplace-data/google-play-subscriptions.md).
# Google Play Subscriptions
{% hint style="danger" %}
This functionality is available only for projects with integrated devtodev SDK version 2.1.0 or higher for native applications and not lower than 3.1.0 for Unity!
{% endhint %}
{% hint style="info" %}
Please note that the current section describes how to integrate **only one source** of subscription data – Google Play. To get subscription data in devtodev reports, you also need to integrate the [**Subscription event via SDK**](/integration/integration-of-sdk-v2/setting-up-events/basic-methods.md#subscriptions).\
When you integrate both data sources (Google Play and SDK), the [**Subscriptions report**](/reports-and-functionality/project-related-reports-and-fuctionality/smart-view/monetization-reports.md#subscriptions) will become available, and devtodev will correctly match the data with your users. If one of the integrations is missing, the **Subscriptions** **report** will not work correctly.
{% endhint %}
{% stepper %}
{% step %}
#### [Settings in Google Cloud Platform Console](#settings-in-google-cloud-platform-console-1)
[Enable Google Play Android Developer API](#google-play-android-developer-api)
[Set up Service Account](#service-account)
[Set up Pub/Sub service](#pub-sub-service)
{% endstep %}
{% step %}
#### [Settings on devtodev side](#step-3.-settings-on-devtodev-side)
{% endstep %}
{% step %}
#### [Settings in Google Play Console](#step-3.-google-paly-console)
[Add service account and grant permissions](#service-account-and-user-permissions)
[Set up Real-time developer notifications](#monetisation-setup)
{% endstep %}
{% step %}
#### [SDK Integration](#sdk-integration-1)
{% endstep %}
{% endstepper %}
## Settings in Google Cloud Platform Console
{% hint style="info" %}
If you have already activated the [Google Play Android Developer API](#google-play-android-developer-api) and set up a [service account](#service-account) to work with devtodev, you can skip this section and proceed to [Pub/Sub service setup](#pub-sub-service).
{% endhint %}
### Google Play Android Developer API
1. Go to [Google Cloud Console]() under your Google account.\
Select the project for which you want to configure **Google Play Developer API**. Then go to the **APIs and services** section.
2. Go to the **Library** section.
3. Find the **Google Play Developer API** section.
4. Click `ENABLE` to enable the **Google Play Android Developer API**.
### **Service account**
Go to the [**Service accounts**](https://console.cloud.google.com/apis/credentials/serviceaccountkey) section.
1. Select the **project** to link the service account to and where you will collect subscription data later. Create a new project if it is not in the list.
2. In the list of available service keys, click `CREATE SERVICE ACCOUNT`.
3. Fill in the **Service account name** field. The **Service account ID** field will be filled in automatically (use the screenshot below as an example). Click `CREATE AND CONTINUE`.
4. Skip the optional steps 2-3 and click `DONE` at the end of the form.
5. After creating a service account, you will be returned to the list of available service accounts.\
\
Select the created account and open the **KEYS** tab (1), click `ADD KEY` (2), and then select the **JSON** key type (3) in the pop-up window.\
Click `CREATE` to confirm your choice.\
\
The generated **private key file** will be downloaded automatically. You will need to upload this key to devtodev later (see [Settings on devtodev side](#step-3.-settings-on-devtodev-side)).
6. Go to the **IAM** section (1) in the **Permissions** tab and click `GRANT ACCESS` (2) to add roles to the service account.\
In the **New principals** section (3), enter the service account address and grant it the **Pub/Sub Subscriber** role (4).\
If you do not have this role, you need to activate the **Pub/Sub service** in the Cloud Console ([activate Pub/Sub API](https://console.cloud.google.com/apis/api/pubsub.googleapis.com)).\
Save the changes (5).
### **Pub/Sub service**
Go to the [list of topics](https://console.cloud.google.com/cloudpubsub/topic/list) in the **Pub/Sub** service.
1. Select the project where you would like to collect subscription data. Click `CREATE TOPIC`.
2. To create a topic: fill in the **Topic ID** (use the screenshot below as an example), disable **Add a default subscription** option (1) and click `CREATE` (2).
3. Select a topic, click on three dots and select **View permissions**.
4. Click `ADD PRINCIPAL` to add the service account.
5. Add the `google-play-developer-notifications@system.gserviceaccount.com` service account and grant it the role of **Pub/Sub Publisher**. Save the changes.
6. Open the list of subscriptions and click `CREATE SUBSCRIPTION`.
7. In the form that appears:
* Specify the **Subscription ID** (1).
* Fill in the Topic name in **Select a Cloud Pub/Sub topic** field (2).
* In the **Delivery type,** select **Push** (3)**.**
* Copy the **Endpoint URL** from devtodev (see steps 8-9) and insert it in the **Endpoint URL** field (4).
Leave all other parameters unchanged. Save the changes.
8. To get **Endpoint URL** go to [devtodev](https://analytics.devtodev.com/), select the same app and open the app settings (**Settings -> Payments integration -> Subscriptions**). Click `Integrate`.
9. Copy the **Endpoint URL** and paste it in the corresponding field in Google Cloud (step 7).
## **Settings on devtodev side**
1. Upload the **Private key file** obtained in the [Service Account](#service-account) step (1).
2. Specify Android App ID (2).
3. Add all existing subscriptions, specifying the bundle, subscription period, and name for each subscription.
4. Click `Save` (3) to finish integration.
## **Settings in Google Play Console**
### Service account and User permissions
To set up user permission, you need to log into your Google Play Console account and invite your [previously created service account](#service-account).
1. Sign into the [Google Play Developer Console](https://play.google.com/apps/publish/signup/).
2. In the **Users and permissions** section, you can add users and manage their permissions.
* Go to **Users and permissions.**
* Click `Invite new users`.
3. Add the [Service Account](#service-account) as a new user:
* Add your service account email in the **Email address** field (1).
* In the **Permissions section** (2), select **the apps** (3) the service account will have access to. Click `Apply` (5). \
Grant permissions to individual apps, or use account permissions to grant access to all apps in your developer account.
* Grant the necessary rights to perform actions (see next step **Account permissions**).
4. Open **Account permissions** tab. Grant the following permissions:
* View app information (1)
* View app quality information (2)
* View financial data (3)
Click `Apply` to confirm.
{% hint style="info" %}
**Please note that the specified permissions may not apply immediately!**
{% endhint %}
5. Click `Invite user` to finish the user setup.
### Monetisation setup
After [creating a subscription](#pub-sub-service) in the **Pub/Sub** **service**, you'll need to register the created topic as a target for **Real-time developer notifications** (RTDN).
1. Go to the app’s **Monetise with Play** → **Monetisation setup** section.
2. Enter the full name of the topic in the **Topic name** field.
3. Tick the **Enable real-time notifications** checkbox.
4. Send a **test notification** using the link below (4). If everything is configured correctly, the test notification will change the integration status of the **Subscriptions** in devtodev to Active (Settings → Payments integration → Subscriptions → Market connection).
5. Click `Save changes` to finish the setup.
## SDK Integration
Integrate the [SDK Subscription event](/integration/integration-of-sdk-v2/setting-up-events/basic-methods.md#subscriptions) to complete the integration.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.devtodev.com/3rd-party-sources/app-marketplace-data/google-play-subscriptions.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
