Troubleshooting
Klaviyo WooCommerce Integration Issues: A Simple Guide

Short answer
Most Klaviyo WooCommerce integration issues come from an outdated plugin, revoked REST API keys, plain permalinks, a firewall blocking Klaviyo, or caching plugins delaying its tracking script. Update the Klaviyo plugin, reconnect the integration, allow API requests in your security tools, and exclude Klaviyo scripts from optimisation.
Key takeaways
- The integration has two parts: API data sync and onsite tracking scripts.
- Revoked API keys and plain permalinks break the connection.
- Firewalls and security plugins often block Klaviyo's API requests.
- Script delay and combine options can stop cart and checkout events.
- Subscribers only join lists when the checkout consent box is enabled.
Why is your Klaviyo WooCommerce integration not working?
Klaviyo WooCommerce integration issues usually come from an outdated or inactive Klaviyo plugin, broken WooCommerce REST API access, a security plugin or firewall blocking Klaviyo, caching that strips tracking scripts, or a checkout that does not fire Klaviyo's events.
The symptoms vary. Orders may not reach Klaviyo, the Started Checkout flow may never trigger, product feeds may be empty, or sign-up forms may not appear on your store.
Most of these problems have simple fixes. This guide walks through them in the order that usually finds the cause fastest.
How does the Klaviyo WooCommerce integration work?
The integration uses the Klaviyo plugin on your WordPress site plus a connection in your Klaviyo account; Klaviyo pulls store data through the WooCommerce REST API, while the plugin adds onsite tracking and checkout events.
Two parts need to work together:
- Server-side sync. Klaviyo reads orders, customers and products from your store through API keys created during setup.
- Onsite tracking. A Klaviyo script on your pages records events such as Active on Site, Viewed Product and Added to Cart, and the plugin sends Started Checkout.
If one side breaks, you see partial data. For example, orders sync but product views do not. Knowing which side is failing points you to the right fix.
The official Klaviyo plugin on WordPress.org is the starting point for the WordPress side.
What should you check first?
Start by confirming the Klaviyo plugin is active and up to date, that the integration shows as connected in your Klaviyo account, and that your site loads over HTTPS without errors.
Quick checks:
- In WordPress, go to Plugins and make sure the Klaviyo plugin is active and updated.
- Update WooCommerce and WordPress too, after taking a backup.
- In Klaviyo, open your integrations and check the WooCommerce integration status for errors.
- Load your store in a browser and check for a valid SSL certificate.
- Note when the problem started and what changed around that time.
Klaviyo's own WooCommerce troubleshooting guide lists the current error messages and what they mean. Check it if your integration page shows a specific code.
How do you fix a failed connection or API error?
A failed connection is usually caused by missing or revoked WooCommerce REST API keys, plain permalinks, or the REST API being blocked, so reconnect the integration and make sure the WordPress REST API responds normally.
Try these fixes:
- Permalinks. Go to Settings > Permalinks and make sure it is not set to Plain. Save the page once to refresh the rules.
- API keys. In WooCommerce > Settings > Advanced > REST API, check that the key created for Klaviyo still exists with the right permissions. If it was deleted, reconnect from the Klaviyo plugin settings to create a new one.
- REST API health. Open Tools > Site Health and look for REST API errors. Our guide on fixing REST API errors in Site Health covers the usual causes.
The WooCommerce REST API documentation explains how keys and authentication work if you need more detail.
Is a firewall or security plugin blocking Klaviyo?
Yes, this is very common: security plugins, host firewalls and services like Cloudflare can block or challenge Klaviyo's requests to your API, which stops orders and products from syncing.
Signs of this problem include sync errors that mention 401, 403 or timeout responses.
To fix it:
- Check your security plugin's firewall log for blocked requests to /wp-json/wc/ paths.
- Allow those requests, or allowlist the integration according to your security plugin's instructions.
- If you use Cloudflare or a host firewall, check for bot challenges on the API path.
- Ask your host whether their server firewall blocks API traffic.
Do not turn off security completely. Instead, add a targeted rule. Our guide on Wordfence settings shows where allowlisting lives in one popular plugin.
Why are orders or products not syncing to Klaviyo?
Orders and products usually stop syncing because of API blocks, a stalled background sync, products that are hidden or private, or a very large catalogue that takes time to process after first connecting.
Work through these points:
- Give the first sync time. A large store can take a while to bring in historical data.
- Check product visibility. Drafts, private products and hidden products may not appear in catalogue feeds.
- Check background tasks. WooCommerce uses the Action Scheduler for queued jobs. If many actions are stuck as past due, background work may not run. See fixing past-due Action Scheduler actions.
- Check WP-Cron. If your host disables WP-Cron without a real cron job, scheduled tasks may not run.
If only some orders are missing, compare their status. Klaviyo may treat some statuses, like failed or draft orders, differently from completed ones.
Why is Started Checkout or Added to Cart not firing?
Cart and checkout events usually fail because the Klaviyo script is delayed or blocked, the shopper is not identified, or your checkout type is not supported by your plugin version.
Klaviyo can only send Started Checkout for a shopper it can identify, typically by email. A guest who never enters an email may not trigger it.
Check the following:
- View the page source and confirm the Klaviyo script is present.
- Exclude Klaviyo scripts from delay JavaScript or combine JavaScript options in your speed plugin.
- Test with an email address typed into checkout, then look for the event in that profile in Klaviyo.
- If you use the block-based checkout or a custom checkout plugin, check that your Klaviyo plugin version supports it.
Our comparison of WooCommerce cart and checkout blocks vs shortcode explains how the two checkout types differ.
Why are Klaviyo sign-up forms not showing?
Sign-up forms usually fail to show because onsite tracking is off, the Klaviyo script is blocked by a consent tool or script optimiser, the form's targeting rules exclude the page, or the form is not published in Klaviyo.
Check that the form is live in Klaviyo and that its targeting and display rules match the pages you are testing.
Test in a private window. Klaviyo forms can hide themselves from visitors who have already seen or closed them.
Cookie consent tools may block Klaviyo until a visitor accepts. That is often correct behaviour, so test after accepting cookies.
Why are customers not subscribed to email or SMS?
Customers are only added to lists when they give consent, so if subscribers are missing, check that the Klaviyo plugin's checkout consent checkbox is enabled and linked to the correct list in its settings.
The plugin lets you add opt-in checkboxes for email and SMS at checkout. If they are off, buyers become profiles but not list members.
Placing an order is not the same as agreeing to marketing. Laws such as the GDPR and similar rules elsewhere require clear consent for marketing messages.
This is general information, not legal advice. Our guide on making WooCommerce GDPR compliant covers the basics.
Klaviyo WooCommerce problems at a glance
Use this table to match the symptom you see with its usual cause and fix.
| Symptom | Likely cause | Fix |
|---|---|---|
| Integration shows an error | Revoked API keys or plain permalinks | Reconnect, set pretty permalinks |
| No orders or products syncing | Firewall or security block | Allow the API path, check logs |
| Partial or delayed data | Stuck background tasks | Check Action Scheduler and cron |
| No Viewed Product or Added to Cart | Tracking script delayed or blocked | Exclude Klaviyo from script optimisation |
| No Started Checkout | Shopper not identified or unsupported checkout | Test with an email, update plugin |
| Forms not showing | Targeting, consent tool or caching | Check form rules, clear cache |
| No new subscribers | Consent checkbox off | Enable checkout opt-in |
How do you find a plugin conflict?
If nothing above works, test for a conflict on a staging copy by disabling other plugins and switching to a default theme, then enabling them one at a time until Klaviyo breaks again.
Always do this on staging, not your live store. Turning off payment or shipping plugins on a live shop can lose real orders.
Our guide on how to find which plugin is causing a problem walks through the method step by step.
Clear every cache after each change. See how to clear cache in WordPress if you are not sure where your caches are.
When should you contact Klaviyo support?
Contact Klaviyo support when your integration shows errors you cannot explain, data stays missing after you remove blocks and conflicts, or the problem started right after a Klaviyo plugin update.
Send them clear details:
- Your WordPress, WooCommerce and Klaviyo plugin versions.
- The exact error shown on the integration page.
- An example order number or profile email that did not sync.
- What you have already tried.
You can also post on the plugin's support forum on WordPress.org or check the Klaviyo for WooCommerce listing for compatibility notes. Other store owners often report the same bug after an update.
Frequently asked questions
Why is Klaviyo not tracking WooCommerce orders?
Orders usually stop syncing because Klaviyo cannot reach your store's API. Check that the API keys still exist, permalinks are not set to Plain, and no firewall or security plugin is blocking requests to the WooCommerce API path.
Do I need the Klaviyo plugin for WooCommerce?
Yes. The Klaviyo plugin handles the connection setup, onsite tracking and checkout events. Without it, Klaviyo cannot collect the full set of store events used by flows such as abandoned cart.
Why is my abandoned cart flow not sending?
The flow depends on the Started Checkout event, which needs the shopper to be identified, usually by entering an email. Script delays, unsupported checkouts or a flow in draft mode can also stop it.
Does caching break Klaviyo on WooCommerce?
Page caching is usually fine, but plugins that delay or combine JavaScript can stop Klaviyo's tracking script from running. Exclude Klaviyo scripts from those settings and clear all caches after the change.
How long does Klaviyo take to sync a WooCommerce store?
A small store often syncs quickly, while a large store with many orders and products can take longer for the first historical import. New events after that should appear much faster.
Sources
- Troubleshooting your WooCommerce integration Klaviyo Help Center
- Klaviyo plugin WordPress.org
- Klaviyo for WooCommerce WooCommerce
- WooCommerce REST API Documentation WooCommerce
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


