What does this do?
Variants helps make the experiments workflow decision-ready in Testvoy. The goal is not only finding a setting, but understanding why it exists, how to read the outcome and where to debug first.
Know when to use it
Learn which UI fields matter
Know what success looks like
When should you use it?
Use this guide during first setup, experiment creation, report interpretation or before sharing with a client or team. Testvoy keeps the workflow approachable for non-technical users while still exposing SDK, event and security context for developers.
- 01
Choose the relevant workspace and project
- 02
Follow the checklist on this page
- 03
Verify with preview or verifier
- 04
Share the setting or report with the team
How to do it
Most Testvoy workflows follow the same pattern: choose context, define the rule or change, then verify through QA and reporting. This keeps the product focused on decision quality, not only running tests.
- Is the workspace correct?
- Is the project key or domain correct?
- Does the goal/event match?
- Were mobile and desktop checked?
- Any bot/SRM or dropped event warning?
Example experiment setup
Example: you want to test hero CTA copy on the pricing page. Use a clear experiment name, target /pricing, create Control and Variant B, set signup_started or purchase_completed as the primary goal, split traffic 50/50 and do not launch before preview/QA is complete.
- 01
Choose New experiment
- 02
Name it Pricing Page CTA Copy Test
- 03
Select Type: A/B Test
- 04
Set URL targeting to exactly /pricing
- 05
Variant B: change CTA copy to 'Start 14-day free trial'
- 06
Choose primary goal: signup_completed
- 07
Set traffic allocation to 50/50
- 08
Press Start after QA checklist passes
Name: Pricing Page CTA Copy Test
Type: A/B Test
URL target: /pricing
Control: Current CTA
Variant B: 14 gün ücretsiz dene
Primary goal: signup_completed
Traffic split: 50% / 50%Practical scenario
A growth team changes CTA copy on the pricing page, connects signup_started and signup_completed goals, then reads Google Ads and returning visitor segments separately. If the result is promising, they share a report link with the client or leadership.
Common mistakes
Most mistakes come from wrong project keys, overly broad selectors, missing goals, staging/prod mixups, early decisions on small samples or skipping mobile QA.
Naming an experiment 'test'
Launching without a goal
Deciding on total CVR only
Sending screenshots instead of shareable reports