Download websites that use MailChimp for WooCommerce

About MailChimp for WooCommerce

A shop owner does not install MailChimp for WooCommerce to change how anything looks. The plugin sits at the joint between two systems that most stores keep apart, the storefront and the mailing list, and its job is to keep the two in step. Orders, cart contents, product records and customer details move out of WooCommerce and into a campaign tool on a schedule, so an abandoned basket or a first purchase can set off a message without anyone writing a query by hand.

Because of that, the presence of the plugin on a domain carries several facts at once. The site runs WooCommerce, which means WordPress and PHP underneath. Someone at the business decided that email was a revenue channel worth wiring into checkout rather than a newsletter sent when there was time. And the store has an account with an outside platform, which is a budget line and a switching cost. For anyone selling storefront services, competing mail tooling, or analytics that plug into commerce data, a domain in this list is qualified in a way that a raw list of WordPress sites is not.

The commercial shape behind the integration also changed while the install base kept growing. The mail platform it connects to now belongs to Intuit, a company whose centre of gravity is accounting and tax software for small businesses, so the plugin is one of the places where a finance vendor touches the daily operations of very small merchants. The code itself stays under GPL v2 and is distributed free through the plugin directory, first appearing there in 2017, which is why adoption follows a plugin directory curve rather than an enterprise sales curve.

As of October 2026 we record MailChimp for WooCommerce on 29,997 sites, of which 11,597 are in United States, and registrations cluster under .com. The geographic weight matches where WooCommerce and the mail platform both sell hardest, so the list is thinner as a sampling frame for merchants outside that market. Anyone sizing a European or Asian segment should expect the counts here to sit below the real figure.

Version data is where a researcher should slow down. We hold 99 distinct version strings for the plugin, and the value that recurs more than any other is 1.0.0, a value round enough that it is more likely a default left in page markup than a real record of what is installed. Version strings are self reported by the plugin output, they vanish whenever a caching or optimisation layer strips comments, and they are not an audit of patch level. The version column is worth treating as a hint to verify, not as evidence.

Which leads to what the download is actually for. A per domain lookup answers whether one shop runs the integration. The dataset answers the other direction, giving every store that has already committed to it, with country, registration and the rest of the stack attached, so the working question becomes which of those merchants are large enough to sell to, which are running old code, and which sit in a market where nobody has called them yet.