What is Play Integrity API?

Google’s Play Integrity API lets your backend assess the environment where a Play-distributed Android app runs — device and install integrity signals based on your Play Console setup.

When should a tester campaign require Integrity?

When fraud risk is high, builds must stay on trusted devices, or you need stronger evidence than telemetry alone. It adds integration cost; skip it for low-risk closed testing quotas.

Who configures Integrity on Tester Marketplace?

Publishers invite the service account in Play Console, integrate Integrity in the tester build, and post tokens to the campaign API. Testers see when a token is required in their progress.

Technical guide

Play Integrity for Android apps & tester campaigns

What Play Integrity is, how it fits paid tester campaigns, and how studios link Play Console with Tester Marketplace for server-side checks.

Short definition

Play Integrity API lets your backend assess the environment where your Play-distributed Android app runs — device, install integrity and more, per your Play Console setup. It is Google's attestation layer for apps distributed through Play; verdicts are meant to be checked server-side, not trusted from the client alone.

Why publishers use it in beta campaigns

Paid or quota-driven testing attracts abuse: emulators, rooted devices, or people who install once and never play. Integrity does not replace session/event rules — it adds a trust signal that the install environment looks legitimate before you count the assignment as complete.

High-value soft launches where fraud would waste budget.
Builds that must stay off unofficial sideloads.
Campaigns where telemetry alone is not enough evidence of a real device.

Inside Tester Marketplace

Publishers can require a recent attestation to complete an assignment.
The publisher dashboard includes an assistant to invite the service account in Play Console and verify with a real token.
Testers see in their progress when a token is required.
Decode & tracking endpoints live on Tester Marketplace; your studio still owns Play Console linkage and the in-app Integrity request.

Who does what

Google runs the API on device. Tester Marketplace hosts decode & tracking endpoints. Your studio invites the service account email we provide in the assistant, integrates Play Integrity in the build testers install, and posts tokens to the campaign API — a common B2B pattern. Testers only need a compatible real Android device; they do not configure Play Console.

When not to require it

If you only need to fill a closed-testing quota once and trust your invite list, Integrity may be overkill. Start with measurable sessions/events; turn Integrity on when fraud or device trust becomes the bottleneck. See also when to require Integrity in campaigns.

Related: Play Integrity API, Android attestation, anti-fraud beta testing, Google Play integrity, publishers guide, pricing.

← Publishers Testers →Publisher login