What does this do?
Browser SDK helps make the sdk and api 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?
<head>
<title>Store Name | Online Shopping</title>
<script
async
src="https://cdn.testvoy.com/sdk/v1/testvoy.min.js"
data-project-key="PROJECT_KEY_HERE">
</script>
<meta name="description" content="Discover products and buy with confidence." />
</head>Implementation example: place the script in head right after title
Place the Testvoy SDK snippet inside the head so experiment variants can be evaluated as early as possible. The practical placement is: title first, Testvoy script immediately after it, then meta description and the rest of the head tags. The SDK starts early while async keeps it from blocking render.
- 01
Open Project settings > SDK setup in the Testvoy app
- 02
Copy the project key
- 03
Find the head tag in your site template
- 04
Paste the Testvoy script immediately below title
- 05
Replace PROJECT_KEY_HERE with the real project key
- 06
Deploy and verify SDK loaded with /docs/install/verify-installation
<head>
<title>Store Name | Online Shopping</title>
<script
async
src="https://cdn.testvoy.com/sdk/v1/testvoy.min.js"
data-project-key="PROJECT_KEY_HERE">
</script>
<meta name="description" content="Discover products and buy with confidence." />
</head>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