I’m having trouble getting dynamic variables to work in my abandoned cart flow using the "Add to Cart" event. I’ve integrated Klaviyo with PrestaShop, and the event data is being captured correctly (I can see properties like AddedItemProductName, AddedItemPriceInclTax, AddedItemImageURL, etc. in the event's properties). However, when I use these variables in my email templates (e.g., {{ event.AddedItemProductName }}, {{ event.AddedItemPriceInclTax }}), they don’t render in the emails.
Am I missing something in how I’m referencing the variables, or is there an issue with the PrestaShop integration?
Please note that I’ve successfully set up a flow and dynamic variables using “started checkout” event.
I see a support ticket on this, I’m sharing with the broader community as well:
In Klaviyo, the "Add to Cart" event is inherently designed to handle data on a per-item basis. This means that each "Add to Cart" event only captures information for a single item added to the cart. This behavior is consistent across different platforms, including PrestaShop, WooCommerce, and others. Therefore, when using the "Add to Cart" event, you would typically use static tables or variables in your email templates to handle the data for one item at a time. Events like "Started Checkout" and "Placed Order," on the other hand, capture all items involved in the event, which is why dynamic tables work better for these cases.
If you need to capture and display multiple items added to the cart before checkout, you can certainly do this via a custom event. You would need to track the data on your end and then send a request to Klaviyo’s events APIs. You can implement this either client-side using the Create Client Event endpoint or server-side using the Create Event endpoint. I hope this helps!
I see a support ticket on this, I’m sharing with the broader community as well:
In Klaviyo, the "Add to Cart" event is inherently designed to handle data on a per-item basis. This means that each "Add to Cart" event only captures information for a single item added to the cart. This behavior is consistent across different platforms, including PrestaShop, WooCommerce, and others. Therefore, when using the "Add to Cart" event, you would typically use static tables or variables in your email templates to handle the data for one item at a time. Events like "Started Checkout" and "Placed Order," on the other hand, capture all items involved in the event, which is why dynamic tables work better for these cases.
If you need to capture and display multiple items added to the cart before checkout, you can certainly do this via a custom event. You would need to track the data on your end and then send a request to Klaviyo’s events APIs. You can implement this either client-side using the Create Client Event endpoint or server-side using the Create Event endpoint. I hope this helps!
By clicking “Accept All Cookies,” you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts.
Privacy Preference Center
Your Privacy
Strictly Necessary Cookies
Performance Cookies
Functional Cookies
Targeting Cookies
Site Analytics
Your Privacy
When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.
Privacy Notice
Strictly Necessary Cookies
Always Active
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
Performance Cookies
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
Functional Cookies
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
Targeting Cookies
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Site Analytics
These cookies record your visit to our website, and are used to track your visit including information such as: web page interactions (clicks, hovers, focus, mouse movements, browsing, zooms and other interactions), referring web page/source through which you accessed the Sites, heatmaps and scrolls, screen resolution, ISP, and statistics associated with the interaction between device or browser and the Sites. If you are accessing our Services with a European IP address, you have been asked to consent to the use of these cookies (you are free to deny your consent).