Beta labels help you control who sees what during a beta. They let you segment tasks across different groups of testers, without creating separate betas or overwhelming people with irrelevant work.
With labels, your beta stays focused, measurable, and adaptable to real-world tester setups.
How do beta labels work?
Beta labels are beta-level entities that act as visibility filters.
You can assign labels to:
- tasks
- testers
- tester invitations (testers who haven’t accepted the beta yet)
A task is only visible to testers whose labels match the task’s labels. Tasks without labels remain visible to everyone. Tasks and testers can have multiple labels assigned at the same time.
This makes labels a simple but powerful way to tailor task visibility before and after testers join your beta.
Beta labels are not workspace tags. Workspace tags belong to your whole workspace and stay on a tester in every beta they join, while a label belongs to one beta. Triggered emails can use workspace tags in To, but not labels. Use Triggered Emails to Notify the Right People explains the difference and a way to email testers by label.
How do I set up beta labels?
1. Create label categories
From your beta’s main menu, open Labels and create one or more label categories. Categories help you organize labels by purpose, such as platform, feature, device type, or configuration.
For example:
- Platform → iOS, Android
- Feature → Sync, Notifications
- Connectivity → Wifi, Bluetooth, USB
The Labels page for a beta, showing a label category and its labels
2. Assign labels to testers (and pending testers)
Next, assign labels to:
- active testers
- pending testers who haven’t accepted the invitation yet
Assigning labels at the invitation stage ensures testers see the right tasks as soon as they join, without any extra setup later.
The beta testers table with a label column, showing which labels each tester has been assigned
3. Assign labels to tasks and publish
Finally, assign labels to the relevant tasks and publish your changes.
Only testers with matching labels will see those tasks. Tasks without labels will continue to be visible to all testers.
A task open in the editor with the Labels panel beside it, one label selected
The order of steps matters. Once a task has a label, it is no longer visible to testers who don’t have that label. To avoid unexpected visibility issues, assign labels to testers first, then label your tasks and publish the changes.
How do labels affect results and completion?
Task visibility directly affects completion calculations and tester funnel milestones. Completion is calculated based only on the tasks visible to a tester. For example, If a beta has 10 tasks, but a tester can only see 6 of them, their completion rate is calculated using those 6 tasks:
- 6 visible tasks
- 3 completed tasks
- completion rate: 50%
The same logic applies to milestones in the tester funnel. This ensures completion metrics stay accurate and fair, even when tasks are segmented.
How do I see results for each customer or group?
When several testers from the same customer, team or site share a beta, you often want one answer per group: did this customer try the task or not? Group results gives you that view.
- Create a label category for your groups, such as "Customer", and turn on Group results. You can also turn it on later by editing an existing category.
- Add one label per group, such as one per customer, and assign each tester their group's label.
- Open Results, then Feedback, and pick a group's label in Filter by username, tags or labels.
With Group results on, everyone with that label counts as one tester:
- Each task shows 100% completion if anyone in the group finished it, and 0% if no one did.
- Active and dropped counts show at most 1.
For example, if three testers carry the label Acme and one of them finishes the setup task, setup shows 100% for Acme.
Without Group results, the same filter shows the share of the group's testers who finished each task. Either way, the filter shows one group at a time and leaves out tasks that group cannot see.
How do I let testers in the same group see each other's tickets?
Turn on Share tickets for a label category. Testers who share a label in that category can then see each other's tickets in the beta, so a customer's team can follow one another's reports instead of filing the same issue twice. Testers in other groups still cannot see them.
- From your beta's main menu, open Labels, create or edit the label category, and turn on Share tickets.
- Assign each tester their group's label, as described above.
Testers who share a label can:
- read each other's tickets and reply to them
- follow and upvote them
Some things stay private:
- Direct chats between a tester and your team are never shared.
- Internal notes stay visible to managers only.
- Only the tester who created a ticket can edit it.
Visibility follows the labels, so a tester who loses the label stops seeing the group's tickets. Tell your testers before you turn this on, because tickets they already filed become visible to the rest of their group.
When should I use beta labels?
Beta labels are especially useful when:
- You want to share common tasks such as on-boarding or general feedback tasks with all testers, while segmenting feature-specific tasks.
- Testers have different platforms, devices, or configurations.
- You want to reduce task overload by showing each tester only a subset of tasks.
- You want results per customer, team or site rather than per tester.
- You want testers from the same customer or team to see each other's tickets.
Labels let you run more complex betas while keeping the experience simple for testers.