Step 7: copy the opt-in link and paste it in Peerbeta

In the published track's “Testers” tab, copy the “Join on the web” link, which starts with https://play.google.com/apps/testing/, and paste it in Peerbeta.

J
Written By JordanLast updated 1 hour ago

What this step is for

The opt-in link makes each person a tester of your app. Peerbeta sends it to every tester it invites, so it has to be the right one.

How to do it

  1. Once the track shows “Published”, open its “Testers” tab.
  2. Copy the “Join on the web” link: https://play.google.com/apps/testing/ followed by your package name.
  3. In this Peerbeta step, paste it and click “Check the link”.

Peerbeta checks the format and the package at once. Then the first 3 testers confirm the link opens your app before recruiting goes on: the link shows “Checked, waiting for 3 testers”, then “Confirmed by testers”.

Common mistakes

  • Pasting the store listing link, with store/apps/details: it only works after opting in.
  • Pasting the internal testing link: it's a different test, and it keeps testers out of the closed one.
  • Pasting another app's link: the package must be your test's.
  • Picking up an extra character when copying from a chat app: copy the link straight from the Play Console.

If 2 of the first 3 testers can't find the app, Peerbeta pauses the test and the link shows “Not found by testers”: see the group isn't on the track ("“Item not found” for several testers: the group isn't on the track").

Was this helpful?

Your feedback shapes what we write next.

← Previous

Step 4: choose the track's countries

Next →

Step 1: create the closed testing track

Related articles

“This is the store listing link”: testers need the opt-in linkThe pasted link is your app's Play Store listing, which only works once a tester has opted in. Copy the opt-in link, the one with apps/testing, from the track's Testers tab.No opt-in link in the Play Console yetThe Play Console shows the opt-in link only once the closed testing track is published. Finish the track, publish a release and wait for “Published”.“This is the internal testing link”: the wrong link was pastedThe pasted link belongs to your internal test, not to the closed test. Copy the closed testing track's opt-in link instead, and keep our testers out of internal testing.Step 5: check the target API levelGoogle refuses a new app that targets too old an API: since 31 August 2026, API 36 for phone apps. Check targetSdk in build.gradle and enter it in Peerbeta.