Klaviyo Abandoned Cart Flow Troubleshooting: Why Only 12% Fire

If your abandoned cart flow barely fires—say, ~12% of abandoners—you’re almost certainly facing one of three problems: your flow isn’t eligible to start, the trigger metric (usually Started Checkout) isn’t reaching Klaviyo reliably, or the data is arriving too late or malformed to qualify. This guide shows Shopify and WooCommerce teams exactly how to diagnose and fix it, from 60–90 second checks to advanced server-side safeguards.

Key Takeaways

• Low firing rate is typically a data or eligibility issue—verify Started Checkout and Added to Cart volumes and timing first.

• Client-side tracking gets blocked by cookie consent, ad blockers, or duplicate snippets; fix those before changing your flow logic.

• Shopify’s native abandoned emails and strict filters can quietly suppress entries—audit them early.

• For headless, CMP-heavy, or unreliable client-side setups, use server-side events with deduplication to restore coverage.

The 60–90 Second Checklist (Klaviyo abandoned cart flow troubleshooting)

Run these fast checks before you dive deep:

1. In Klaviyo → Integrations → Shopify, confirm the store is Connected and that Track behavioral events (and Viewed Product, if separate) is enabled. See Klaviyo’s guidance in Enable onsite tracking for Shopify and the automatic Added to Cart migration.

2. In Klaviyo → Analytics → Metrics, search for Started Checkout and Added to Cart; confirm they show activity in the last 24 hours and that volumes look reasonable for your traffic.

3. Open a recent profile (Audience → Profiles), click an event, and compare the occurrence time vs Klaviyo’s registration time; if events are delayed by many hours, metric-triggered flows may skip them.

Authoritative references: Klaviyo docs on onsite tracking and metrics visibility provide exact UI touchpoints and behavior details. See Enable onsite tracking for Shopify and Troubleshooting placed order tracking in the Help Center.

What Usually Breaks

Most “only 12% firing” issues trace back to blocked or missing events, duplicate scripts, or platform conflicts. Use this table to map symptoms to likely causes and fixes.

Sources for patterns and fixes appear throughout Klaviyo’s Help Center and developer docs, plus Shopify’s guidance on abandoned checkout emails.

Troubleshooting, Step by Step

Beginner: sanity-check the obvious

• Flow status & eligibility. In the flow builder, resolve alerts, and make sure every email/SMS is set to Live (not Draft/Manual). Confirm the trigger is the intended metric (typically Started Checkout). Review entry and exclusion filters—overly strict filters can gut entries. Use View flow history to spot recent edits that changed behavior. See Klaviyo’s Troubleshooting a flow.

• Confirm data exists and is fresh. In Analytics → Metrics, verify Started Checkout and Added to Cart have recent events. On a profile’s Activity Details, check that the registration time is close to the occurrence time; large delays can disqualify events from metric-triggered flows. See Troubleshooting a metric-triggered flow.

• Turn off Shopify’s native abandoned emails. In Shopify Admin → Settings → Checkout → Customer emails → Abandoned checkouts, disable the native reminders to avoid overlap and confusion. Shopify’s Abandoned cart recovery emails article shows where to find this.

Intermediate: integration, consent, and theme health

• Duplicate or outdated klaviyo.js. On Shopify, ensure you don’t have both an app-embed and an old manual theme snippet. Search theme.liquid for klaviyo and company_id. Duplicates can create profile messiness and broken events. Fix by removing extra snippets and ensuring only one Klaviyo account is connected. See Klaviyo’s Troubleshooting viewed product tracking and related community notes.

• Consent/cookie banners (CMP). Many CMPs block Klaviyo cookies (e.g., __kla_id) and scripts until consent. If forms don’t render or events don’t fire pre-consent, you may see a sharp drop in Active on Site, Viewed Product, Added to Cart, and Started Checkout. Configure your CMP to allow Klaviyo per policy and fire events after consent. Klaviyo’s OneTrust setup guide explains the pattern.

• WooCommerce specifics. There isn’t a first-party WooCommerce plugin that auto-enables behavioral events like Shopify’s app. Teams typically add Klaviyo’s JS manually or via GTM and/or adopt server-side forwarding for reliability. Check for plugin conflicts, CDN/firewall blocks, and consent settings. Validate in the browser network tab that klaviyo.js loads and events post successfully.

Advanced: server-side reliability and event engineering

• Implement server-side events. For headless checkouts, strict CMPs, or ad-blocked clients, forward Started Checkout and Added to Cart server-side using Klaviyo’s Track API. Include a stable identifier (email, phone, or hashed customer ID), a unique_id for deduplication, and set time to the actual occurrence time to avoid late-arrival skips. See Klaviyo’s API-based website activity events and custom integration FAQs.

• Test and validate. Use a test profile. Send a server-side Started Checkout event and watch for it in Analytics → Metrics and on the profile. Confirm the event’s occurrence time and registration time are close; large lags may block flow entry.

• Keep deduplication clean. Klaviyo deduplicates by metric + unique_id. If you send both client- and server-side versions, ensure unique_id is consistent, or use mutual exclusion filters between “native” and “server-side” metrics to avoid duplicates.

Practical Example/Workflow: restoring the trigger with server-side forwarding

If client-side tracking is unreliable due to CMP rules or a headless checkout, you can add a server-side safety net. One neutral way is to use a first-party tracking and forwarding tool to send Started Checkout to Klaviyo in real time with a unique_id and an identified profile. For example, a workflow using a managed solution can forward checkout events with first-party identifiers, so Abandoned Cart flows trigger even when klaviyo.js is blocked. You would then configure Klaviyo filters to prevent double-triggering between native and server-side metrics and monitor lift by comparing entries over a 14-day window. For a concrete integration reference, see the Klaviyo integration overview on Attribuly, which describes supported server-side events and how they appear in Klaviyo’s Metrics list with clear labeling. This approach doesn’t change your email copy or timing; it simply restores the missing trigger so your existing flow can run.

Reference: Attribuly integration overview — https://attribuly.com/integrations/klaviyo/

Developer Appendix: payload, dedup, and a tiny curl

Here’s a high-level server-side payload structure for Klaviyo’s Track API. Use deterministic IDs, include a unique_id for deduplication, and set time to the event’s occurrence (UNIX seconds).

{
    "data": {
      "type": "event",
      "attributes": {
        "profile": { "$email": "customer@example.com" },
        "metric": { "name": "Started Checkout" },
        "properties": {
          "unique_id": "CHK_12345",
          "$value": 149.00,
          "items": [{"ProductID":"SKU-1","Quantity":1,"Price":149.00}]
        },
        "time": 1713403200
      }
    }
  }
  

A minimal curl example (replace placeholders; send with your private API key):

curl -X POST https://a.klaviyo.com/api/events/ \
    -H "Authorization: Klaviyo-API-Key <PRIVATE_KEY>" \
    -H "Content-Type: application/json" \
    -d '{
      "data": {"type":"event","attributes":{
        "profile":{"$email":"test@yourbrand.com"},
        "metric":{"name":"Started Checkout"},
        "properties":{"unique_id":"TEST_CHK_001","$value":59.00},
        "time": '$(date +%s)'
      }}}'
  

Consult Klaviyo’s developer docs for API usage and monitoring guidance.

Benchmarks & What “Healthy” Looks Like

• Cart abandonment is common: the Baymard Institute’s meta-analysis estimates an average abandonment rate above two-thirds, which is why these flows matter.

• In Klaviyo’s benchmark reporting, automations (including abandoned cart flows) repeatedly outperform campaigns on engagement and placed order rates, but your recovery depends on consent rates, traffic mix, and offer strategy. Healthy setups often see substantially higher trigger coverage than 12% once events are captured reliably.

• For timing, abandoned cart sequences frequently start within a few hours, with 2–3 messages tested. Ranges and exact tactics vary—optimize with A/B testing rather than copying a template.

Helpful references:

• Baymard Institute on average cart abandonment. https://baymard.com/lists/cart-abandonment-rate

• Klaviyo’s benchmarks and abandoned cart setup guidance. https://www.klaviyo.com/products/email-marketing/benchmarks • https://help.klaviyo.com/hc/en-us/articles/115002779411

Audit Worksheet & Bug-Report Template

Quick audit checklist (copy/paste):

• Flow is Live; trigger = Started Checkout; entry/exclusion filters reviewed; delays make sense.

• Klaviyo → Integrations → Shopify: Connected; Track behavioral events ON; Viewed Product ON if separate.

• Analytics → Metrics: Started Checkout and Added to Cart volumes present in last 24h.

• Profile Activity Details: registration time ≈ occurrence time (not hours late).

• Shopify native abandoned emails disabled.

• Theme health: no duplicate klaviyo.js; only one Klaviyo account connected.

• CMP configured to allow Klaviyo cookies/scripts post-consent; forms render.

• For WooCommerce: JS loads without errors; no CDN/firewall blocks; consider server-side events.

Bug-report template (send to Klaviyo or your developer):

• Flow URL/ID; trigger metric; entry/exclusion filter screenshots; message statuses.

• Integrations settings screenshots (Shopify toggle states).

• Two example profiles expected to enter but didn’t: event timestamps + registration times.

• Network/API logs for your manual test event; sample payload (no PII; hash where appropriate).

• Theme/app changes in the last 7 days; CMP configuration snapshot.

Next Steps

If client-side fixes still leave gaps, explore a server-side path to get Started Checkout into Klaviyo reliably and deduplicated. For a managed route and documentation on supported server-side events, review the Klaviyo integration overview from Attribuly: https://attribuly.com/integrations/klaviyo/.