Connect once.
Experiment deliberately.

Start in your project’s Integration section. It generates setup instructions with your actual public project key, environment, endpoint, and experiment key.

See a concrete A/B example

Compare a studio product photo with a furnished setting. See exactly what changes, what stays consistent and how to measure it. View both variations

Browser JavaScript

Load the browser SDK from https://app.varypilot.com/sdk/v1/browser.min.js. The global object Varypilot exposes the browser client. Use a stable visitor identifier, connect your consent-management platform, and request the assigned variation before applying it.

Script-tag QA inspector

Inspect published experiments and preview variations in your own tab, with Varypilot analytics paused during QA.

Download the Varypilot script · Installation and QA guide

Load the Varypilot script on your page and connect your consent settings. For the local fullstack integration, open a product page and select Varypilot QA to inspect and switch server-rendered variations.

Node.js module

Download the Node.js module. Import the module from your local project.

PHP SDK

Run these commands in your PHP project root. Composer installs the SDK in vendor/ and creates vendor/autoload.php.

composer require varypilot/sdk-php:"^0.1"

Load Composer's autoloader before creating the PHP client. On PHP 7.0 or 7.1, use Composer 2.2 LTS.

require_once __DIR__ . '/vendor/autoload.php';

PHP installation and usage guide · Optional single-file download

Use server-side assignment when your application renders the experience. Generate a server credential in the workspace for the chosen environment. Keep it on your server and never include it in client code. The Integration section provides the request format and headers.

Google Tag Manager

Download the Varypilot GTM template.

The GTM integration loads the browser SDK and supports initialization, exposure, and conversion events. Set the stable visitor identifier and analytics consent from your website. Use the exact goal event name configured in the experiment.

Consent and measurement

Assignment and event collection are separate operations. Event recording requires explicit analytics consent. Count exposure when the visitor actually sees the assigned experience, and send revenue in the currency and minor units configured for the goal.

Before publishing

1. Add the correct domain to its environment.
2. Define your hypothesis, control, variants, and traffic allocation.
3. Attach primary and secondary goals and set the analysis plan.
4. Verify your own staging integration, then publish to the intended environment.
5. Check configuration delivery and recorded events before interpreting results.

Open your workspace

For integration help, contact hello@varypilot.com.