Stripe and Klaviyo integration

Hey, 

Just revisiting this. With the method of uploading coupons, how do I add an expiry window for after it’s sent. For example, I want a coupon to be used in my win-back flow that will last for 48 hours from the time it is sent.

Thanks!

And this will link to our custom stripe checkout and have them expire there? Thanks :)

Hi David,

Thanks for this. I understand that  I have to upload them into stripe as well. However, I’m not sure how I’d go about setting the expiry date to a certain amount of time after an email send. So for our customer winback flow we’d like to send a discount code that will expire a week after the email is sent.

Thanks,

Ben

@David To :)

Ahh ok, we have a custom website and don’t use shopify. Do you have any recommendations on setting up customer winback flows if we can’t set variable expiry times in this way? Ideally we want to give only a certain amount of time for the codes to be used, to be sent, say after a month of their first order. Thanks!

Hey @brewcrew,

Some ways I’ve seen this accomplished is through the use of either a custom event or through the use of a custom profile property being updated via API. 

Custom events are highly flexible and customizable based on how they’re created. This means you can even stitch multiple events or logic together (in your backend) to trigger an event in Klaviyo. What I’ve seen are users making calls to the coupon API of the tool/app they’re using - in this case Stripe, to generate a dynamic coupon based on the logic they want. I.E. after a user’s first purchase. Then, they’ll pass that dynamic coupon code that was generated to Klaviyo through a custom event. This would then allow you to trigger a metric-triggered flow off of this event while calling that discount code in the email. 

The concept is similar when going through the custom profile property route. Instead of creating a custom event to pass the discount code that was generated through your third-party tool’s coupon API; the discount code is passed as a custom profile property. Going this route, you wouldn’t be able to trigger a flow off of a custom profile property being added or applied. But this would allow you to call the custom profile property and value containing the discount code in any email you want. 

In both instances, it’s important to understand because the discount code is generated through a third-party app, the variable expiration date will need to be managed through time delays in Klaviyo. 

If you haven’t already, I would suggest taking a look through our Developer Portal to learn more about our API to implement either of the solutions shared. We also have an extensive network of Klaviyo Partners you can reach out to for more hands on assistance when it comes to custom development help. 

David