TestPogo reference
Set up your TestPogo campaign after payment
Find your Google Play web opt-in link, add the TestPogo group and complete app-access setup after payment.
Updated 2026-11-01 · Read as Markdown
1. Share your app links
After payment, enter your app name, contact email and Google Play web opt-in link. Testing notes are optional; include the workflows you want testers to try, without passwords or private user data.
In Play Console, choose your app → Closed testing → your track → Testers → Join on the web → Copy link. Share the web opt-in link, not only the store installation link.
2. Add the TestPogo tester group
Add [email protected] to your closed track’s Google Groups tester settings. The group URL is https://groups.google.com/g/testpogo-testers.
Google supports multiple Google Groups on a group-based track. Add TestPogo alongside your existing groups, if any. If you currently use an email allowlist, keep existing access intact and have the setup checked before switching methods.
3. Make the release accessible
Publish an installable closed-test release. The post-payment setup asks you to enable India, USA, UK and your own country for testing. If your app has distribution restrictions, explain them to the team before changing the track. Country availability does not guarantee a specific mix of tester nationalities or language fluency.
Keep the closed track and TestPogo group available throughout the campaign. Report login requirements, paid access and device restrictions in your testing notes.
4. Give app-only viewer access
The current onboarding process requires app-level viewer access for [email protected]. Set an expiry 20 days ahead; the team will request an extension if needed. This uses your existing developer account, without creating or transferring ownership of a developer account.
Viewer access helps the team check tester onboarding, spot progress problems and arrange replacements. It also helps identify Google warnings that need attention. Never share your Google password or signing keys.
5. Let the team check access
Once your details are submitted, the team checks that testers can opt in and install. Onboarding timing starts after payment and verified working access: Top-up within 12 hours, Standard within 48 hours, Managed within 24 hours.
Campaign updates arrive by email. The developer applies for production access from their own account when Google’s requirements are met.