Hi @double d, welcome to the community!
Since you have a custom integration with Klaviyo, I want to point out that you can also leverage the built-in Klaviyo “Back in Stock” trigger/feature via the API as well. You can see documentation and a guide for that here:
The way Klaviyo handles items that come back in Stock is fairly robust, it lets you adjust how many people to notify relative to your stock, and how much time to allot for each notification before it notifies the next batch. If you’re not familiar with the Back in Stock feature, you can learn more about it here:
If for some reason, that’s not something you want to implement, you can also build a custom HTML Form that submits an email to a designated List with a hidden form values with the product name (and any other information like sizes or variants) that maps to custom profile properties. Then, you can build a Segment based on those custom profile properties to notify people when you have stock. Note, one limitation is that this implies that user can only put themselves on a waitlist for a single product at a time. You can see this documentation on building custom HTML forms here:
Another way to do this is to build a form, that that submits the email along with the product name as a “custom metric” in Klaviyo. Though this is a bit more involved, it lets users waitlist on more than one product over time. Since you have a custom Klaviyo implementation, passing in this metric should be no different then other custom events you’ve already implemented, except this one is based users submitting for a product waitlist.
Hope that helps!
Hello and thank you for your input.
I read the API and flow setup documentation and was confused with the wording - sometimes it mentions Back in stock as a feature, othertimes as an event so I was assuming that if we create it, it will not be available as an API metric within the segment metric list (used for creating segments). I realise now that if we implement this BIS feature, it will appear in the segment API metric list as all other custom metrics we developed and hence we will be able to create segments of BIS subscribers.
And in the next phase, we will definately implement a flow as well.
Best regards
