Full Answer

Testing the Klaviyo WooCommerce integration requires verifying three independent data paths — server-side order sync, client-side browsing tracking, and form submission flow.

Start with a test purchase. Use a real email address, not a disposable one, because Klaviyo may flag disposable domains. Complete the full checkout process including payment — use a small-value product or a coupon code that reduces the total. Within minutes, navigate to Klaviyo's Activity Feed and search for the Placed Order event associated with your test email. Open the customer profile and verify the order timeline shows the correct product names, quantities, and order total.

Next, test browsing behavior. Log in to your WooCommerce store with the same test email and visit several product pages. Return to the Klaviyo profile and check for Viewed Product events. These events rely on the JavaScript snippet and will not appear if the snippet is missing, blocked by an ad blocker, or loaded through Google Tag Manager with delayed execution.

Test form submissions by completing a Klaviyo signup form on your site. Verify the submission appears in Klaviyo, the subscriber is added to the correct list, and any connected welcome flow triggers.

Finally, validate the server-side connection. The Klaviyo plugin settings page in WordPress displays connection status indicators for both API keys. A failed connection typically means an incorrect private key or a server-level firewall blocking outbound requests to Klaviyo's API endpoints.

Run these tests after every WooCommerce core update, theme change, or caching plugin configuration change. Each of these modifications can silently break one or more of the three data paths without producing a visible error.