How to Connect Klaviyo to Shopify the Right Way (Plus WooCommerce and HubSpot)

Connecting Klaviyo to Shopify is a one-click job. Connecting it properly, so that every event you need for flows and segmentation is actually flowing, is where brands quietly lose half the value. We have set up and rebuilt Klaviyo integrations across 800+ brands, and the same three or four details get missed almost every time. Here is how to do it right, and how WooCommerce and HubSpot differ.

---

What the Klaviyo Shopify integration actually syncs

Klaviyo’s native Shopify integration is the deepest ecommerce integration it offers, because Klaviyo’s data model treats Shopify events as first-class objects rather than tags you apply by hand. Connected correctly, it syncs:

• Order data: Placed Order, Fulfilled Order, Cancelled Order, Refunded Order, with full line-item detail (product, variant, category, price).
• Checkout data: Started Checkout, the event most cart flows should trigger on.
• Customer profiles: contact details, order history, and predicted attributes (lifetime value, churn risk, next-order date) calculated automatically.
• Product catalog: so flows and campaigns can render dynamic product blocks.
• Onsite browsing: Viewed Product and Active on Site, but only if you install the onsite tracking snippet (more on that below, because this is the step everyone skips).

---

Step by step

1. Connect the integration. In Klaviyo, add Shopify as an integration and authorise it. Shopify begins syncing historical orders and customers automatically, which backfills your profiles with real purchase history from day one.
2. Install the onsite tracking snippet. This is the step that gets missed. Without Klaviyo’s onsite tracking active on your storefront, you get orders but you do not get Viewed Product or browse behaviour, which means no browse abandonment flow and weaker segmentation. On most Shopify themes this installs automatically through the integration; verify it is actually firing before you assume it is.
3. Sync the product catalog. Confirm your catalog feed is connected so dynamic product blocks pull real products, not placeholders.
4. Choose your cart trigger deliberately. Started Checkout is more reliable than Added to Cart because it fires after the customer has entered enough detail for you to actually reach them. Added to Cart fires earlier but loses anonymous browsers. For most stores, build the cart flow on Started Checkout.
5. Authenticate your sending domain. SPF, DKIM, and DMARC. This is part of the integration, not an afterthought. Gmail and Yahoo now require it, and without it your beautifully-synced data drives emails that land in spam.

---

The details most brands miss

• Onsite tracking not firing. The number one silent failure. No onsite tracking means no browse data. Test it: view a product logged in as a known profile and confirm the event appears in Klaviyo.
• Historical backfill. Let Shopify backfill order history before you launch flows, so profiles are populated with real purchase behaviour and your segments work on day one.
• Started Checkout vs Added to Cart confusion. Triggering the cart flow on the wrong event either misses recoverable revenue or chases people who were never really in checkout.
• Catalog not connected. Dynamic blocks quietly fail, and your “abandoned cart” email shows a generic layout instead of the actual product the customer left behind.

Get these right and the integration does what it is supposed to: turn Shopify’s first-party data into flows that recover revenue. Get them wrong and you have a connected integration that is only doing half its job, which is worse than obvious, because everything looks fine on the surface.

---

Klaviyo and WooCommerce

WooCommerce works with Klaviyo, but the integration is thinner than Shopify’s and needs more hands-on setup. You install the Klaviyo plugin, connect it, and add the onsite tracking script manually. Order and customer data sync well; browse tracking and catalog integration take more configuration than Shopify’s near-automatic setup.

The practical guidance: WooCommerce plus Klaviyo is a perfectly good stack, but budget for a more careful setup and verify each event is flowing rather than assuming parity with Shopify. The flows, segmentation, and deliverability principles are identical once the data is connected.

---

Klaviyo and HubSpot

This one is a different question, because HubSpot is not an ecommerce platform, it is a CRM and marketing-automation tool built for B2B and lead nurture. Brands connect Klaviyo and HubSpot when they run a consumer store on Klaviyo and a B2B or wholesale pipeline on HubSpot, and want the two to talk.

The integration keeps contact data in sync between the two systems so a lead in HubSpot and a customer in Klaviyo are not living in separate silos. If your business is purely DTC ecommerce, you do not need HubSpot in the stack at all, Klaviyo covers it. If you genuinely run both a consumer store and a sales pipeline, syncing them is worth doing. We break down where each tool fits in our Klaviyo vs ActiveCampaign comparison, which covers the same ecommerce-vs-CRM trade-off.

---

The engineering mindset

An integration is plumbing. If one pipe is not connected, everything downstream runs dry, and it does it quietly. That is why we treat integration setup with the same precision as flight-control systems: verify every event, confirm the backfill, test the tracking, authenticate the domain, then build. A flow built on a half-connected integration will always underperform, no matter how good the copy is.

If you want your Klaviyo integration set up right the first time, or audited to find what is silently not firing, that is exactly what our Klaviyo setup and Klaviyo agency teams do. Already on the wrong platform and want to move? We handle migrations to Klaviyo regularly. Book a free audit and we will tell you what is connected, what is not, and what it is costing you.

---

Sources

• Klaviyo, Shopify Integration
• Google, Email Sender Guidelines