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 it works?

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.

How to use 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
• Setup → Single account, Multi-account

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.

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.

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 labels affect results and completion

Task visibility directly affects completion calculations. 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%

This ensures completion metrics stay accurate and fair, even when tasks are segmented.

Practical use cases

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.

Labels let you run more complex betas while keeping the experience simple for testers.

‍

‍

‍

‍