> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking Google Play Console as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/google-play-console

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links).

## On this page

- [Prerequisites](#prerequisites)
- [Adding a data source](#adding-a-data-source)
- [Sync modes](#sync-modes)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)
- [Troubleshooting](#troubleshooting)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

`npx @posthog/wizard warehouse`

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

The Google Play Console connector syncs crash rate, anr rate, excessive wakeup rate, and more into the PostHog data warehouse, so you can analyze them alongside your product data.

## Prerequisites

Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.

## Adding a data source

1.  In PostHog, go to the [Sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section.
2.  Click **\+ New source** and click **Link** next to this source.
3.  Enter your credentials (see [Configuration](#configuration) below) and click **Next**.
4.  Select the tables you want to sync, choose a sync method and frequency, then click **Import**.

Once the syncs are complete, you can start querying this data in PostHog.

Sync Android vitals and error reporting from the Play Developer Reporting API: crash and ANR rates, excessive wakeups and stuck wakelocks, slow starts and slow rendering, low-memory kills, plus error issues, error reports, and the anomalies Play detects.

To connect, create a Google Cloud service account and enable the **Play Developer Reporting API** in its project. Then, in Play Console under **Users and permissions**, invite the service account's email and give it access to view app quality data. Upload that service account's JSON key below.

Leave the package names blank to sync every app the service account can see.

You'll be asked for:

-   **Google service account JSON key**

## Sync modes

Each table can be synced in one of several modes, depending on what the source supports:

-   **Webhook** (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
-   **Incremental** – only new or updated rows are synced on each run, using a cursor field (such as an `updated_at` timestamp). Cheaper than a full refresh, but deletes aren't captured.
-   **Append only** – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
-   **Full refresh** – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.

See [sync methods](https://posthog.com/docs/data-pipelines/sources.md#sync-methods) for a full explanation of how each mode works and how to choose between them.

All Google Play Console tables are full refresh. Each sync replaces the contents of the table.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `Google service account JSON key` | file-upload | Yes |
| `App package names` | text | No |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `crash_rate` | Daily crash rate from Android vitals, broken out by app version. | Incremental, Full refresh | date | app, date, versionCode |
| `anr_rate` | Daily ANR (application not responding) rate, broken out by app version. | Incremental, Full refresh | date | app, date, versionCode |
| `excessive_wakeup_rate` | Daily rate of sessions waking the device more than twice an hour. | Incremental, Full refresh | date | app, date, versionCode |
| `stuck_background_wakelock_rate` | Daily rate of sessions holding a background wakelock for over an hour. | Incremental, Full refresh | date | app, date, versionCode |
| `slow_start_rate` | Daily rate of slow app starts, broken out by start type and app version. | Incremental, Full refresh | date | app, date, startType, versionCode |
| `slow_rendering_rate` | Daily rate of sessions with slow frame rendering, broken out by app version. | Incremental, Full refresh | date | app, date, versionCode |
| `lmk_rate` | Daily rate of low-memory kills the user perceived, broken out by app version. | Incremental, Full refresh | date | app, date, versionCode |
| `error_counts` | Daily error report counts, broken out by report type and app version. | Incremental, Full refresh | date | app, date, reportType, versionCode |
| `bitmap_memory_usage` | Daily bitmap memory usage percentiles, broken out by app version. | Incremental, Full refresh | date | app, date, versionCode |
| `anon_rss_and_swap_memory_usage` | Daily anonymous RSS and swap memory usage percentiles, broken out by app version. | Incremental, Full refresh | date | app, date, versionCode |
| `crash_rate_by_device_model` | Daily crash rate from Android vitals, broken out by app version and device model. Off by default, because the extra dimension multiplies rows per day and rows synced is billed. | Incremental, Full refresh | date | app, date, versionCode, deviceModel |
| `crash_rate_by_api_level` | Daily crash rate from Android vitals, broken out by app version and Android API level. Off by default, because the extra dimension multiplies rows per day and rows synced is billed. | Incremental, Full refresh | date | app, date, versionCode, apiLevel |
| `anr_rate_by_device_model` | Daily ANR (application not responding) rate, broken out by app version and device model. Off by default, because the extra dimension multiplies rows per day and rows synced is billed. | Incremental, Full refresh | date | app, date, versionCode, deviceModel |
| `anr_rate_by_api_level` | Daily ANR (application not responding) rate, broken out by app version and Android API level. Off by default, because the extra dimension multiplies rows per day and rows synced is billed. | Incremental, Full refresh | date | app, date, versionCode, apiLevel |
| `excessive_wakeup_rate_by_device_model` | Daily rate of sessions waking the device more than twice an hour, broken out by app version and device model. Off by default, because the extra dimension multiplies rows per day and rows synced is billed. | Incremental, Full refresh | date | app, date, versionCode, deviceModel |
| `excessive_wakeup_rate_by_api_level` | Daily rate of sessions waking the device more than twice an hour, broken out by app version and Android API level. Off by default, because the extra dimension multiplies rows per day and rows synced is billed. | Incremental, Full refresh | date | app, date, versionCode, apiLevel |
| `stuck_background_wakelock_rate_by_device_model` | Daily rate of sessions holding a background wakelock for over an hour, broken out by app version and device model. Off by default, because the extra dimension multiplies rows per day and rows synced is billed. | Incremental, Full refresh | date | app, date, versionCode, deviceModel |
| `stuck_background_wakelock_rate_by_api_level` | Daily rate of sessions holding a background wakelock for over an hour, broken out by app version and Android API level. Off by default, because the extra dimension multiplies rows per day and rows synced is billed. | Incremental, Full refresh | date | app, date, versionCode, apiLevel |
| `slow_start_rate_by_device_model` | Daily rate of slow app starts, broken out by start type, app version and device model. Off by default, because the extra dimension multiplies rows per day and rows synced is billed. | Incremental, Full refresh | date | app, date, startType, versionCode, deviceModel |
| `slow_start_rate_by_api_level` | Daily rate of slow app starts, broken out by start type, app version and Android API level. Off by default, because the extra dimension multiplies rows per day and rows synced is billed. | Incremental, Full refresh | date | app, date, startType, versionCode, apiLevel |
| `slow_rendering_rate_by_device_model` | Daily rate of sessions with slow frame rendering, broken out by app version and device model. Off by default, because the extra dimension multiplies rows per day and rows synced is billed. | Incremental, Full refresh | date | app, date, versionCode, deviceModel |
| `slow_rendering_rate_by_api_level` | Daily rate of sessions with slow frame rendering, broken out by app version and Android API level. Off by default, because the extra dimension multiplies rows per day and rows synced is billed. | Incremental, Full refresh | date | app, date, versionCode, apiLevel |
| `lmk_rate_by_device_model` | Daily rate of low-memory kills the user perceived, broken out by app version and device model. Off by default, because the extra dimension multiplies rows per day and rows synced is billed. | Incremental, Full refresh | date | app, date, versionCode, deviceModel |
| `lmk_rate_by_api_level` | Daily rate of low-memory kills the user perceived, broken out by app version and Android API level. Off by default, because the extra dimension multiplies rows per day and rows synced is billed. | Incremental, Full refresh | date | app, date, versionCode, apiLevel |
| `apps` | Apps the connected service account can report on. | Full refresh | — | packageName |
| `error_issues` | Clustered crash, ANR, and non-fatal issues with their report and user counts. | Full refresh | — | name |
| `error_reports` | Individual crash, ANR, and non-fatal error reports, including stack traces. | Incremental, Full refresh | eventTime | name |
| `anomalies` | Metric anomalies Play detected against its expected range. | Full refresh | — | name |
| `release_filter_options` | Releases currently serving on each track, one row per version code they contain. | Full refresh | — | app, track, release, versionCode |

## Troubleshooting

-   If the connection fails with an authorization error, the google service account JSON key is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
-   If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.

If your sync is failing or data looks wrong, see the [Data warehouse troubleshooting guide](https://posthog.com/docs/data-warehouse/troubleshooting.md). If that doesn't help, [contact support](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) – we're happy to help.