WordPress

Definition

WordPress is the open-source system for publishing pages, posts, and, with WooCommerce, a store. In an A/B test it is the site the snippet has to load on. The test itself is assigned in the browser after that load.

What WordPress means in A/B testing

WordPress renders PHP templates, a theme, and plugins. Page builders such as Gutenberg, Elementor, Divi, and Bricks change how the HTML is produced, not the fact that a client-side script can edit it after delivery. Caching plugins often store one HTML response per URL. A client-side test fits that model: every visitor can receive the cached control HTML, and the snippet applies the variant. A PHP-level test that writes a different page per visitor fights the cache.

Why WordPress matters

WordPress sites collect plugins. A testing tool that adds server work on every request, or that depends on one builder's editor, breaks the next theme update. Injecting one script, and reading WooCommerce events as goals, keeps the experiment independent of the theme. Flicker still matters, because the cached HTML is the control and it will paint if the variant script is late.

Example of WordPress

A WooCommerce catalog tests a shorter product title and a higher add-to-cart button. The Mida plugin adds the snippet in the head. The visual editor changes the title and the button on the product template. Add-to-cart and the order are Mida goals through the WooCommerce integration. Cached HTML stays shared. Shoppers see the variant only after the script runs, which is why the snippet has to be early in the head.

How to use WordPress

Install the Mida plugin, or paste the snippet into a sitewide header field, and view source to confirm it is in the head on a post, a page, and a product URL. Build the variant in the visual editor and preview it logged out, with the cache enabled. Track the WooCommerce action that matches the hypothesis, then place a test order and find it on the right variant before the test goes live.

Common mistake

A common mistake is excluding the snippet from cached pages, or loading it from the footer. Cached visitors then stay on the control, the split is no longer the one you configured, and a sample ratio mismatch shows up. Another is judging the test from a builder preview that never loaded the snippet.

How Mida works with WordPress

The WordPress integration is a one-click install that injects the tracking code and connects WooCommerce. The WordPress A/B testing guide shows the same plugin on WordPress.org and the same split of work: the script is on the site, the experiment dashboard is Mida. The visual editor is documented for WordPress and WooCommerce. MidaGX is documented to generate variants on WordPress from a prompt or a Figma file.

The WooCommerce integration records product views, add-to-carts, and orders as goals. The site's platform notes also allow the snippet via header code or GTM. Anti-flicker still belongs in the head itself, as the QA checklist describes, not only inside a tag manager. Sandbox, Mida's free plan, covers smaller sites up to 100K monthly tracked users.

Related A/B testing terms

• WooCommerce
• Webflow
• Tracking Code
• Ecommerce Platform

FAQ

Does the WordPress plugin include the experiment builder?

No. The plugin's job, as the WordPress.org listing and the WordPress integration describe it, is to add the tracking script. Variants, goals, and the readout stay in the Mida dashboard. That split is what lets a page cache keep serving one HTML file.

How are WooCommerce purchases attached to a variant?

The WooCommerce integration records product views, add-to-carts, and orders as Mida goals. You still confirm with a test order that revenue lands on the variant the buyer actually saw, which is a step on the QA checklist.

Can I put the snippet in only one page builder widget?

You can, and then every other template is untracked. The install that matches the plugin and the integration is sitewide: the plugin, a header inserter, or the theme header, so posts, templates, and product pages share one snippet.