We are in the process of integrating our inventory management and order administration system, Booqable, with Klaviyo, to automate transactional and marketing email/SMS campaigns based on rental periods.
Our goal is to create a segment containing a series of gift card numbers that correspond to specific territories in our inventory system. When an order is received in Booqable and includes a gift card number from this pre-defined list, we want to trigger an automated workflow that sends scheduled SMS and email notifications aligned with the rental period.
We would greatly appreciate your guidance on the following:
Segment Creation: How can we create a segment in Klaviyo that dynamically includes a list of gift card numbers related to a specific territory?
Data Sync: What is the best way to ensure seamless integration between Booqable and Klaviyo to automatically update this segment when a new order with a matching gift card number is placed?
Automated Workflows: How to set up email/SMS flows triggered by changes in order status, ensuring timely communications throughout the rental period?
Best Practices: Are there any recommended best practices for handling such segmentation and automation to optimize performance and ensure accuracy?
Your insights and recommendations on the feasibility of this approach would be incredibly valuable to us.
Are you still working on setting up your integration? Happy to provide some insight here.
Segment Creation:
If you’re looking to create a segment of everybody with a certain set of gift card numbers, you should ensure that these gift card numbers are all within a defined range. When you segment based on a number property, you can create conditions such as “PROPERTY is at least/is at most/is greater than or equal to/ect”. If you want to make a segment that contains everybody who has a certain type of gift card, the definition would look like “Gift Card Number is at least 123456 AND Gift Card Number is at most 234567”, for instance.
Are these gift cards assigned to profiles in Klaviyo yet? If not, I’d recommend downloading a CSV file from your platform containing the email addresses of these profiles in one column, and their gift card numbers in another. From there, you can upload it to Klaviyo, and the corresponding gift card number will be assigned as a profile property for each individual. This doc here does a great job explaining how to do this, if you haven’t uploaded profile properties into Klaviyo before.
Data Sync:
Zapier is definitely an option. There are quite a few custom integrations that developers have made over the years, and Booqable may already have one. I’d recommend checking out Zapier to see if one exists, (It looks like one does) and exploring it or reaching out to the developer to determine if it would send over the right info to Klaviyo.
If you don’t see any existing integration you can use, I’d recommend checking out the APIs on our developer portal. There are lots of really useful API calls you can make that can help you create profiles, subscribe profiles, send events to Klaviyo, pull reports, update profiles with properties, and much much more. People use these calls all the time to develop new integrations.
If you want to attach a gift card number to somebody’s profile, you could use our Create Event endpoint to create an event that triggers when some action is taken on your store. Inside this endpoint, you can add event and profile properties that you can use to segment with.
Automated Workflows:
If you’ve managed to send events to us using our Create Event endpoint and profile and subscription data by using our Create Profile and Bulk Subscribe Profiles endpoints, you’re probably ready to make a flow. Splits/filters and all flow features are available, even for flows triggered by custom events like the ones you plan to create.
Best Practices:
I think I went over some best practices above, but I’d love to hear more about what you’re trying to accomplish, so I can point you in the right direction. Let me know if I can help out with anything else.
Thanks for reaching out! Your use case sounds exciting, and here’s how you can do it:
Segment Creation: Use custom properties or tags to upload the gift card numbers into Klaviyo. These can then be used to dynamically segment customers based on matching data from Booqable orders.
Data Sync: Utilize a middleware tool like Zapier or a custom API integration to sync data between Booqable and Klaviyo. Ensure the integration updates custom properties or triggers events in real-time when relevant orders are placed.
Automated Workflows: Use the synced data (e.g., gift card number or order status updates) to create event-triggered flows in Klaviyo. Include conditional splits to align communications with the rental period milestones.
Best Practices:
Regularly validate data syncing between Booqable and Klaviyo to avoid gaps.
Test workflows with sample data to ensure correct triggers and timing.
Leverage SMS/email A/B testing to optimize messaging for engagement.
If you’d like tailored assistance or examples, feel free to reach out directly!
Thank you for your response and detailed recommendations. I appreciate your insights and would like to provide some feedback and follow-up questions regarding the suggested solutions:
Segment Creation: I attempted to use custom properties; however, I couldn’t figure out how to simultaneously upload a list of 200 gift card numbers linked to a specific location by importing them from an Excel file. Could you provide guidance or best practices for bulk importing such data into Klaviyo?
Data Sync: Our developer has initially considered using Zapier (Make) or webhooks for integrating Booqable with Klaviyo. We are exploring the feasibility of these approaches and would appreciate any insights or recommendations you might have regarding their implementation and potential challenges.
Looking forward to your response and further guidance. Thanks again for your help!
Are you still working on setting up your integration? Happy to provide some insight here.
Segment Creation:
If you’re looking to create a segment of everybody with a certain set of gift card numbers, you should ensure that these gift card numbers are all within a defined range. When you segment based on a number property, you can create conditions such as “PROPERTY is at least/is at most/is greater than or equal to/ect”. If you want to make a segment that contains everybody who has a certain type of gift card, the definition would look like “Gift Card Number is at least 123456 AND Gift Card Number is at most 234567”, for instance.
Are these gift cards assigned to profiles in Klaviyo yet? If not, I’d recommend downloading a CSV file from your platform containing the email addresses of these profiles in one column, and their gift card numbers in another. From there, you can upload it to Klaviyo, and the corresponding gift card number will be assigned as a profile property for each individual. This doc here does a great job explaining how to do this, if you haven’t uploaded profile properties into Klaviyo before.
Data Sync:
Zapier is definitely an option. There are quite a few custom integrations that developers have made over the years, and Booqable may already have one. I’d recommend checking out Zapier to see if one exists, (It looks like one does) and exploring it or reaching out to the developer to determine if it would send over the right info to Klaviyo.
If you don’t see any existing integration you can use, I’d recommend checking out the APIs on our developer portal. There are lots of really useful API calls you can make that can help you create profiles, subscribe profiles, send events to Klaviyo, pull reports, update profiles with properties, and much much more. People use these calls all the time to develop new integrations.
If you want to attach a gift card number to somebody’s profile, you could use our Create Event endpoint to create an event that triggers when some action is taken on your store. Inside this endpoint, you can add event and profile properties that you can use to segment with.
Automated Workflows:
If you’ve managed to send events to us using our Create Event endpoint and profile and subscription data by using our Create Profile and Bulk Subscribe Profiles endpoints, you’re probably ready to make a flow. Splits/filters and all flow features are available, even for flows triggered by custom events like the ones you plan to create.
Best Practices:
I think I went over some best practices above, but I’d love to hear more about what you’re trying to accomplish, so I can point you in the right direction. Let me know if I can help out with anything else.
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).