Getting started

A-Z glossary

Learn Testvoy and experimentation terms with short definitions and related docs links.

Last updated: May 22, 20268-14 minBeginner to intermediate
Start free See pricingMethodology

A-Z concepts

This glossary summarizes the terms you will see in the Testvoy interface.

Workspace: team or client workspace.

Project: single site or app scope.

Experiment: measured test.

Control: original experience.

Variant: changed experience.

Goal: success event.

Funnel: step-by-step journey.

Segment: user group.

SRM: traffic allocation mismatch check.

Bayesian probability: probability to beat control.

Frequentist result: p-value and confidence interval reading.

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.

  1. 01

    Choose the relevant workspace and project

  2. 02

    Follow the checklist on this page

  3. 03

    Verify with preview or verifier

  4. 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?

Implementation example

For A-Z glossary, 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.

  1. 01

    Choose the project

  2. 02

    Create the setting or rule with a clear name

  3. 03

    Enter an example URL/event/segment value

  4. 04

    Verify with preview or verifier

  5. 05

    Check the result in reporting

Example fields
Name: A-Z glossary
Project: storefront-production
URL: /pricing
Goal: signup_completed
Audience: all visitors

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

Related pages

Getting startedCore concepts glossary

Learn workspace, project, experiment, goal, funnel, segment, SRM and statistics concepts.

Frequently asked questions

Who is A-Z glossary for?

Marketing, growth, product and developer teams can use the same guide at different depths.

Do I need a developer?

Not for basic visual changes and report reading; SDK, custom events, custom JS or enterprise security benefit from technical support.

How do I know it worked?

Verifier, recent events, preview, QA checklist and report warnings show setup and experiment health.

What is the common mistake?

Wrong project keys, missing goals, fragile selectors, early decisions on small samples and skipped mobile QA are common.

Docs

Try this guide in the app

Finish setup, create your first experiment and read the report with cleaner data in Testvoy.

Start free Docs