A/B Testing

If your WordPress or WooCommerce website is running A/B experiments, such as showing different layouts or content variations to different users, it can cause inconsistent or unreliable test outcomes in CheckView. This is particularly true for production-level smoke tests, where small layout shifts can lead to false failures.

To help ensure your automated tests remain stable and accurate, here are a few approaches you can take:

1. Whitelist IP Addresses to Bypass A/B Experiments

Many A/B testing platforms allow you to exclude specific IPs from participating in experiments. If your tool supports this, we recommend:

  • Excluding all CheckView IPs (see CheckView IP list)
  • Optionally excluding your own IP to keep local testing consistent with automated runs

This is the most straightforward solution and ensures that test bots always receive the same version of your site.

2. Block A/B Testing Scripts via Query Parameters

If your A/B platform is loaded through Google Tag Manager or any other script manager, you can use CheckView’s query string parameters to conditionally prevent the A/B logic from running.

How to set it up:

  1. CheckView appends two query parameters to each test URL: checkview_test_id (a unique identifier for the test run) and checkview_test_type (the type of test being executed). For example: https://example.com/?checkview_test_id=71a323ga-ad9c-4b5c-8bdc-xa5980cb72f4&checkview_test_type=form.
  2. In your tag manager or site script loader, add logic to skip the A/B test script when the checkview_test_id parameter is detected. Since the test ID changes on each test run, use partial detection to check for the presence of the parameter name rather than matching a specific value.

This ensures that when CheckView runs its test, it always loads the default or control version of the site.

Docs