Guide · Play Console
Play Integrity in closed testing — practical checklist
How to use Play Integrity API during Google Play closed testing: verdicts, common failures, tester quota, and when to require it on measurable campaigns.
Closed testing covers Play Console tester quota. Play Integrity API is not the quota: it attests that the app runs in a trustworthy environment. On Tester Marketplace you can require Integrity per campaign when fraud or emulators matter more than integration friction.
Quota vs Integrity (don't conflate them)
- Play quota: minimum real testers on the track — see the quota checklist.
- Integrity: attestation token per session/device — app and device integrity verdicts.
- You can cover quota without Integrity; Integrity without quota does not satisfy closed testing.
Checklist before requiring Integrity in closed testing
- Test build published on the closed-testing track (not sideload-only APK).
- Same signing / Play App Signing key Play Console expects.
- Play Integrity API enabled and service account / Cloud project linked.
- Token decoded on the server (never trust the client alone).
- Documented verdict threshold (e.g.
MEETS_DEVICE_INTEGRITY) and a plan for legitimate failures. - Testers informed: rooted/emulator devices will fail — align expectations with the technical guide.
Common failures (what to check)
- No device verdict: emulator, uncertified image, or install outside Play.
- App integrity fails: different signing key, package name or version not recognized by Play.
- Token rejected on backend: clock skew, reused nonce, or wrong Cloud project.
When to enable it on Tester Marketplace
If you only need quota and telemetry, start without Integrity. Enable it on well-paid campaigns, soft launches, or after abuse — details in when to require it on campaigns.