Hi. I’d like to bring in a field from customer order data (event) into Klaviyo as I would like to use this data in flows:
For a Woocommerce subscription product - the _delivery_date is generated automatically based on the customer post code & order date. When the subscription is renewed, the delivery date changes to the upcoming delivery date.
Objective: I would like to use this event to trigger a flow to send an email on the Monday before delivery - “reminding people to make any changes before delivery” & on the delivery date to send a “Your order is coming today - don’t forget to put your boxes out for collection”.
How do I bring this field from Woocommerce into Klaviyo so I can do this?
(Oh and would these flows be considered transactional?)
Best answer by david.to
Love the strategy you are using!
Since this custom field of
_delivery_date is not a default field synced to Klaviyo, I would recommend leveraging Klaviyo’s API to sync this data to Klaviyo. You can find resources on how Klaviyo’s API functions to sync this custom data from the articles below:
- Getting Started with Klaviyo APIs
- Track and Identify API Reference
- Klaviyo API Documentation
- Setting Up API-based Transactional Events
- Setting Up API-based Website Activity Events
- Integrate a Standard Ecommerce Platform
- Integrate a Subscription Ecommerce Platform
- Technical Terms Glossary
For this particular use case, I would recommend either syncing this custom field as its own custom event/metric to allow you to build a metric triggered flow off of it. Alternatively, you can also use the API to sync this
_delivery_date field as a custom profile property which would allow you to build a date triggered flow off of this data. Since this would be a custom solution, we would recommend reaching out and working with developer you are familiar with or finding a Klaviyo partner who can assist in this endeavor to achieve your goal.
Furthermore, since these emails would pertain to a customer’s order with important information, so long as they adhere to Klaviyo’s transactional email guidelines found in the Guide to Using Flows to Send Transactional Emails article, these emails can certainly be considered transactional. Keep in mind that transactional emails are an essential, non-marketing email and would not contain any marketing materials. Once your flow and email are created with your desired content, you can request the email be marked as transactional by contacting our Customer Success team and use the subject line "Transactional Email Request" while including the below information in your message body:
- URL link(s) to the flow(s)
- Flow name(s)
- Subject line of the email(s) that are transactional
Hope this helps! Thanks for being a member of the Community!