PrestaShop data reference

Estimated 5 minute read

|

Updated Feb 18, 2026, 12:00 AM EST

Table of contents

You will learn

Learn about the metrics and customer data synced from PrestaShop to Klaviyo. 3 types of events sync from PrestaShop to Klaviyo:

  • Order events sync every 30 minutes (e.g., Placed Order).
  • Transactional order events sync in real time, if you choose to enable them in your module settings (e.g., Placed Order Transactional).
  • Klaviyo onsite events (Active on Site, Viewed Product, and Added to Cart).

PrestaShop data reference - 图1

PrestaShop data reference - 图2

List of PrestaShop API metrics in Klaviyo

List of PrestaShop API metrics in Klaviyo

Transactional versus non-transactional metrics

If you toggled on Send real-time order events to Klaviyo when integrating, a second set of order events labeled as transactional will sync to Klaviyo in real time. For instance, you’ll see a metric in Klaviyo labeled Placed Order Transactional, which will sync in real time, in addition to a metric labeled Placed Order, which will sync every 30 minutes. The real-time transactional events that sync to Klaviyo are:

  • Placed Order Transactional
  • Fulfilled Order Transactional
  • Cancelled Order Transactional
  • Refunded Order Transactional

Transactional events toggle on in Klaviyo plugin settings in PrestaShop

Transactional events toggle on in Klaviyo plugin settings in PrestaShop

A metric labeled Transactional does not automatically give the emails it triggers transactional status. Learn how to use flows to send transactional emails, including how to request transactional status for your messages.

PrestaShop metrics

You can view all PrestaShop metrics in Klaviyo by navigating to Analytics > Metrics. Filter by PrestaShop to see order and transactional order events (they will have a PrestaShop icon) or filter by API to see Klaviyo onsite events (they will have a gear icon).

Active on Site

This event is created when a customer is active on your PrestaShop store.

Viewed Product

Klaviyo tracks this event when a customer views a product on your PrestaShop store. This is useful if you'd like to set up a browse abandonment flow or provide customers with personalized product recommendations based on product browsing data.

Added to Cart

This event is created when a customer adds an item to their cart.

Started Checkout

The Started Checkout metric is created when:

  • A customer logs in to their account, adds something to their cart, and navigates to the checkout page.
  • Without logging in, or using guest checkout, a customer adds something to their cart, navigates to the checkout page, and enters their email address.

Klaviyo captures the value of a cart at the time of checkout, as well as other pertinent details of a customer's cart that you can use for personalized abandoned cart emails. The event includes the following data:

  • Language The language used.
  • CartID An ID assigned to the cart.
  • ItemsThe names of the products in the cart, e.g., Red T-shirt or Blue Pants.
  • ItemCount The number of items in the cart.
  • TotalDiscounts The total amount of any coupons or discounts if someone used a code, e.g., 10.00.
  • Categories The complete set of categories for the products in the cart, e.g., t-shirts, men's, pants, and sale.
  • TagsThe list of meta keywords for the products in the cart.
  • ShopIdThe ID of the shop associated with the cart.
  • ReclaimCartUrlA URL that can be used to rebuild the customer’s cart, for instance in an abandoned cart email.
  • $event_idThe ID of this Started Checkout event.
  • $value The value of the cart.
  • $extra Additional cart data for personalizing emails.
  • external_catalog_id Used in catalog organization in Klaviyo.
  • integration_key Your ecommerce platform (PrestaShop).

Placed Order, Fulfilled Order, Cancelled Order, and Refunded Order

All of these events are created based on the order status mapping you configured when integrating. Each event includes product information about the items purchased, including product names, categories, etc. These events include the following data:

  • $valueThe total value of the order.
  • $extra Additional order data for personalizing emails.
  • CategoriesThe complete set of categories for the products in the order, e.g., t-shirts, men's, pants, and sale.
  • ItemCountThe number of items in the order, e.g., 2.
  • Items The names of the products in the order, e.g., Red T-shirt or Blue Pants.
  • ShopIdThe ID of the shop associated with the order.
  • LanguageIdThe numeric PrestaShop language ID associated with the order, e.g., 1.
  • TotalDiscounts The total amount of discounts applied to the order, e.g., 10.00, whether or not a discount code was used.
  • DiscountCodes Any discount or coupon codes someone used towards the order, e.g., SPRING10.
  • TagsThe list of meta keywords for products in the order.
  • OrderStatusThe status of the order, as configured in order status mapping, e.g., Payment Accepted.
  • external_catalog_id Used in catalog organization in Klaviyo.

Ordered Product

This event is tracked once for each unit of a product in an order, up to 100 events per order line item. For example, if a customer buys 2 t-shirts and 1 pair of jeans, 1 Placed Order event is tracked along with 3 Ordered Product events.

The event Klaviyo tracks includes detailed information about each product someone purchases. This is useful when creating behavioral segments based on product options and other detailed information that's not available for filtering in the Placed Order event. Ordered Product events include the following data:

  • NameThe name of the ordered product.
  • SKU The SKU of the ordered product.
  • ProductId The ID of the ordered product.
  • QuantityAlways 1, because each event represents 1 unit of the product.
  • CategoriesThe complete set of categories for the product, e.g., t-shirts, men's, and sale.
  • TagsThe list of meta keywords for the product.
  • $event_id An ID associated with this Ordered Product event.
  • $valueThe price of 1 unit of the ordered product, including tax.
  • $extra Additional product data for personalizing emails.
  • external_catalog_id Used in catalog organization in Klaviyo.

Synced customer data

In addition to the metrics Klaviyo syncs from PrestaShop, Klaviyo will also create a unique profile for every customer that we sync. When we sync contact information, there are also certain custom properties that may get added to each Klaviyo profile. Here are the properties automatically synced from PrestaShop:

  • Email, First and Last Name, City, State/Region, Zip Code, Country, Phone NumberThese built-in Klaviyo fields are automatically populated with all available data from PrestaShop.
  • $localeThe language and country tag of the store the customer interacted with (e.g., “en-us”).
  • $locale-language The language tag derived from the $locale property (e.g., “en”).
  • $locale-country The country tag derived from the $locale property (e.g., “us”).
  • Last Order CurrencyThe currency of the customer's last order.
  • BirthdayThe customer's birthday.
  • GenderThe customer's gender.
  • PrestaShop Account Created DateThe date on which the customer created their PrestaShop account.
  • PrestaShop Default GroupThe default PrestaShop group that the customer belongs to.
  • PrestaShop GroupsAll PrestaShop groups that the customer belongs to.
  • PrestaShop ShopsThe shop(s) with which a customer has interacted.

Additional resources

Learn how to integrate your PrestaShop store with Klaviyo. Klaviyo is PrestaShop’s preferred marketing automation partner. This process involves 2 steps: installing a free module (PrestaShop Automation with Klaviyo) in PrestaShop and enabling the integration within Klaviyo. This article also provides information about monitoring your data sync, setting up transactional emails, and updating your module so that you can grow with Klaviyo. - How to use flows to send transactional emails

Learn how to set up important transactional emails inside Klaviyo that are triggered when your subscribers purchase or interact with your brand. Customers expect these emails and will search for them in their inbox. For this reason, transactional emails are sent to almost all customers and should not contain any marketing content.

Was this article helpful?

YesNo

Use this form only for article feedback. Learn how to contact support.

Explore more from Klaviyo

Community

Connect with peers, partners, and Klaviyo experts to find inspiration, share insights, and get answers to all of your questions.

Visit Community

Partners

Hire a Klaviyo-certified expert to help you with a specific task, or for ongoing marketing management.

Hire a partner

Support

Access support through your account.

Email support (free trial and paid accounts) Available 24/7

Chat/virtual assistance Availability varies by location and plan type

Log in