How to Share Your Closed Test Opt-In Link So Testers Can Actually Join

Most failed opt-ins come down to three things: the tester is signed in to the wrong Google account, the account isn't on your tester list, or your release isn't live on the track yet. Fix those and most "the link doesn't work" problems go away.

This post covers where to find the link, what to send with it, and how to troubleshoot when someone gets stuck. Play Console screens change from time to time, so check Play Console Help if a button has moved.

What the opt-in link actually is

The opt-in link is a web URL tied to one closed testing track of one app. A tester opens it, confirms they want to join, and then gets a link to the Play Store listing where they can install the test version.

It does not install anything by itself. Opting in and installing are two separate steps, and testers sometimes do only the first.

The link usually looks something like this, with your own package name at the end:

https://play.google.com/apps/testing/com.yourcompany.yourapp

Before you share it: three checks

Sending the link too early is the most common self-inflicted problem. Check these first.

1. The track has a release. Create a release on your closed testing track and send it for review. If there is nothing published to the track, testers may see an error or find nothing to install. Review times vary.
2. The testers are on the list. In the track's Testers tab, you pick an email list or a Google Group. Anyone outside that list will be refused. If you are unsure which to use, our blog has a comparison of email lists and Google Groups.
3. The countries are right. If you limited the track to certain countries, testers outside them may not be able to install. Check the countries tab on the track.

Where to find the link in Play Console

1. Open your app in Play Console and go to Testing → Closed testing.
2. Open the track you are using.
3. Go to the Testers tab.
4. Look for the section about how testers join your test, and copy the link.

Layouts shift over time, so if you can't find it, search Play Console Help for "closed test opt-in link".

What testers need to do, in order

Give testers these steps in your message. Don't assume they know the flow.

1. Make sure the Google account added to your tester list is the one signed in on their Android phone's Play Store.
2. Open the opt-in link. On the phone is easiest, since the account is already there.
3. Tap the button to become a tester.
4. Follow the link to the Play Store page and install the app.
5. Open the app and stay opted in. For the 12-testers-for-14-days rule, people must remain opted in for 14 days in a row, so leaving the test early can cost you.

If you want the rule explained in full, see our step-by-step post on how the 12 testers for 14 days rule works.

A message template you can copy

Hi! Thanks for helping test my app. Here's how to join:
1. On your Android phone, check that the Google account you gave me is the one signed in to the Play Store.
2. Open this link: [your link]
3. Tap "Become a tester", then install the app from the Play Store page.
4. Please open the app each day and keep it installed for at least 14 days. Don't leave the test.
5. If you see an error, send me a screenshot and the email address you're signed in with.

The last line matters. It turns a silent failure into something you can fix in a minute.

Why the link fails and what to do

"Item not found" or "app not available"

The usual causes are the wrong Google account, an email missing from the list, or a release that hasn't been published yet. Ask the tester which account they are signed in with, then compare it with your list. Typos in email addresses are common.

The tester has several Google accounts

The browser or phone may open the link with a different account than the one you added. Ask them to switch to the right account in the Play Store app first, then reopen the link. Opening the link in a private browser window and signing in only with the right account also works.

The tester uses a work or school account

Some managed accounts block access to apps outside their organization. A personal Gmail account is usually easier. Ask testers to use one, and add that address to your list.

The tester just got added

If you added someone to the list a moment ago, changes may take a little while to show up. Wait and have them retry rather than re-sending the link repeatedly.

The tester opted in but never installed

This happens more than you'd think. The tester clicked "Become a tester", got distracted, and never tapped through to the Play Store. Ask them to open the same link again, and it should now show the install page.

The device isn't compatible

If your app's minimum SDK or device requirements exclude the tester's phone, the Play Store may say it's not compatible. Check the device catalog in Play Console, and ask the tester for the phone model and Android version.

The tester is on iOS or a device without Google Play

The link only works with Android devices that have the Play Store. A tester on an iPhone or a phone without Google services can't join.

Share the link where people will read it

• Send it in a direct message or email, not buried in a long post. One link, one clear set of steps.
• Ask for the Google account email first, add it to your list, and only then send the link. This avoids half the errors above.
• Don't post the link publicly and expect the list to sort itself out. People outside your list will hit errors and you won't know who they are.
• Follow up after a day. Ask who has installed. Silence usually means someone is stuck, not uninterested.

If you don't have testers to send it to

Finding people is often the harder problem. TesterMob gives you testers who use their own Android phones, use each app about 20 minutes a day, and write feedback. You pay $9.99 per app, once, in USDT. The developer side is described on the developer page, and pricing has the details.

Whoever your testers are, the same rules apply: the right account, on your list, with a live release behind the link. TesterMob isn't affiliated with Google and can't guarantee production approval, so check Play Console Help for current requirements. Common questions are also answered in the FAQ.

A quick pre-send checklist

• A release is published to the closed track.
• The tester's Google account email is on your list, spelled correctly.
• Countries are set so the tester's location is included.
• Your message explains which account to use and tells them to stay opted in.
• You've asked for a screenshot if anything goes wrong.

Take five minutes to run through this list before you send the link. It saves days of back-and-forth, and you don't want to find out on day 10 that half your testers never actually joined.