Skip to main content

Hello, 

 

We have partnered with a third party and we will be sending their customers a discount code for the next three years every time the customer resubscribe or subscribes to their annually membership.

 

They will be sending customer data in from a API, such as if they have paid, tier of membership and expiration date and start date. Example profile here https://www.klaviyo.com/profile/01J9RYTNAV6M4S0XVJVRG1JPMH

 

We are playing on using the SDA_EXP_DATE as a flow trigger. I just wanted to know if the below flow will work for the next three years. 

https://www.klaviyo.com/flow/Y4s8JN/edit

 

So if I signed up today my exp date would be 28/10/2025 and if I decided to to resub it would change to 28/10/2026, would I get the discount code email in 2024 and in 2025 if I resub. 

 

Thanks,

George

Hi @george12345245135124 

Thank you for posting your question in the community. I wasn’t able to open the shared links as I don’t have access to your specific account, but I think I can offer some insights. 

If the flow is going to be triggered by a custom metric via the API then you can use each annual resub as the trigger to send the email each year.

In your case, my thought is, you would use the first subscription exp date to enter the user into a date-based flow. The benefit of the data based flow is that you can set it to repeat on any specific cadence, monthly or annually. You could set up a flow filter to either look at the date or maybe another data point such as paid or not paid. Then, in the next year, if their status is still paid, they could get the flow again. 

If you are using the date in a segment and someone is sent the email their first year, they would not receive it again from the same flow. Segment and List-triggered flows only allow a contact to be entered once. 

So you may want to consider a date-based or metric-based flow. If you can share a screenshot of the flow you have set up, I’d be happy to review that and provide more specific feedback, but based on your description I thought this would be helpful context.

Please let me know if you have any questions.

Best,

@In the Inbox 


Hi @In the Inbox

 

Thank you very much for taking a look into this and delivering your insight. 

 

Here is a screenshot of how my flow is currently set up:

 

 


Reply