Has anyone worked with the WooCommerce Integration by MakeWebBetter plugin with a Pro plan on Hubspot?
We are using a site structure with subdirectories by language, i.e., the main domain is .com and varies by country or language with paths such as /es, /it, etc.
We have noticed that when sending data to HubSpot, the fields collected by the plugin always seem to come from the main .com domain, regardless of the subdirectory corresponding to the country or language.
In addition, we have noticed similar behavior with products: only one product and a single price are synchronized, even though prices vary by country.
Is this expected behavior of the plugin, or is something in the plugin configuration incorrect?
By default, the plugin treats the entire site as a single store, so it pulls the primary domain for all content it syncs to HubSpot. That means the country/language context in the subdirectory is often ignored, and you only see .com in HubSpot, not .com/es or .com/it. The same goes for product sync, it usually grabs the default price and doesn’t always pick up regional variations unless the plugin is customized or you have separate Woo stores for each region.
If you want the integration to recognize different languages or countries, you’ll likely need a custom field or property in HubSpot that maps to the subdirectory (e.g., set by a workflow or during sync). Sometimes you can work around it by tagging contacts/orders based on the landing page or language selection, but it’s not always perfect.
As for products, you’d need to check if your WooCommerce setup is handling prices as variable products per region, and if the plugin is set to sync those variations (often it just grabs the default).
If you really need clean separation by country or language, it sometimes ends up being easier to run each region as a separate Woo store with its own plugin integration, though that does add overhead.
Double-check the plugin config, but from what you’re describing, that behavior’s pretty much how it works out of the box. If you want to tweak it, you’ll likely be looking at some customization or scripting. Bit of a hassle, but possible if your HubSpot processes rely on those details.
We’ve also noticed that a large number of contacts synced through the plugin are showing “INTEGRATION” as the Original Source drill-down in HubSpot.
Is this expected behavior when using the WooCommerce Integration by MakeWebBetter plugin?
Or could this indicate that some tracking parameters (like cookies or source data) are being bypassed during the sync?
We’d like to better understand how this value is determined and if there’s a way to preserve the original source (e.g., Organic Search, Paid Social, etc.) when contacts come from WooCommerce.
What you’re seeing with “INTEGRATION” in Original Source is expected when contacts are created via the MakeWebBetter WooCommerce plugin.
The plugin pushes data into HubSpot through the API, bypassing the HubSpot tracking code and cookies. Since HubSpot didn’t observe the visitor’s browsing session, it can’t assign Organic Search, Paid Social, etc., so it just marks the origin as Integration.
If you want more accurate attribution, the key is making sure HubSpot’s tracking code runs on your storefront and that cookies aren’t blocked before checkout.
That way, if a user was already tracked from, say, a Google Ads click, HubSpot will link that existing contact record to the WooCommerce order when the email matches. If the only touchpoint happens at checkout, HubSpot has no context and the attribution stays as Integration.
A practical workaround is to capture UTMs or language/country context in hidden checkout fields, map those into HubSpot contact properties, and then use workflows or reports to keep that attribution data visible.
That won’t rewrite the Original Source, but it gives you reliable segmentation and reporting on where buyers actually came from.
Would you like me to outline exactly how to set up those hidden fields in WooCommerce so HubSpot receives them automatically?
Hi @evs949
Thank you for reaching out to the Community!
I’d like to invite some community members who are subject matter experts to join this conversation. @himanshurauthan@Jon-PrairiePath@MichaelMa - Would you be able to share any insights on this? Your expertise would be greatly appreciated.
Best,
Victor