Klaviyo Integrations: The Ecommerce Stack That Matters

Klaviyo advertises more than 350 pre-built integrations. That number sells the platform, but it tells you very little about what you actually need. Across 800+ brands, the pattern we see is the same: a working ecommerce retention stack runs on six to eight integrations, wired properly, with every one of them either triggering a flow or feeding a segment. The other 340 are optional.

This is the hub for our integration guides. It covers the connections that matter for ecommerce, what each one sends and in which direction, and the setup details that decide whether they actually earn their place.

---

What are Klaviyo integrations?

Klaviyo integrations are connections that move customer data between Klaviyo and the other tools in your stack. Your store sends orders, carts and browsing. Subscription, review and helpdesk apps send their own events. Klaviyo sends segments out to ad platforms and, optionally, profile data back to your store. Each connection should power a flow or a segment.

As of September 2026, Klaviyo’s own integrations page groups them into ecommerce platforms, advertising, loyalty, helpdesk, shipping and logistics, subscriptions, and quizzes and surveys. The groups are useful. The question that matters for each one is simpler: what event does this give me, and what will I build on it?

---

The integrations that matter for ecommerce

Category	Common apps	What reaches Klaviyo	What you build with it
Store platform	Shopify, WooCommerce, BigCommerce	Orders, checkouts, carts, browsing, catalog	Every core flow: welcome, cart, browse, post-purchase, win-back
Subscriptions	Recharge	Subscription started, cancelled, upcoming order	Replenishment, cancellation save, upcoming-charge reminders
Reviews	Klaviyo Reviews, Judge.me, Yotpo, Okendo	Review requests and submitted reviews	Review request flows, review-based segments, UGC in emails
Helpdesk	Gorgias, Zendesk	Opened and resolved tickets, CSAT	Suppress promos during open tickets, post-resolution follow-ups
SMS	Klaviyo SMS (native), Attentive, Postscript	SMS consent, sign-up source, SMS events	Cross-channel flows and one consent record
CRM	HubSpot, Salesforce	Contacts, deal stages (via connectors)	B2B and wholesale routing alongside DTC
Advertising	Meta Ads, Google Ads	Meta lead ad sign-ups (segments go outbound)	Retargeting, suppression audiences, lookalikes, lead ad welcome flows

The rest of this guide goes through them in that order.

---

Store platforms: the integration everything else depends on

Shopify

Shopify is Klaviyo’s deepest integration and the one most brands start with. Per Klaviyo’s Shopify setup guide, you install it from Integrations > Explore apps, authenticate the store, choose which Klaviyo list receives customers who accept email marketing at checkout or through Shopify forms, then switch on onsite tracking through the Klaviyo app embed in your Shopify theme.

That app embed is where most setups go wrong. Without it you get orders but no browsing: no Viewed Product, Viewed Collection, Submitted Search, Added to Cart or Active on Site, which means no browse abandonment and much thinner segments. Klaviyo also notes that, depending on your Shopify Customer Privacy settings, it may not track onsite events for visitors in the EU, EEA, UK and Switzerland until they consent. If you sell into those markets, expect less browse data there and plan for it.

Data also flows back the other way, but only if you choose. The setting Sync profiles and profile data from Klaviyo to Shopify sends name, email, phone, email and SMS subscription status, email and SMS events, locale and custom properties to Shopify customer records. Turn it on if your team works in Shopify’s customer view or other Shopify apps read those fields. Leave it off if nothing downstream uses them.

The full walkthrough, including the four details most brands miss, is in our Klaviyo Shopify integration guide.

WooCommerce

WooCommerce connects through the free Klaviyo for WooCommerce extension. It syncs in real time via the WooCommerce REST API and sends Started Checkout, Placed Order, Ordered Product and Added to Cart, plus your catalog. It needs more care than Shopify: caching plugins, firewalls and checkout customisations can all break the connection without any obvious error. Setup, testing and abandoned cart on Woo are covered in our Klaviyo WooCommerce guide.

BigCommerce, Magento, Salesforce Commerce Cloud and others

Klaviyo lists pre-built integrations for BigCommerce, Magento, PrestaShop, Salesforce Commerce Cloud and Wix alongside Shopify and WooCommerce. For anything else, Klaviyo’s developer guide sets out the event model to rebuild: Active on Site, Viewed Product, Added to Cart and Started Checkout from the browser, Placed Order, Ordered Product, Fulfilled Order, Canceled Order and Refunded Order from the server, a historical sync, and a catalog feed. If a custom build skips any of those, the flows that depend on them will be missing too.

Checkout platforms: Checkout Champ

Brands that run checkout on a funnel platform rather than the store’s own checkout need the checkout platform connected too, or abandoned checkout and post-purchase flows go quiet. Checkout Champ’s Klaviyo plugin sends Started Checkout, Placed Order, Ordered Product, Fulfilled Order, Cancelled Order, Refunded Order and Subscription Restarted server-side. If the store is also connected to Klaviyo, check that orders don’t arrive twice. Setup and settings are in our Checkout Champ and Klaviyo guide.

---

Subscriptions: Recharge

For supplements, coffee, pet food and anything else on a replenishment cycle, the subscription platform holds the most valuable events in the stack. Recharge now builds and maintains its own Klaviyo integration. Per Recharge’s documentation, stores still on the legacy Klaviyo-built version must upgrade to the Recharge-built one.

Once connected, Recharge sends custom properties to each profile (with a backfill on install) and event metrics you can trigger flows from, including Subscription started on ReCharge, Subscription cancelled on ReCharge, Order upcoming on ReCharge and Order placed successfully on Recharge. Recharge’s own guidance is to replace its default notifications with Klaviyo flows built on those metrics, so the upcoming-charge reminder, the cancellation confirmation and the activation email all carry your branding and can be A/B tested.

Other subscription apps have their own vendor-built integrations; for Loop, see our Loop Subscriptions and Klaviyo guide, and for a side-by-side of the apps, our Shopify subscription apps comparison.

The revenue sits in what you do with them: a cancellation flow that offers a skip or swap before the subscriber leaves, an upcoming-order reminder that cross-sells, and segments that separate subscribers from one-time buyers so your campaigns stop offering a first-order discount to people already paying monthly.

---

Reviews apps

You have two routes:

• Klaviyo Reviews. Klaviyo’s native reviews product runs on Shopify and WooCommerce. Per Klaviyo’s help centre, it is billed separately from email and SMS, and review collection runs through a flow (there is a prebuilt Klaviyo Reviews: Review request flow in the library). The benefit is one profile: review data sits next to order data without a sync.
• A dedicated reviews app. Judge.me, Yotpo and Okendo all connect to Klaviyo. Judge.me, for example, can send review requests through Klaviyo flows and push new reviews back as an event, according to Judge.me’s help centre. Klaviyo can also import reviews from Yotpo, Okendo, Stamped, REVIEWS.io, Judge.me and Loox if you later consolidate.

Whichever you use, make sure the review request goes out from one place. The most common mistake we find is the reviews app sending its own request email while a Klaviyo flow sends another.

---

Helpdesk: Gorgias and Zendesk

Helpdesk integrations are the most underused connections in ecommerce Klaviyo accounts. They matter for one reason: you shouldn’t send a 20%-off promo to someone with an open complaint about a damaged order.

• Gorgias. Per Klaviyo’s Gorgias guide, it sends Opened Ticket, Resolved Ticket and satisfaction survey responses into Klaviyo in real time. Gorgias shows Klaviyo profile data, consent and custom properties to agents in return. There is no historic sync, so only activity after setup comes across.
• Zendesk. Per Klaviyo’s Zendesk guide, it syncs opened and resolved ticket metrics (for all brands or specific brands) and lets agents answer Klaviyo SMS and WhatsApp replies from inside Zendesk.

The build: a segment of profiles with a ticket opened in the last few days and not yet resolved, excluded from promotional campaigns, and a short post-resolution flow that asks for a review only when the survey score was good.

---

SMS tools

If you run SMS in Klaviyo, there is nothing to integrate: email and SMS consent live on one profile and one flow can branch between channels. If you run a separate SMS platform, the integration decides whether your two programs coordinate or collide.

Attentive is the most common pairing we see at larger brands. Its integration sends email sign-ups from Attentive forms into a Klaviyo list, syncs opt-outs between the two, and pulls Klaviyo segments into Attentive once a day. How that works in detail, and when consolidating makes more sense, is in our Klaviyo Attentive integration guide. For Shopify-only brands weighing the SMS specialist route, see Klaviyo vs Postscript.

---

CRMs and other email platforms

These are the integrations where search intent and reality diverge most.

• HubSpot. Klaviyo’s help centre says plainly that Klaviyo does not have a built-in HubSpot integration. Brands that run a DTC store in Klaviyo and a B2B or wholesale pipeline in HubSpot connect them with a partner app, a two-way sync tool, or Zapier. The options and trade-offs are in our Klaviyo HubSpot integration guide.
• Mailchimp. Klaviyo’s Mailchimp integration exists, but it is one-way and built for migration: it pulls audiences, subscription status, suppressions and 90 days of engagement into Klaviyo. Running both platforms at once needs a different approach. See our Klaviyo Mailchimp integration guide.
• Salesforce. Klaviyo integrates with Salesforce Commerce Cloud as a store platform. Connecting Salesforce as a CRM is a separate project, usually through a connector or custom API work.

---

Advertising: Meta and Google

Ad integrations mostly run outbound: Klaviyo sends segments to the ad platform. The one inbound exception is Meta lead ads.

• Meta Ads. Syncs Klaviyo lists and segments to Meta as custom audiences and can build lookalikes from them. Per Klaviyo’s Meta Ads guide, audience membership updates hourly on Klaviyo’s side, though Meta can take 24 to 48 hours to accept and process changes. It also syncs Meta lead ad sign-ups into Klaviyo in real time as a Filled Out Lead Ad event, with form answers saved as profile properties, so a lead ad can trigger a welcome flow straight away.
• Google Ads. Syncs segments for Customer Match. It only works if your Google Ads account is eligible for Customer Match, so check that before you plan a campaign around it.

The three audiences worth syncing on day one: recent purchasers (to exclude from acquisition spend), high-intent non-buyers (viewed product or started checkout, no order), and your top customers by predicted lifetime value as a lookalike seed.

---

How to audit the integrations you already have

Most accounts we audit don’t have too few integrations. They have too many, and some are fighting each other. Run this check once a quarter:

1. List every connected app in Klaviyo’s Integrations tab and every app with a Klaviyo API key. Revoke keys for tools you no longer use.
2. Map each one to a flow or segment. If an integration isn’t feeding anything, it’s adding profiles, properties and risk for no return.
3. Look for duplicate sends. Reviews apps, subscription apps and SMS platforms often ship with their own emails switched on. Two cart reminders or two review requests means one of them needs to go.
4. Check consent flows. Every tool that can subscribe or unsubscribe someone needs a clear answer to “which system wins?”. Conflicting consent is a compliance problem, not just a data one.
5. Test the events. Place a test order, open a test ticket, start a test subscription. Confirm each metric lands on the right profile within minutes.

This is also where the question of Klaviyo vs Mailchimp, or any other platform, usually gets settled. The platform with the deeper ecommerce integrations wins on the data it can act on, which is the argument we make in Klaviyo vs Mailchimp.

---

Getting it wired properly

Integrations are plumbing. Nobody sees them when they work, and when one fails nothing errors: a flow just goes quiet and revenue drifts down. If you want your stack mapped, tested and cleaned up, that is part of our Klaviyo setup service. If you’d rather start with a read on what is and isn’t connected, request a free Klaviyo audit. We’ll tell you which integrations are earning their place and which ones to switch off.