I have an automation which sends a discount code to the customer after 90 days of inactivity since the last order. This works fine.
My problem is that the same code is sent again and again to the same customer after another 90 days period without an order. How can I restrict a flow/automation so that it only sends the discount code to the customer once? A pointer in the right direction would be very much appreciated.
What if you tagged the customer after that email gets sent, and then make a condition for sending the email, only if customer does not have that tag?
That sounds like a great idea @JoesIdeas . I actually already tried to add a tag to the customer:
But I don’t seem to be able to add a condition to check for these tags?
Why can’t you add a condition?
@paul_n these are the conditions I can choose of:
Maybe I am searching in the wrong place? Is there a difference in the variables available in Marketing automations vs. the Flow app?
Those aren’t conditions but fields.
An order has a customer which has those tags. So you need to check order / customer / tags
Aaaah, I wasn’t aware that I need to access the customer attributes via the order object. Makes total sense. Thanks for your help, @paul_n
I would love to know how this got resolved. I am having the same problem. But I don’t understand the solution. Did this actually get resolved? If so, how?
I think you need to say which problem you are having, not just “same problem”, as I’m not sure where you are stuck
Paul, it is literally the same exact problem as described by the op.
"
I have an automation which sends a discount code to the customer after 90 days of inactivity since the last order. This works fine.
My problem is that the same code is sent again and again to the same customer after another 90 days period without an order. How can I restrict a flow/automation so that it only sends the discount code to the customer once? A pointer in the right direction would be very much appreciated."
You are using a double-negative, which is pretty much never the correct approach, and also very confusing to understand. You want to use “None of order / customer / tags IS EQUAL TO retarget90”
Do you put in your own description into that task?
There are no customer tags.
When you run “None” on a list that is empty, you get true, because none of the items could match.
This is useful a way to check if a tag doesn’t exit. The problem with “is not equal to” is that if there are 2 tags (“tag1”, “tag2”) it will always be true, which then makes the other “None” is always false.
No, its the automatic description
In your workflow image above it says “does not equal”, so I think this image is from after you changed it
