What is Testvoy?
Testvoy is a modern experimentation product that combines A/B testing, visual editing, feature flags, personalization, funnel/segment reporting, bot-aware data quality and shareable reports in one focused platform.
Create experiments
Connect goals
Read reports with cleaner data
Share results with teams or clients
Core terms to know
An A/B test compares two or more experiences. Control is the original experience. Variant is the changed experience. Goal is the success event. CVR is conversion rate. Funnel is the user journey steps. Segment is a user group.
Control
Variant
Goal
Session, visitor, conversion, CVR
Confidence, SRM, Bayesian probability
What to do in the first 30 minutes
The goal on day one is not a perfect experimentation program, but confirming the data pipeline and first experiment flow.
- 01
Create account
- 02
Choose workspace
- 03
Create project
- 04
Add SDK snippet
- 05
Verify first event
- 06
Create first experiment
- 07
Choose goal
- 08
Complete QA checklist
- 09
Launch
- 10
Read report
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?
Implementation example
For Getting started, the safest approach is to start with a small verifiable scenario, then validate the setting in Testvoy through QA and reporting. The example fields below clarify what to enter in a real project.
- 01
Choose the project
- 02
Create the setting or rule with a clear name
- 03
Enter an example URL/event/segment value
- 04
Verify with preview or verifier
- 05
Check the result in reporting
Name: Getting started
Project: storefront-production
URL: /pricing
Goal: signup_completed
Audience: all visitorsPractical 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