Complete Klaviyo Integrations Guide for Shopify DTC Brands (2026)

You're doing $2M a year on Shopify. Klaviyo is set up — welcome series live, abandoned cart flow running. You're attributing maybe 18–22% of revenue to email. Someone on your team (or a thread on Twitter) tells you that integrating Recharge, Yotpo, and Postscript will "unlock another 30% of revenue." You spend three weekends wiring things up. Now your profiles are full of duplicate events, your flows are firing twice, and your deliverability has quietly cratered.

This guide is the one I wish existed when we were doing this the hard way.

I've now set up or audited Klaviyo integrations for over 40 Shopify DTC brands between $1M and $20M ARR. The difference between a clean, high-performing integration stack and a bloated mess comes down to sequencing, intentionality, and knowing which apps are actually worth the noise they introduce into your data layer.

Here's exactly what to build, in what order, and what it'll cost you.

---

Your Situation (And Why It's Different From Generic Advice)

At $1M–$5M ARR, you're probably running Shopify with the native Klaviyo integration, one SMS tool, maybe a review app, and a popup. Your email revenue percentage is decent but not great — likely 20–30% when it should be 35–45% for a brand at your stage.

At $5M–$10M ARR, you've added some complexity. Subscriptions via Recharge or Skio, possibly a loyalty program, maybe post-purchase tools. Your flows are getting unwieldy. You're not sure which integrations are pulling their weight.

At $10M–$20M ARR, you have a real stack — but it's accumulated organically, not designed. You've got attribution conflicts, profile pollution from apps that aren't scoped properly, and a data layer that nobody fully understands.

The pain at all three stages is the same: you don't have a framework for deciding what belongs in Klaviyo and what doesn't.

This guide gives you that framework.

---

Start Here: The Native Shopify Integration Is Non-Negotiable

Before anything else, your Shopify–Klaviyo native integration needs to be configured correctly. This sounds obvious. Most brands get it wrong.

The native integration tracks six core events by default: viewed_product, added_to_cart, started_checkout, placed_order, ordered_product, and refunded_order. These are the foundation every flow is built on. If any of these are misfiring — or if you've installed a third-party order tracking app that's doubling up on placed_order events — your attribution is already broken.

Three things to verify right now:

Event deduplication. Go to your Klaviyo activity feed for a test profile. Place a test order. You should see exactly one placed_order event and one ordered_product event per line item. If you're seeing two, you've got a duplicate event source — usually a second order sync app or a custom webhook that was added before you turned on the native integration.

Historical sync depth. Klaviyo lets you sync up to five years of Shopify order history. Do it. Your ecommerce customer segmentation and win-back flows are only as powerful as the historical data behind them.

Customer properties. Make sure accepts_marketing, total_spend, order_count, and predicted_lifetime_value are populating on profiles. These are the properties your VIP segments depend on.

Once the native integration is clean, everything else layered on top will perform correctly. Build on a shaky foundation and you'll spend months debugging.

---

Tier 1: The Five Integrations That Directly Unlock Revenue

These aren't "nice to have." For most Shopify DTC brands at $2M+, each of these has a direct, measurable impact on email-attributed revenue within 60–90 days of proper setup.

1. Recharge — Subscription Event Intelligence

If you have a subscription product and you're not piping Recharge events into Klaviyo, you're leaving serious money on the table.

Recharge sends 14 event types to Klaviyo: subscription_created, subscription_cancelled, subscription_paused, charge_failed, upcoming_charge, and more. Most brands that install Recharge only use charge_failed for a dunning flow. That's the floor, not the ceiling.

One supplement brand we worked with had Recharge installed but no subscription-specific flows in Klaviyo — just their standard post-purchase sequence. We rebuilt their integration to fire distinct flows off subscription_created (an onboarding sequence built for LTV, not one-time buyers), upcoming_charge (a pre-charge engagement email to reduce cancellations), and subscription_cancelled (a structured win-back sequence, not a generic "we miss you"). Email revenue as a share of total revenue went from 21% to 33% in 90 days — a 32% lift in absolute email revenue.

The key is tagging subscription vs. one-time buyers as a profile property so your campaigns segment cleanly. Subscribers are not the same customer as a one-time purchaser, and ecommerce subscription marketing demands a different message cadence.

2. Yotpo — Reviews and Loyalty as Behavioral Triggers

Yotpo's Klaviyo integration fires events when a customer submits a review, earns loyalty points, redeems a reward, or hits a loyalty tier. These are powerful behavioral triggers that most brands ignore entirely.

The flows to build:

• Post-review thank you — triggered off submitted_review, personalised by star rating. A five-star reviewer gets an upsell. A three-star reviewer gets a support touchpoint.
• Loyalty tier upgrade — triggered when a customer hits Gold or VIP tier. This is one of the highest-engagement emails you'll ever send.
• Points expiry reminder — triggered 30 days before points expire. Open rates on these consistently hit 45–55% in our client accounts.

The ecommerce loyalty programs playbook only works when your loyalty platform is talking to your email platform. Yotpo-to-Klaviyo is how you close that loop.

3. Justuno — Intelligent Popup-to-Profile Enrichment

Most popup tools just capture an email and a phone number. Justuno goes further — it can capture quiz answers, product preferences, and attribution data at the point of signup, and sync all of that to Klaviyo as custom profile properties.

Why this matters: a subscriber who tells you at signup that they're shopping for "sensitive skin" or "size XL" or "building muscle" is dramatically more valuable to segment than a generic email address. Your welcome series can branch immediately based on what they told you, rather than spending three weeks inferring it from browse behavior.

We set this up for a skincare brand at $4M ARR. Welcome series CVR went from 3.1% to 5.7% because the first email was actually relevant to the subscriber's stated concern. That's not magic — it's ecommerce email personalization done at the point of capture.

4. Postscript — SMS as a Klaviyo-Adjacent Channel

Postscript is, in my view, the best SMS platform for Shopify DTC at the $1M–$10M range. It's Shopify-native, the compliance tooling is solid, and its Klaviyo integration is well-documented.

The integration does two critical things: it syncs opt-in status bidirectionally (so a subscriber who opts out of SMS in Klaviyo is suppressed in Postscript, and vice versa) and it lets you trigger Postscript flows from Klaviyo events. That means your abandoned cart flow can send an email at hour one, an SMS at hour four, and another email at hour 24 — all from one decision point in Klaviyo.

If you're spending money on paid acquisition and not recovering abandoned carts via SMS, you're paying to acquire customers you can't fully convert. Postscript-Klaviyo together closes that gap.

5. Attentive — SMS for $10M+ Scale

At $10M ARR and above, Attentive is the SMS platform worth the premium. Its integration with Klaviyo is more sophisticated than Postscript's — it supports two-way profile sync, suppression list mirroring, and revenue attribution that doesn't conflict with Klaviyo's own attribution window.

The main reason brands at this stage move to Attentive isn't features — it's list size and deliverability infrastructure. Attentive's carrier relationships and compliance monitoring are built for brands sending millions of messages per month. Postscript starts to show its limits around 200K subscribers.

The integration setup here is more complex. You need to align attribution windows between both platforms, define which channel "owns" which customer touchpoint, and set up proper UTM parameters so Google Analytics doesn't double-count. Worth getting an agency who's done this before rather than winging it — the SMS compliance risk alone justifies it.

---

Tier 2: The Five Integrations That Mature Accounts Add

These integrations don't unlock revenue on day one. They add depth, reduce churn, and build the kind of lifecycle data that makes your email program significantly smarter over 6–12 months.

1. Shopify Flow — Trigger Emails From Any Store Event

Shopify Flow lets you create custom automations inside Shopify — and fire custom events to Klaviyo as the action. This unlocks things the native integration doesn't cover: "customer tagged as wholesale," "order flagged as a gift," "product out of stock for a specific variant," "order refunded more than twice."

For brands running complex operations, Shopify Flow is what bridges your operational logic to your marketing layer. It's free. Use it.

2. Skio — Subscription Analytics and Cohort Data

Skio is a Recharge alternative with stronger cohort analytics and a cleaner customer portal. Its Klaviyo integration is nearly identical to Recharge's event schema, so if you're migrating from Recharge to Skio (a move more brands are making in 2026), your existing flows don't need a rebuild.

What Skio adds beyond Recharge is better churn prediction data — it surfaces subscribers who are likely to cancel before they cancel, which you can pipe into Klaviyo as a predictive property and trigger a pre-emptive retention flow.

3. Wonderment — Order Tracking Triggers

Post-purchase is where most brands are weakest. The standard "your order has shipped" email is a transactional checkbox. Wonderment turns shipping events into a behavioral trigger layer: delay detected, package stalled, out for delivery, delivered.

Each of these maps to a Klaviyo event you can build a flow on. A delay detection email that empathises, explains, and offers a small gift — sent automatically when a package stalls for 48 hours — consistently generates 15–20% reply rates and dramatically reduces "where's my order" support tickets. That's your post-purchase experience working properly.

4. Malomo — Branded Tracking Pages With Re-Engagement

Where Wonderment focuses on email triggers, Malomo focuses on the tracking page itself. It replaces the carrier's tracking page with a branded experience that can display product recommendations, loyalty points balances, and review request CTAs.

Malomo sends click and view events from the tracking page to Klaviyo. A customer who clicks a product recommendation on their tracking page while waiting for their first order is a highly qualified second-purchase signal. Build a flow on that event. We've seen second-purchase rates improve by 8–12 percentage points when this is set up correctly.

5. Loop Returns — Turning Returns Into Retention

Loop returns fires return_initiated, return_approved, and exchange_completed events to Klaviyo. That's your returns experience — which for most DTC brands is a churn risk — turned into a retention opportunity.

A customer who initiates a return and exchanges for a different size or variant is still a loyal customer. They deserve a different post-return sequence than a customer who returned for a refund and went quiet. Ecommerce returns strategy isn't just operational — it's a lifecycle marketing lever.

---

Custom API Setup: When You've Outgrown Native Integrations

At $10M+ ARR, or if you're running a headless Shopify build, native integrations stop being sufficient. You need server-side event tracking.

The core issue: browser-based tracking (the default for most Klaviyo integrations) is increasingly unreliable. iOS privacy changes, ad blockers, and cookie restrictions mean that 20–35% of your viewed_product and added_to_cart events may never reach Klaviyo. Server-side tracking sends events directly from your backend — or from Shopify's servers — to Klaviyo's API, bypassing the browser entirely.

This matters most for browse abandonment flows. If you're only capturing 70% of product views, your browse abandonment trigger rate is 30% lower than it should be — and that's a significant revenue gap at scale.

The Klaviyo API also lets you write custom profile properties that no native integration supports: customer quiz scores, predicted next order date, churn risk tier, lifetime margin (not just revenue). These properties become the backbone of your most sophisticated segments. If you're thinking seriously about behavioral data and AI-driven personalization, you need these properties populated cleanly before any AI layer can do useful work.

For headless builds specifically — Hydrogen, Next.js storefronts — you'll need to implement Klaviyo's JavaScript snippet manually and map custom events to Klaviyo's event schema. This is a developer job, not a marketing job. Budget 15–20 dev hours for a proper implementation.

---

Deliverability Integrations: The Infrastructure Most Brands Ignore

You can have perfect integrations and still see declining performance if your sending infrastructure is wrong.

DMARC and DKIM. These aren't optional in 2026. Gmail and Yahoo's bulk sender requirements make DMARC with at least p=quarantine a hard requirement if you're sending over 5,000 emails per day. Use a DMARC reporting tool — Postmark's free tier or Dmarcian — to pipe aggregate reports so you can see who else is sending on your domain. The Gmail/Yahoo compliance requirements aren't going away, and the brands ignoring them are seeing inbox placement tank.

BIMI. Brand Indicators for Message Identification lets your logo appear next to your sender name in Gmail and Apple Mail. It requires a Verified Mark Certificate (VMC), which costs $1,200–$1,500 per year, and your DMARC policy needs to be at p=reject. At $5M+ ARR, the brand recognition lift is worth it. At $1M ARR, it's not the priority.

Dedicated IP. Klaviyo auto-assigns dedicated IPs at 50,000+ monthly email sends. If you're below that threshold, stay on the shared IP pool — it's actually better maintained than most brand-managed dedicated IPs. If you've been assigned a dedicated IP and haven't warmed it properly, deliverability is your first problem to fix before anything else.

---

The Phased Roadmap: Week 1 → Month 1 → Quarter 1

Don't try to build everything at once. This is the sequencing we use with every new client.

Week 1 — Foundation Audit and Cleanup

• Audit native Shopify integration for duplicate events
• Verify all six core events are firing cleanly
• Set up DMARC/DKIM if missing
• Confirm historical order sync is complete
• Document which integrations are currently installed and what events each one fires

Month 1 — Tier 1 Revenue Integrations

• Integrate Recharge or Skio and build subscription-specific flows (created, paused, cancelled, charge failed)
• Integrate Yotpo or your review app and build post-review and loyalty tier flows
• Integrate Postscript or Attentive based on your list size
• Set up proper SMS-email coordination for abandoned cart
• Audit popup tool — switch to Justuno if your current tool isn't enriching profiles

Quarter 1 — Tier 2 Depth + Custom Properties

• Implement Wonderment or Malomo for post-purchase tracking triggers
• Set up Loop Returns events and build return/exchange-specific sequences
• Implement server-side event tracking if you're at $10M+ or running headless
• Build out custom profile properties using Shopify Flow for operational events
• Review deliverability infrastructure — BIMI rollout if appropriate

---

What NOT to Integrate: The Junk That Breaks Your Stack

This is the section that saves you the most pain.

Any app that duplicates placed_order without proper deduplication logic. Common culprits: third-party order confirmation apps, AfterShip when configured alongside native Shopify tracking, some Google Shopping feed apps. If you're unsure, check the activity feed on a test profile after an order and count how many times the event fires.

Review apps that aren't Yotpo, Okendo, or Stamped. Smaller review apps often have buggy Klaviyo integrations that fire events with inconsistent property schemas. Your flows break silently because the event fires but the properties your conditional splits rely on aren't populated. The Klaviyo email metrics guide becomes very confusing when half your events are incomplete.

Loyalty apps that sync the entire points ledger on every change. Some loyalty integrations write a new Klaviyo event every time points change — every order, every email open that earns points, every small bonus. At scale, this floods profile activity feeds and makes automation logic almost impossible to build cleanly. Check your integration's event frequency before switching it on.

Multiple popup tools simultaneously. I've audited brands running Klaviyo's built-in forms, Privy, and a third-party quiz tool all at once — each syncing slightly different profile data for the same subscriber. The profile becomes a mess of conflicting properties. Pick one capture tool. Do it well.

---

Cost Breakdown by ARR Tier

Here's what a realistic integration stack costs, excluding Klaviyo itself.

Integration	$1M ARR	$5M ARR	$20M ARR
Recharge / Skio	$99–$299/mo	$299–$499/mo	Custom
Yotpo Reviews + Loyalty	$199/mo	$499/mo	$999+/mo
Justuno	$99/mo	$199/mo	$399/mo
Postscript / Attentive	$100–$300/mo	$500–$1,500/mo	Attentive custom
Wonderment	$99/mo	$199/mo	$399/mo
Loop Returns	$99/mo	$199/mo	$399/mo
Malomo	$49/mo	$99/mo	$199/mo
BIMI / VMC	—	$1,200/yr	$1,200/yr
Custom API dev (one-time)	—	$2,000–$5,000	$5,000–$15,000
Total monthly	~$700–$900/mo	~$2,000–$3,200/mo	~$4,000–$6,000/mo

At $1M ARR, the full Tier 1 stack costs roughly 1–1.1% of revenue per month. If you're not generating at least 8–10x that in incremental email revenue from the integrations, something in your setup or flow logic is broken.

At $20M ARR, the combined stack is 0.2–0.3% of revenue. At that point the question isn't whether to build it — it's whether you have the internal team or agency to run it properly. The best Klaviyo agencies at that tier are worth the investment specifically because the setup complexity is high enough that bad configurations cost more than agency fees.

---

Your DTC Marketing Stack Is a System, Not a Collection of Apps

The brands that do this well treat their Klaviyo integration layer as infrastructure — designed, documented, and maintained. They audit it quarterly. They remove apps that aren't contributing events to active flows. They keep their profile schema clean.

The brands that struggle treat Klaviyo integrations like a plug-and-play app store: install everything that looks useful, fix problems when they surface, wonder why attribution doesn't add up.

Your DTC brand marketing stack should be built around your data layer, not around your app subscriptions. Every integration you add should answer one question before you turn it on: what new event or property will this create, and what will I do with it?

If the answer is "I'm not sure yet" — wait.

If you're ready to audit what you have or build what you're missing, we do this for Shopify DTC brands every week. Reach out and tell us your current stack and ARR — we'll tell you exactly what's worth building next.