A/B testing data paths

Where WordPress A/B testing plugins send visitor data

An A/B testing plugin can assign a visitor to a test variant when the page loads. Some plugins load an outside testing script to do that. Requests to that service include an IP address and browser information. Other plugins choose the variant on your WordPress server and keep results in your database. This table describes the setups below; your settings can change where requests go.

Based on plugin documentation, not tests of your site. Your settings can change what loads. This is not legal advice or a compliance rating.

Scan your site for third-party requests

How we group A/B testing plugins

We compare the A/B testing setups named below. A plugin that assigns variants on your WordPress server and stores results in WordPress is different from a plugin that loads an outside testing script. Heatmaps and session recordings belong on the heatmap plugin privacy page. We have not tested consent timing or how long testing-service logs are kept.

A/B testing plugins

No paid placement. Variants chosen on your site first, then outside testing services, then plugins not yet reviewed. Names are alphabetical within each group.

PluginDocumented behaviorDocumented service domainsHow long data is keptBefore consentLinksSource
Opti-Behavior

This row covers Opti-Behavior in its default self-hosted mode: A/B tests run in WordPress and results stay on your server. Click maps and session recordings from the same plugin belong on the heatmap plugin privacy page. Consent timing is not tested here.

Variants chosen on your siteNo outside testing script documented for this setup. Other page requests are not covered.Not assessedNot tested
  • None
Variolab

This row covers Variolab when visitors are split with a first-party cookie and impressions are stored in the WordPress database. The listing says tracking is fully internal. Consent timing is not tested here.

Variants chosen on your siteNo outside testing script documented for this setup. Other page requests are not covered.Not assessedNot tested
  • None
Convert Experiences

This row covers Convert Experiences when a project ID is saved. The page loads a testing script from cdn-4.convertexperiments.com in the document head, before other head scripts. Variant assignment is computed by that outside script. Consent timing is not tested here.

Outside testing servicecdn-4.convertexperiments.comNot assessedNot tested
  • None
Crazy Egg

This row covers Crazy Egg when a tracking script is saved. The same script host, script.crazyegg.com, is used for assigning visitors to test versions. Click maps and recordings belong on the heatmap plugin privacy page. Consent timing is not tested here.

Outside testing servicescript.crazyegg.comNot assessedNot tested
Nelio A/B Testing

This row covers Nelio A/B Testing when tests run from the WordPress dashboard. Variant assignment uses a first-party cookie on your site. Conversion events are sent to api.nelioabtesting.com. Heatmaps in the same plugin belong on the heatmap plugin privacy page. An optional setting that keeps the browser on your domain is a different setup and is not this row. Consent timing is not tested here.

Outside testing serviceapi.nelioabtesting.comNot assessedNot tested
  • None
Wingify (VWO)

This row covers the official Wingify plugin, formerly VWO, when an account ID is saved. A VWO account loads a testing script from dev.visualwebsiteoptimizer.com. A Wingify account loads it from edge.wingify.net. The script can briefly hide page content while loading test settings; a timeout or loading error can show it again. A same-page blocking script option is documented. Optional server-side WooCommerce event tracking is a different setup and is not this row. Consent timing is not tested here.

Outside testing servicedev.visualwebsiteoptimizer.com, edge.wingify.netNot assessedNot tested
  • None
Thrive Optimize

We have not reviewed this plugin's A/B testing data path yet.

Not reviewedDocumentation not reviewed yet.Not assessedNot tested
  • None

What this table does and does not prove

This table describes the named A/B testing setups. It does not show what loads on your site. Where no outside testing script is documented, that applies only to the setup described. Other page requests are not covered. Heatmaps and session recordings are a different setup. Plugins marked Not reviewed have not been assessed. We have not tested consent timing, and we have not assessed how long testing-service logs are kept. The site scan linked below checks for third-party requests; it does not access your WordPress database.

Documentation snapshot: Oct 1, 2026. Sources are linked in each reviewed row.

Related pages

Scan your site for third-party requests

/wp-ab-testing-plugin-privacy