Skip to main content
Solved

API: timeframe_filter's "in-the-next" results in [blank] in flow's filters


tsalamazing
Problem Solver I
Forum|alt.badge.img+2

What the title says, basically.

I'm trying to break out of a flow when an order is placed. But the API does not expose this function. Instead, there's the "in-the-next” X (let's say 3) days option, but it's resulting in "placed order 0 times [blank] 3 days”

Best answer by tsalamazing

Dont worry, no need to, anymore

View original
Did this topic or the replies in the thread help you find an answer to your question?

10 replies

Christiannoerbjerg
Expert Problem Solver II
Forum|alt.badge.img+12

Hi ​@tsalamazing 

Thank you for posting in the Community!

Could i get you to elaborate with some images, if possible? I would love to help :-)

Christian Nørbjerg Enger
Partner & CPO
Web: Segmento.dk
LinkedIn: @christianfromsegmento
Voldbjergvej 22b, 8240 Risskov


tsalamazing
Problem Solver I
Forum|alt.badge.img+2
  • Author
  • Problem Solver I
  • 9 replies
  • January 9, 2025
Christiannoerbjerg wrote:

Hi ​@tsalamazing 

Thank you for posting in the Community!

Could i get you to elaborate with some images, if possible? I would love to help :-)

Christian Nørbjerg Enger
Partner & CPO
Web: Segmento.dk
LinkedIn: @christianfromsegmento
Voldbjergvej 22b, 8240 Risskov

 

 

 


MANSIR2094
Problem Solver IV
Forum|alt.badge.img+13
  • Problem Solver IV
  • 174 replies
  • January 10, 2025

Hello ​@tsalamazing 

To break out of a flow when an order is placed, you can use a conditional split or trigger filter to exclude users who have placed an order. If the "in-the-next X days" option isn’t working as expected, try refining the event condition logic to align with your flow’s timing. If implementation feels complex, feel free to reach out, and I can assist further.

 

 


tsalamazing
Problem Solver I
Forum|alt.badge.img+2
  • Author
  • Problem Solver I
  • 9 replies
  • January 10, 2025

I can't exclude users who have generally placed an order because then if you've placed an order 2 years ago, you still dont get in the flow


MANSIR2094
Problem Solver IV
Forum|alt.badge.img+13
  • Problem Solver IV
  • 174 replies
  • January 10, 2025

Hello @tsalamazing,

 

Thank you for pointing that out! I understand the concern about excluding users based on older purchase events. To address this, you can refine the logic further: Use "placed order" with a specific time frame in the conditional split or trigger filter. For example, set the condition to only exclude users who placed an order within the last X days (e.g., 30, 60, or a timeframe that fits your flow).

 

This ensures that users with older purchases (e.g., 2 years ago) can still enter the flow while excluding recent purchasers.

 

If you'd like, I can help you fine-tune the logic or even set this up for you. Let me know how you'd like to proceed!


tsalamazing
Problem Solver I
Forum|alt.badge.img+2
  • Author
  • Problem Solver I
  • 9 replies
  • January 10, 2025

But I don't wanna exclude any of them! Only after the flow is triggered. At which point, I can't know if they ordered on day 1 or day 2 or day whatever.


MANSIR2094
Problem Solver IV
Forum|alt.badge.img+13
  • Problem Solver IV
  • 174 replies
  • January 10, 2025

Thank you for clarifying! If you don’t want to exclude anyone entirely but want to control post-trigger behavior, we can:

 

1. Use a flow filter for subsequent actions: Adjust the timing logic of actions within the flow. For example, add a delay step combined with conditional checks to see if an order was placed during the flow. This ensures users stay in the flow but skip unnecessary steps if they purchase.

 

2. Add conditional checks dynamically: Use event-based checks (like "Placed Order" since flow trigger) tied to each step to personalize further actions. This way, you keep all users in but adapt messages based on their journey.

 

Let me know if you'd like detailed steps or additional customization suggestions!


tsalamazing
Problem Solver I
Forum|alt.badge.img+2
  • Author
  • Problem Solver I
  • 9 replies
  • January 10, 2025

Honest question, who's fault will it be if I report you?


stephen.trumble
Community Manager
Forum|alt.badge.img+60

Hey ​@tsalamazing 

Sorry that you haven’t gotten an answer to this question yet. ​@DavidV or ​@retention, would either of you champs be able to help out? 


tsalamazing
Problem Solver I
Forum|alt.badge.img+2
  • Author
  • Problem Solver I
  • 9 replies
  • Answer
  • January 13, 2025

Dont worry, no need to, anymore