Shopping Cart
Overview
Klaviyo is only as good as the data your store sends it.
When browsing data gets lost to ad blockers, when profiles hold little more than an email address, or when a customer who unsubscribed in Klaviyo still shows up as subscribed in your store, your flows end up sending the wrong message to the wrong people.
This module sends data from your PrestaShop server through the Klaviyo REST API v3, and it also brings changes made in Klaviyo back into your store.
Why it’s worth it
🛡️ Browsing and cart data sent from the server
Product views and add-to-cart events go to Klaviyo from PHP, not from the visitor’s browser. Ad blockers and broken scripts don’t get to decide what Klaviyo sees, so your browse and cart abandonment flows reach more shoppers.
🌍 Multiple Klaviyo accounts in one store
Assign a separate Klaviyo account to any language and currency combination. Your Hungarian HUF storefront can report to one account and your English EUR storefront to another. The module picks the right API keys for every page view, event and API call, and falls back to your default profile when no override matches.
🔄 Newsletter status that stays in sync both ways
When someone unsubscribes in Klaviyo, the newsletter flag is cleared in PrestaShop. When they resubscribe, it’s set again. Incoming webhooks are verified with an HMAC signature. Manual setup works on every Klaviyo plan, and automatic registration is available on Klaviyo’s Advanced KDP plan.
📊 Customer profiles you can actually segment
More than 20 fields sync to each profile, including customer group, language, newsletter and opt-in status, guest flag, registration date and birthday. Purchase history comes along too: number of orders, total spent, average order value, and first and last order date. A segment like “spent over X but hasn’t ordered in 90 days” works from day one.
📐 RFM segments without a pricey add-on
Klaviyo ties RFM and cohort analysis to its separately priced analytics add-ons. The three pillars of RFM, meaning how recently a customer bought, how often they buy and how much they spend, arrive in our module as profile fields: last order date, number of orders and total spent.
With these you can build your own segments on any paid Klaviyo plan, such as your best customers, loyal customers who are drifting away, or one-time buyers worth winning back. Because the numbers are calculated from your PrestaShop orders, you can use them even if your store hasn’t reached the threshold Klaviyo needs for its predictive analytics.
🎟️ Coupons without manual exports
PrestaShop cart rules are updated in Klaviyo automatically when you create, edit or delete them. General codes go into the Klaviyo Coupons API pool, and customer-specific codes are added to that customer’s profile, so you can drop them straight into a flow.
Updates & version history
2.0.1 - 2020-10-03 11:27:11
Improvements
- Fully compatible with PrestaShop 1.6.1.x!
- List “API V2” feature added
- Sync of customers’ historical data
- Customers synced to a list defined by List ID
- The following customer data is synced to Klaviyo:
- customer_default_group: text
- has_membership: true / false
- is_guest: true / false
- prestashop-newsletter: true / false
- prestashop-sale-optin: true / false
- ps-active: true / false
- ps-date-add: January 01, 1970 at 01:00 AM
- ps-date-update: January 01, 1970 at 01:00 AM
- ps-deleted: true / false
- ps-newsletter-date-add: October 13, 2020 at 04:20 PM
- ps_lang: Magyar (Hungarian)
- New Delivery Started Order metric (lets you send a transactional email when shipping starts)
- New Cancelled Order metric
- New Refunded Order metric
- Full historical data can be re-synced. The last sync date can be cleared.
1.0.9 - 2020-05-13 14:00:46
MODULE IMPROVEMENTS
- The “Added to Cart” event is now sent, so you can track products being added to the cart.
- You can choose whether shipping cost is added to the cart value of cart-type events.
- The product description is sent with every event that includes product data.
- The product tags field (if filled in) is sent with every event type that includes product data.
- The custom catalog feed includes the product description and product tags.
- In the admin you can list the HTML elements to strip from the product description before sending.
BUG FIXES
- The “Customer Cart” event now tracks every change
- The “Started Checkout” event gets a unique event ID on every send, so the latest event always carries fresh data.
- Several smaller bugs fixed.
1.0.8 - 2020-05-02 11:27:11
Improvements
- Ajax Added to Cart events added
- Product description and tags added to events such as orders and product views
Fixes
- Shipping costs are included in the cart total - FIXED
🔍 11 events to build your flows on
Browsing: Viewed Product (name, SKU, categories, image, price and compare-at price) and Searched Site (with PrestaShop’s native search and IQIT search).
Cart and checkout: Added to Cart with quantity and value, Started Checkout, which fires on the checkout page rather than the cart, and Customer Cart, which syncs the active cart on every page load.
Orders: Placed Order and a separate Ordered Product event for each line item, plus Fulfilled, Cancelled, Refunded and Delivery Started Order, which you map to your own order statuses.
Order events are sent in batches by a cron job. With the recommended 5-minute schedule, new orders show up in Klaviyo within minutes.
How is it different from the official Klaviyo module?
Klaviyo’s free PrestaShop module is a solid starting point for a simple store. But if you sell in several languages or currencies, need browsing data to arrive even when shoppers use ad blockers, or want unsubscribes in Klaviyo to show up in your store, this is where the differences appear.
| WSC-Klaviyo | Official Klaviyo module | |
|---|---|---|
| Viewed Product and Added to Cart | ✅ Sent from the server, ad blockers can’t stop them | Klaviyo’s browser-based onsite tracking |
| Separate Klaviyo accounts by language and currency | ✅ Yes, with automatic key selection | Not documented; currencies can be converted to one standard currency |
| Unsubscribes synced back to the store | ✅ Yes, via HMAC-verified webhooks | Not documented |
| Coupons | ✅ Automatic sync of your existing cart rules | Import of coupons generated in the module |
| Order stats on the profile | ✅ Order count, total spent, average order value, first and last order | Not among the synced profile properties |
| Search event (Searched Site) | ✅ Native and IQIT search | Not among the documented events |
| Delivery started (Delivery Started Order) | ✅ Mapped to your own order status | Mappable events: Placed, Fulfilled, Cancelled and Refunded |
| Order event updates | ✅ Configurable, every 5 minutes recommended | Every 30 minutes, with optional real-time transactional events |
| Product catalog | ✅ Separate feed for each language and currency | A single catalog sync |
| API call log on your own server | ✅ Daily log file with status codes and errors | Not documented |
This comparison is based on Klaviyo Help Center articles on the PrestaShop integration, updated in February 2026.
💡 When is the official module enough?
If you sell in one language and one currency, and the accuracy of browsing data isn’t critical, Klaviyo’s free module may be a good fit. WSC-Klaviyo is built for stores where email and SMS flows bring in serious revenue and the business has outgrown a simple setup.
More features
📰 Newsletter signup
Works with PrestaShop’s default newsletter module and the newsletter forms of most themes. Signups go to Klaviyo instantly through Klaviyo’s client API, and your private key never appears on the storefront. You pick the Klaviyo list from a dropdown, double opt-in can be switched on or off, and subscription follows only the newsletter checkbox, not the partner offers one.
🗂️ Product catalog feed
A separate JSON catalog for each language and currency, with optional variant-level export. Cached feed files are 55–75% smaller than the raw product data, and inactive products are labeled with a category name you choose.
📈 Reports in the admin
A dashboard shows profile counts, list membership and event metrics.
🧾 Logging
Every Klaviyo API call is written to a daily log file with the method, URL and status code. For failed calls, the response body and cURL error are logged too, so when something goes wrong you can see exactly what happened.
🔐 Security
The private API key is used only on the server, the customer sync endpoint is protected by a token generated at install, and webhooks are accepted only with a valid HMAC signature.
⚙️ Technical details
| PrestaShop | 1.7.0+, 8.x and 9.x, with multistore support |
| PHP | 7.2 or later |
| Klaviyo API | REST API v3 (revision 2025-01-15) |
| Installation | ZIP upload in the PrestaShop back office |
| Requirements | Klaviyo public and private API keys, ability to run cron jobs on the server |
Set it up once and it works in the background.
Your flows get better because they work from more accurate data. If you have questions about setup or which option suits your store, get in touch and we’ll help you decide.
Screenshots and installation
