+2Hi, we are moving our e-commerce businesses away from WooCommerce and using custom integration and wordpress checkout.
How do I figured out what API calls I need to setup for all of the different transactional emails and customer interactions as well as “abandoned cart” etc emails and how to customize them using custom API calls since we won’t be able to use the WooCommerce integration?
Hopefully that makes sense.
+10
Yes! That makes sense. The easiest way to approach a custom WordPress / checkout setup is to start with the emails and flows you want, then map each one to the event that should trigger it and the data that email needs.
A typical setup would be:
In general, onsite behavior like product views and cart activity should be tracked client-side, while transactional events like orders and shipping are best sent server-side. For abandoned cart and checkout emails, make sure those events include product names, IDs, image URLs, product URLs, quantity, price, and a checkout or cart-recovery URL so the email can be personalized properly.
A few things to watch for:
The main thing Klaviyo can’t really promise is the exact cart rebuild / checkout link behavior, since that depends on how your developer builds the custom WordPress checkout. But if your dev team starts with those core events and payloads, that’s the right foundation.
Additional resources to check out:
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
