Klaviyo Added to Cart Not Working on Shopify: Theme Update and Pixel Fixes (2026)

Quick Fix with Thunder

First Decide Which Added to Cart Event You Actually Need

Many Shopify stores used older Klaviyo snippets that listened to product form submissions and pushed a custom Added to Cart event. Newer Shopify integrations can rely on Shopify's tracked Added to Cart event through the integration and pixel path. After a theme update, the native Shopify event may continue working while the older custom Klaviyo metric goes quiet.

Before adding code back, check your Klaviyo flows. If abandoned cart flows can use the current Shopify Added to Cart event, clone and migrate them instead of keeping a duplicate legacy event alive. Duplicate add-to-cart events can over-trigger flows and muddy attribution.

For the storefront side of the same click, read the Shopify add-to-cart button guide and cart not updating until refresh guide.

Check Klaviyo App Embed, Shopify Pixel, and Consent

In Shopify admin, open the live theme customizer and verify the Klaviyo app embed is enabled if your setup depends on it. Then check Shopify customer events and Klaviyo integration settings. A theme update can publish a clean theme where the embed is off, even though the app is still installed.

Test with consent in mind. Use a clean browser profile, accept the cookie banner, view a product, add it to cart, then inspect both the browser network requests and the Klaviyo profile timeline. If the event fires only after consent, your tracking is working as configured.

Klaviyo's Shopify integration documentation and Shopify's Web Pixels API docs are safer references than old snippets copied from forums.

If You Keep a Legacy Event, Bind It Safely

Only keep a legacy Added to Cart event if you have a specific flow migration reason. If you do, avoid brittle selectors that break whenever the theme changes. Listen for the product form submit, wait for a successful cart response, and send one event.

document.addEventListener('submit', async (event) => {
  const form = event.target;
  if (!(form instanceof HTMLFormElement)) return;
  if (!form.matches('form[action*="/cart/add"]')) return;

  const variantId = new FormData(form).get('id');
  if (!variantId) return;

  // Prefer your platform's current Klaviyo/Shopify event path.
  // Do not fire this if Shopify's Added to Cart event already triggers the same flow.
  window._learnq = window._learnq || [];
  window._learnq.push(['track', 'Added to Cart', { VariantID: String(variantId) }]);
});

This simplified example is intentionally conservative. Production tracking should include product name, URL, image, price, collection, and quantity only after the cart mutation succeeds. Do not fire on invalid variants, sold-out products, or failed add-to-cart requests.

Avoid Duplicate Events, Broken Flows, and Slow Product Pages

The worst fix is adding another snippet without removing the old one. That can produce two Added to Cart events: one from Shopify's integration and one from legacy JavaScript. Klaviyo flows may then trigger twice, suppress incorrectly, or report inflated cart intent.

Search your theme for _learnq, Added to Cart, klaviyo, and old app snippets. Check theme.liquid, product templates, custom sections, and tag-manager containers. If an old snippet came from an app uninstall, use the app leftovers cleanup guide.

For performance, use the third-party JavaScript fix guide, Total Blocking Time guide, and complete Shopify speed optimization guide.

Manual Fix vs Thunder Fix

If you are choosing between app automation and hands-on cleanup, compare Thunder pricing, professional speed optimization, and the best Shopify speed apps guide.

FAQ