Klaviyo Shopify Integration
We connect Klaviyo to Shopify and Shopify Plus properly — clean event tracking, server-side events for headless and custom checkouts, back-in-stock, and UK-compliant consent. When the native one-click integration isn't enough, this is the team that builds the rest.
Our Klaviyo integration process
- Audit the connection. We check what's actually flowing into Klaviyo — Active on Site, Viewed Product, Started Checkout, Placed Order, Fulfilled and Refunded Order — and where events are missing, duplicated, or firing without identity. Most broken Klaviyo setups fail here, not in the flows.
- Fix the event layer. Repair or rebuild tracking: native Shopify integration for standard stores, plus client-side onsite tracking and the server-side Events API (POST /api/events/) for headless Hydrogen storefronts and custom checkouts the native connector can't see.
- Build flows + back-in-stock. Abandoned checkout, browse abandonment, post-purchase, and win-back flows wired to real events — plus back-in-stock subscriptions (Email and SMS) including custom catalog feeds for headless and B2B catalogues.
- Verify consent + deliverability. Profile-level email and SMS consent captured to UK GDPR / PECR standards, sending-domain authentication checked, and a real-order replay to confirm event integrity before we hand back.
What's included
- Native Shopify ↔ Klaviyo integration configured correctly — onsite tracking, catalogue sync, and the standard e-commerce metrics firing with proper customer identity
- Server-side event tracking via the Klaviyo Events API for headless (Hydrogen) storefronts and custom checkouts the native connector cannot reach
- Abandoned checkout and browse-abandonment flows triggered by Started Checkout and Viewed Product events — not nightly batches
- Back-in-stock subscriptions across Email and SMS, including custom catalog feeds for headless and B2B variant catalogues
- UK-compliant consent: email and SMS consent captured per profile, double opt-in where required, aligned to GDPR and PECR
- Event-integrity guarantees — unique event IDs to deduplicate retried webhooks, plus a reconciliation pass so Klaviyo matches Shopify
Integration timeline
Typically 1-3 weeks
A standard store with a healthy native integration is mostly a configuration and flow build — 1-2 weeks. A headless Hydrogen storefront or custom checkout that needs server-side event tracking, custom catalog feeds, and consent rework is 2-4 weeks. We confirm a window in writing once the audit shows which events are actually missing — the cost driver is almost always the headless/custom event layer, not the flows.
FAQ
- Does Klaviyo have a native Shopify integration, or do I need a custom build?
- Klaviyo ships a native, one-click Shopify integration, and for a standard Online Store it's the right starting point — we'll configure it rather than bill you for custom work. You need a custom build when the native connector can't see your events: headless Hydrogen storefronts, custom or third-party checkouts, multi-store setups that share one Klaviyo account, or bespoke events you want to trigger flows on. We scope both and recommend the cheaper option that actually works.
- Which Shopify events does Klaviyo track?
- The native integration captures the standard e-commerce metrics: Active on Site, Viewed Product, Started Checkout, Placed Order, Ordered Product, Fulfilled Order, Cancelled Order, and Refunded Order. These power the core flows — abandoned checkout fires on Started Checkout, post-purchase on Placed Order. For anything beyond the standard set, we send custom events to the Klaviyo Events API so they appear as metrics you can segment and trigger flows on.
- Can Klaviyo work with a headless Shopify (Hydrogen) storefront?
- Yes, but not out of the box. The native integration's onsite tracking is built around the Online Store theme, so a headless Hydrogen storefront needs two things wired manually: client-side onsite tracking via Klaviyo's browser library for Active on Site and Viewed Product, and the server-side Events API for Started Checkout, Placed Order, and fulfilment events. We build both layers and verify identity stitching so a logged-in customer's onsite and server events land on one profile.
- How do you set up back-in-stock alerts in Klaviyo for Shopify?
- Klaviyo back-in-stock works through a back-in-stock subscription tied to a catalog variant, and it can notify on Email or SMS. For a standard Shopify store the catalogue syncs natively. For headless storefronts, custom variants, or B2B catalogues, we set up a custom catalog feed so the right variant IDs exist in Klaviyo for the subscription to reference — without that, the alert has nothing to watch.
- Will the integration keep our SMS and email consent UK-compliant?
- Yes. Consent is captured at the profile level in Klaviyo, with email and SMS treated as separate consent channels, and we configure double opt-in where your sending strategy or jurisdiction requires it. We align the setup to UK GDPR and PECR so marketing consent is explicit and auditable — important because Klaviyo will send to whatever consent state your integration writes, correct or not.
- How do you stop duplicate orders or events in Klaviyo?
- Server-side events are sent with a unique event ID, so a webhook Shopify retries — which it routinely does — updates the existing event rather than creating a second Placed Order. We pair that with a reconciliation pass that diffs Klaviyo metrics against Shopify orders, so revenue reporting in Klaviyo matches what Shopify actually processed rather than drifting over time.
- How much does a Klaviyo Shopify integration cost?
- Configuring and fixing a native integration with a flow build typically runs £3K-£8K. A headless or custom-checkout build with server-side event tracking, custom catalog feeds, and consent rework is usually £8K-£20K. We share firm pricing in writing after the audit — the variable is how much of your event layer the native connector already covers versus what we have to build server-side.