Checkout Testing baseline and visitors

Checkout Testing observes checkout sessions before it launches tests. The baseline protects merchants from making decisions on too little data. The page should show real checkout-testing data for the selected store and should not reuse broader analytics visitor counts unless they measure the same thing.

Visitors tracked

Visitors Tracked is the count of checkout testing visitors observed for the selected store. It can differ from analytics Total Visitors because analytics may count broader storefront sessions, while checkout testing focuses on checkout sessions that can contribute to a testing baseline.

Baseline target

RocketCheckout uses a baseline target before the first test can launch. The dashboard should show progress clearly, rounded to a clean percentage, and explain how many more visitors are needed.

Active tests

Active Tests counts currently running checkout experiments. If there are no active tests, Best Variant CVR and Lift vs Control may show empty values until a test has enough data.

Platform plugin role

Tests are deployed through the connected platform plugin or app where supported. The plugin reads the active test config on each checkout session and routes shoppers to the assigned variant automatically.

If the page says connection required

Confirm the source connection is connected for the selected store. If Performance has SDK samples but Checkout Testing is still pending, generate a checkout session and verify checkout telemetry, not just product-page traffic.