Google Play Grouping API

Name: Google Play Grouping API API
Brand: Google Play Grouping API
Availability: InStock

✓ Official Vendor SpecAnalyticsProduct Analyticsnone2 EndpointsREST

For Agents

Tag Android users with custom attributes server-side so Google Play Console can segment vitals, listings, and notifications by audience.

Quickstart

Get started with Google Play Grouping API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"tag a Google Play user with a cohort attribute"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Google Play Grouping API API.

Verify that an app-issued user token corresponds to a valid Play user before tagging

Create or update server-side tags on an Android user keyed by app package and token

Build audience cohorts inside Play Console by combining multiple tag values

Drive segmented vitals reporting and notification targeting from app backend events

GET STARTED

Start building with Google Play Grouping API API

Explore with Jentic

View OpenAPI Document

The Google Play Grouping API lets Android apps tag in-app users with custom attributes that Play Console can then use as audience filters in vitals reports, store listing experiments, and notifications. Two endpoints cover verifying that a token belongs to a Play user and creating or updating tags on that user, all keyed by an opaque app-issued token. The intended flow is server-side: an app's backend mints tags such as 'beta_cohort' or 'high_lifetime_value' so Play tooling can segment vitals and messaging on those attributes.

★ Audience-Based Vitals Segmentation

Server-side, an app backend tags signed-in Android users with attributes such as customer tier, beta cohort, or country pricing band. Once tags are in Play, the developer filters crash and ANR vitals by tag value to see whether a regression is concentrated in a specific cohort. Tag updates are eventually consistent and typically reflected in Play Console reports within hours.

POST /v1alpha1/{appPackage}/{token}/tags:createOrUpdate with body containing tags=[{key: 'tier', value: 'enterprise'}] for each signed-in user.

Targeted Play Notifications

Marketing and lifecycle teams use Play Grouping to define audiences for Play Store listing experiments and Play notifications. The backend writes tag values such as 'lapsed_30d' or 'subscriber_active' to each user, and Play Console targets messaging to those tag values. The setup decouples user segmentation from in-app code and centralises it in the backend.

Iterate over a CRM segment of lapsed users and POST /v1alpha1/{appPackage}/{token}/tags:createOrUpdate with tags=[{key: 'lifecycle', value: 'lapsed_30d'}] for each user's Play token.

Token Verification Before Tagging

Before applying tags from an untrusted client, a backend calls verify on the app-issued token to confirm it represents a real Play user for the given package. This avoids polluting Play tag stores with junk identifiers and produces audit-friendly logs of which tokens were honoured. The verify and tags:createOrUpdate endpoints together form a two-step write path.

POST /v1alpha1/{appPackage}/{token}:verify, and on a successful response immediately POST /v1alpha1/{appPackage}/{token}/tags:createOrUpdate with the intended tag set.

AI Agent Tagging via Jentic

Lifecycle automation agents that decide which user is in which cohort can call the Grouping API through Jentic without managing app-package paths or token formats by hand. Jentic exposes the verify and tags:createOrUpdate operations as two search-load-execute calls, so the agent can verify a token then write tags in a single short flow.

Search Jentic for 'tag a Google Play user', load the tags.createOrUpdate schema, and execute it with the app package, user token, and the cohort tag values.

Key Endpoints

2 endpoints — the google play grouping api lets android apps tag in-app users with custom attributes that play console can then use as audience filters in vitals reports, store listing experiments, and notifications.

METHOD

PATH

DESCRIPTION

POST

/v1alpha1/{appPackage}/{token}/tags:createOrUpdate

Create or update tags on a Play user identified by app token

POST

/v1alpha1/{appPackage}/{token}:verify

Verify that an app-issued token corresponds to a real Play user

POST

/v1alpha1/{appPackage}/{token}/tags:createOrUpdate

Create or update tags on a Play user identified by app token

POST

/v1alpha1/{appPackage}/{token}:verify

Verify that an app-issued token corresponds to a real Play user

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Google Cloud project credentials needed to call the Grouping API are stored encrypted in the Jentic vault. App-issued user tokens stay scoped to the request and are not persisted by the agent.

Intent-based discovery

Agents search Jentic with intents like 'tag a Google Play user' or 'verify a Play user token' and receive the matching operation with its full input schema.

Time to first call

Direct integration: 1-2 days for project setup, package linkage, and token plumbing. Through Jentic: under 1 hour.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Google Play Developer Reporting API

Filter vitals reports by the audience cohorts created here

Choose Reporting to query crash and ANR rates for the cohorts you have already tagged via Grouping.

Complementary

Google Play Integrity API

Attest the device and app before trusting a token enough to tag the user

Choose Play Integrity to verify device and app integrity before issuing tags from an untrusted client.

Complementary

Google Play Android Publisher API

Manage releases and listings whose audiences are defined by Grouping tags

Choose Android Publisher to set up store listing experiments that target audiences defined by Grouping tags.

FAQs

Specific to using Google Play Grouping API API through Jentic.

What authentication does the Google Play Grouping API use?

The OpenAPI spec for v1alpha1 declares no security schemes — calls are authenticated using the app-issued user token in the path plus standard Google project credentials negotiated out of band. Through Jentic any required project credentials are stored in the Jentic vault and injected at call time.

Can I write multiple tags on a user in one call?

Yes. POST /v1alpha1/{appPackage}/{token}/tags:createOrUpdate accepts a list of tag key-value pairs in a single request, so an entire cohort definition such as tier, lifecycle, and country can be written in one call. Existing keys with the same name are overwritten.

What are the rate limits for this API?

Standard Google Cloud project quotas apply. Because tagging is typically driven from a backend reacting to user events, design the writer to batch updates and back off on 429 responses rather than calling per-event from a hot loop.

How do I tag a user through Jentic?

Run jentic search 'tag a Google Play user', load the schema for POST /v1alpha1/{appPackage}/{token}/tags:createOrUpdate, and execute it with the app package, user token, and the desired tag list. Verify the token first by calling the {token}:verify operation if the token came from an untrusted client.

Is the Google Play Grouping API free?

There is no per-call charge for this API. Standard Google Cloud quota and Play developer account requirements apply. The feature is in v1alpha1, so behaviour and quotas may change as it stabilises.

Can I read the tags currently on a user?

No. The two endpoints in v1alpha1 are tags:createOrUpdate and the token verify operation; there is no read endpoint for inspecting a user's existing tags. Track tag state in the writer's own datastore if you need a read path.

Google Play Grouping API

Quickstart

Capabilities

Start building with Google Play Grouping API API

Use Cases

Key Endpoints

Why though Jentic?

Related APIs

FAQs