Klaviyo Connector for WooCommerce — store events, profiles and subscriptions in Klaviyo

Klaviyo Connector for WooCommerce connects your store to Klaviyo through the official API. Klaviyo flows — abandoned cart, browse abandonment, thank-you, win-back — are only as good as the events they receive. This plugin sends them from WooCommerce itself, in the background, without duplicates and with one private key: the checkout never waits for Klaviyo. Running OpenCart? See Klaviyo Connector for OpenCart.

Before you install: if the official Klaviyo for WooCommerce plugin is active in your store, deactivate it. Two plugins send the same orders with different ids, and Klaviyo counts them twice.

How it was tested — honestly. Klaviyo offers no sandbox. The plugin is built on the official documentation (Klaviyo OpenAPI, revision 2026-07-15) and tested end to end in a test store against a simulation of the API written from that documentation: block and classic checkout, HPOS, PHP 7.4 and 8.3, multi-currency, Polylang, the Complianz consent banner. We also ran the format of our events through the live Klaviyo API’s own validation and compared its answers to a wrong key with what the plugin expects. The first real Klaviyo account it runs on is our client’s; you can try it on yours with the 7-day Pro trial. The log shows every request and Klaviyo’s answer, and if Klaviyo answers differently from its documentation, we fix it quickly.

What the shopper sees

Nothing changes for the shopper except one discreet checkbox. They browse, add to the cart and go to the checkout. As soon as they finish typing a valid e-mail, the store records Started Checkout — not on every keystroke, so no half-typed profiles appear in Klaviyo. If they leave, the abandoned-cart e-mail carries a link that brings back exactly their cart: products, variations, quantities and coupon, in any browser on any device.

The “Email me news and offers” checkbox is never pre-ticked, and you write its text. Whoever ticks it joins the Klaviyo list you chose with marketing consent (on a double opt-in list Klaviyo first sends a confirmation e-mail). Whoever does not gets the usual order e-mails and nothing promotional.

What the store gets

• Abandoned carts that come back. Started Checkout with the full cart and a link that restores it — the base of Klaviyo’s abandoned-cart flow.
• Orders without duplicates. Placed Order and Ordered Product go from the server through WooCommerce hooks, once per order, however often the payment gateway changes the status. The value is what the customer paid, in the order currency.
• Segments that work. Every line carries its price after discounts with and without tax, SKU, categories, brand, image and link; the order carries coupons, shipping and address. The profile gets name, phone in E.164, address and the order language.
• Proof of consent. The answer, the time and the exact checkbox wording are kept on the order, and an order note tells whether the subscription went through.
• Peace of mind on staging. The key is tied to the site address: a copy of the database on a test domain sends nothing to the live Klaviyo account until you confirm.

What the admin gets

Settings live in WooCommerce → Klaviyo. On the “Connection” tab you paste the private key and press “Check the connection”: the plugin reads the account, fills in the public key and loads your lists. The “Tracking” tab switches events on, sets which statuses count as placed and the cookie consent mode. “Consent” holds the list and wording of the checkbox and its place in the classic checkout.

Every order has a Klaviyo box: what the customer answered and what this order has already sent to Klaviyo. From there you can also send Placed Order by hand for an order created before the plugin was installed.

The “Queue & log” tab shows the queue and every API call of the last 30 days: response code, time, Klaviyo’s error text. “Send now” and “Retry failed” buttons, and “Copy diagnostics” collects what our support needs — without the key.

How it works, step by step

1. In Klaviyo: account settings → API keys page → create a private key (Full access, or Custom with the scopes from the FAQ).
2. Deactivate the official Klaviyo plugin if it is installed.
3. Install the plugin, paste the key on the “Connection” tab and press “Check the connection”.
4. On the “Consent” tab choose the Klaviyo list for the newsletter checkbox and, if you like, your own wording.
5. If your site has a cookie banner, pick it on the “Tracking” tab (WP Consent API, Complianz, Cookiebot or your own).
6. Place a test order with a real e-mail (not example.com) and check Klaviyo: Analytics → Metrics → Placed Order, the customer profile, the list subscription.
7. Build your Klaviyo flows on Started Checkout, Viewed Product and Placed Order — the plugin already fills them.

Pro: the whole order life cycle and the catalog

Pro adds Fulfilled Order (at the status you choose, with tracking numbers), Canceled Order and Refunded Order — every refund, partial ones too. Metric names are Klaviyo’s own, and Canceled and the first refund carry the same unique_id as Placed Order, which is how Klaviyo subtracts them from customer lifetime value (CLV).

The product catalog sends products and variations with price, stock, images and categories — for product blocks in e-mails, recommendations and back-in-stock flows. A product or stock change reaches Klaviyo a minute later; nothing unchanged is sent again. Past orders of 3–60 months go with their original dates and start no flows: nobody gets a “thanks for your order” for last year’s purchase.

Under the hood

• Klaviyo’s official REST API, revision 2026-07-15 pinned in one place; Klaviyo supports a revision for two years.
• Own queue table with a unique job key + Action Scheduler: a hook firing twice cannot queue a second order. Every event has a stable unique_id, so a retry never duplicates it in Klaviyo.
• A 429 with Retry-After pauses the whole queue for exactly that long without spending an attempt; 5xx and network errors retry with a growing pause up to 6 hours; a refusal with Klaviyo’s text stays visible in the log.
• Cookie consent: before consent klaviyo.js is not loaded and no Klaviyo cookie is set.
• The shopper’s language comes from the pages they browsed, so the block checkout (REST) and the classic one (wc-ajax) get the right language with Polylang and WPML.
• PHP filters for every event, order line, profile and catalog item.
• Uninstalling removes settings, queue, log and saved carts; consent records on orders stay — they are the store’s proof of consent.

How to install

1. Download the zip with the “Download free” button at the top of the page.
2. WordPress → Plugins → Add New → Upload Plugin → choose klaviyo-connector-for-woocommerce-1.0.0.zip → Install → Activate.
3. WooCommerce → Klaviyo → paste the private key → “Check the connection”.
4. For Pro: “Licence” tab → enter the licence key or press “Try Pro for 7 days”.