When should I require Play Integrity on a campaign?

When emulator risk, tampered builds or session fraud is high — e.g. well-paid campaigns or sensitive builds. For a basic closed-testing quota it is often optional.

Does Integrity replace session rules?

No. Integrity attests the device environment; session and event rules measure usage. High-trust campaigns usually combine both.

Guide · anti-fraud

Play Integrity in tester campaigns — when to require it

When to enable Play Integrity on beta campaigns, what it adds against fraud, and how it fits Play Console plus Tester Marketplace.

Play Integrity is Google’s API to check that the device and environment are suitable. In tester campaigns it helps reduce sessions on emulators or unofficial builds. On Tester Marketplace you can enable it per campaign — it is not required on every run.

When it makes sense

High-pay campaigns or sensitive builds.
History of abuse or device-farm risk.
Soft launch where you need trust in the measurement environment.

When you can skip it

For a one-off Play quota with trusted testers or an admin gate, Integrity adds integration friction. Start with sessions/events and enable it when fraud cost exceeds integration cost.

What it means for your team

Integrate the API in the build testers install.
Link the app / service account in Play Console per the technical guide.
Send the token to the campaign endpoint — Tester Marketplace decodes on its infrastructure; you do not need to replicate our servers.

Go deeper

Create a campaign with Integrity More resources