Get Your First A/B Test Running in 10 Minutes

CADENCE is free A/B testing infrastructure. Set up a test, ship it, prove it worked. Four steps. Zero to live.

What you'll accomplish:

  • Create your free account and get your Project ID
  • Install CADENCE on your site (1 minute)
  • Create a button color test (5 minutes)
  • See results in your dashboard

Watch: Getting started with CADENCE

A 10-minute walkthrough of everything on this page, from account creation to live results.

10:00

Video coming soon

Step 1: Create your account and get your Project ID

  1. Go to cadence.softpath.co/start and sign up for a free account
  2. Create a workspace (this is where your tests live)
  3. Create your first project — CADENCE will generate a Project ID for you
  4. Copy the Project ID from your project's Settings page — you'll need it in the next step

What's a Project ID?

A Project ID is a short code (like proj_Ax8mK2pQr4nB) that connects your website to your CADENCE project. It's safe to include in your HTML — it only grants read access to your experiment config and write access to anonymous events.

Step 2: Add CADENCE to your site

Paste this single line into your website's HTML <head> section. Replace the Project ID with yours from Step 1.

<!-- Paste this before the </head> tag on your site -->
<script src="https://cdn.softpath.co/sdk/v1/cadence.min.js" data-project="YOUR_PROJECT_ID"></script>

That's it — one line. The SDK automatically initializes, fetches your experiment config, and runs any visual experiments on the current page.

Not sure where to paste this? See platform-specific instructions for WordPress, Webflow, Shopify, React, and more.

Check it worked

Open your website in a browser. Right-click anywhere, select Inspect, then click the Console tab. Type Cadence and press Enter. You should see an object with methods like init, getVariant, and track. If you see "Cadence is not defined", double-check that the script tag is in the right place and hard refresh with Cmd+Shift+R (Mac) or Ctrl+Shift+R (Windows).

Step 3: Create a button color test

3a. Set up the experiment in your dashboard

  1. Go to your project in the CADENCE dashboard
  2. Click New Experiment
  3. Name it signup-button-color
  4. Add two variants: control (your current button) and green-button
  5. Set traffic to 100% and split to 50/50
  6. Click Start when ready

3b. The SDK handles the rest

If you created a visual experiment with a target URL, CADENCE automatically applies the visual changes on matching pages — no extra code needed.

To track conversions without code, add a data-cadence-goal attribute to any clickable element:

<!-- Zero-code conversion tracking -->
<button data-cadence-goal="signup-click">Sign Up Free</button>

For code-based experiments, you can also write JavaScript to apply changes manually:

<script>
  Cadence.ready().then(function() {
    var variant = Cadence.getVariant('signup-button-color');
    var button = document.querySelector('#signup-btn');

    if (variant === 'green-button') {
      button.style.backgroundColor = '#16a34a';
    }

    button.addEventListener('click', function() {
      Cadence.trackConversion('signup-click');
    });
  });
</script>

Check it worked

Refresh your page a few times. About half the time, you should see your original button, and the other half, a green button. Each visitor is consistently shown the same version. To force a specific variant for testing, add ?cadence_variant=green-button to your URL.

Step 4: See results in your dashboard

  1. Go to your experiment in the CADENCE dashboard
  2. You'll see exposure events (people who saw the button) appearing within seconds
  3. As visitors click the button, conversion events appear too
  4. Let your test run for at least 7 days to get reliable results

When enough traffic comes through, CADENCE tells you which button won — and whether the difference is real or noise.

How long should I wait?

A good rule of thumb: wait until you have at least 100 clicks per variant and at least 7 days have passed. Stopping a test too early can give you misleading results.

What's next

All Documentation

Need Help?

If you have questions or run into issues, check the troubleshooting guide or reach out at hello@cadence.tools