# Google Play testing tracks

<div align="left"><figure><img src="/files/a5hmAO0gakC2e1eNxZfd" alt=""><figcaption></figcaption></figure></div>

### Use an existing Google integration

#### Navigate to the Integration settings view

1. Select an app in the top left corner from the Switcher
2. Navigate to **App Settings** by clicking the gear icon (⚙️) at the top of the Timeline sidebar
3. Click on **Integrations** in the sidebar

#### Connect Google Play testing tracks

* Find the **Play Beta Testing** integration module under the **Beta testing** section
* Click the **Connect** button
* Select an existing Google installation
* Click **Connect**; you’ll be presented with a dialog in which to enter your [Google Play testing track settings](#google-play-testing-track-settings)

### Set up a new Google integration

#### Navigate to the Integration settings view

1. Select an app in the top left corner from the Switcher
2. Navigate to **App Settings** by clicking the gear icon (⚙️) at the top of the Timeline sidebar
3. Click on the **Integrations** option in the app settings sidebar

#### Connect Google Play

1. Find the **Play Beta Testing** integration module under the **Beta testing** section
2. Click the **Connect** button
3. Enter your app’s package name
4. Upload an service account key file (`.json)`

{% hint style="info" %}
You can generate a [service account and associated key file](/integrations/app-stores/google-play-console.md#creating-a-service-account) from within the Google Play Console by first creating an eligible Service Account, and then generating an API key on that Service Account. The user creating the Service Account and key will need to have the **Owner** role in your Google Play Developer account.
{% endhint %}

### Google Play testing track settings

* Enter your Google Play testing track settings:
  * **Package name** — Choose the package name of the app you use for beta testing.
  * **Beta testing track** — Choose a track ('alpha', 'beta', or another custom testing track) that you'll promote to using Runway. Regardless of this setting, all internal builds will be surfaced on the Beta step.

{% hint style="info" %}
The track selected in **Beta testing track** will be used as a default for automations; however, the track selection can be adjusted in **Automation settings**.&#x20;
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.runway.team/integrations/beta-testing/google-play-testing-tracks.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.