On this page
The feedback channel is the smallest field in your closed test setup and the one with the highest leverage. It is shown to testers on the opt-in page, it is the official path for every bug report you will receive, and a missing or ignored channel is the main reason test groups go quiet. Here is how to set it up properly before your first tester arrives.
Where the feedback channel lives
Play Console asks for a feedback URL or an email address as part of your testing track configuration. Once your release is published, that contact point appears on the tester opt-in page, which is the first thing a tester sees after clicking your shareable link.
Open your closed testing track
Go to Testing > Closed testing for your app, select Manage track, and open the Testers tab where your tester list and opt-in link live.
Add a feedback URL or email
Enter the address or URL you want testers to use. Choose something you check daily during the window, because a feedback channel that takes two days to get a reply teaches testers not to bother.
Set it up before you share the link
Complete the channel at the same time as your tester list. Testers who opt in during the first hours should land on a finished page, not an empty one.
Test it yourself
Open the opt-in page as a tester would, find the feedback contact, and send a message through it. If it does not reach you, neither will anything your testers write.
Email, URL, or both
| Option | Best for | Watch out for |
|---|---|---|
| Feedback email | Small tests, direct replies, zero setup | Spam filtering and your own inbox discipline |
| Feedback URL | A short form, a shared doc, or a chat channel you already run | Testers abandon pages that ask for accounts or long forms |
| In-app feedback | Capturing reports with device context attached | It must be built before the test starts, so plan it in development |
What your feedback page should ask for
- What you want them to try this week, as a specific flow rather than 'use the app'.
- What to include in a report: what they did, what they expected, and what happened instead.
- Their device model and Android version, which explains half of all device-specific bugs.
- How fast you will respond, so silence reads as 'working on it' instead of 'ignored'.
Keep the channel healthy
Reply to the first message you receive as fast as you can, and keep replying. Testers mirror your responsiveness: an active channel produces detailed reports in week two, a silent one produces opt-outs. If your volume grows past what one person can handle, or the reports arrive undocumented and out of context, a structured pass from AppsTestLab (report triage and functional testing around the same build) turns the noise into a prioritized defect list.
Frequently asked questions
Is the feedback channel required?
Play Console asks for a feedback URL or email as part of setting up your test, and it is shown to testers on the opt-in page. Functionally it is required, because it is the only official path your testers have to reach you.
Can I change the feedback channel mid-test?
You can update the track configuration, but changing it mid-window means testers who already memorized the old contact may write into the void. If you must change it, tell your group explicitly.
Should the feedback URL point to my website?
Only if it lands somewhere short and specific: a contact form, a feedback form, or a chat invite. A generic homepage makes testers hunt, and most will not.
Do reports through the feedback channel count as engagement?
There is no published metric that counts them, but visible feedback activity is exactly the kind of evidence that engagement was real. Encourage it, log it, and keep the replies coming.
Sources & references
Official Google documentation- Set up an open, closed, or internal testsupport.google.com
- Google Play Console helpsupport.google.com
These links open Google's official Play Console Help pages used to verify this guide. AppsTestLab guidance is independent and not affiliated with Google.
Get help doing this