Hi @Cubes-Asia_Vinbarista
It looks like all is OK with your flow.
To explain, flow filters are evaluated at the trigger and each flow step. You have the flow filter ‘Placed Order zero times since starting this flow’. Everyone who starts checkout will enter the flow as they have NOT placed an order since starting the flow at the time of the checkout-started event. This is why the preview trigger shows your contact (who subsequently placed an order) is eligible to enter the flow.
If you have a time delay at the start of the flow, all checkout-started contacts will be put into the waitlist at the first email. Before that first email send, the flow filter is again evaluated. Any contacts who fail the flow filter (place an order while in the flow) are skipped.
You should be able to see this for your example contact if you check the waitlist at your first email (assuming you have a time delay). If you don’t have a time delay, or that delay has passed for them, you will see them as skipped due ‘fails flow filter’.
The other possibility if you’re still having issues is that the contact has entered the flow, placed an order and then entered the flow again (2nd checkout-started event). On that 2nd checkout they will receive the flow emails even though they purchased on the first checkout. You can avoid this by adding an additional flow filter of ‘Checkout started zero times in the last X hours, days, or weeks’. That stops contacts getting too many abandoned checkout emails within a short timeframe.
Let me know if that helps.
Andy
Hi @bluesnapper,
I had implemented something similar.
In our case, users can subscribe to one of our 4 plans. We found that a minority of users had marked us a spam for sending a confirmation for every time they changed their plan eg. they’ve changed their plan 4x within 5 minutes.
I had implemented “SubscriptionStarted” zero times since starting this flow filter at the email level of the flow.
I then found that users were getting skipped because of this and I can’t explain why this would be the case. These users had only triggered the “SubscriptionStarted” one time to enter the flow.
Hoping you can help!
Kiki