Why use this condition?
The Assigned Tags condition checks whether a client has one or more specific tags. This helps control the flow of the automation scenario and use tags to create various mechanics.
How the condition works
The condition checks whether the client has the tags you've selected for verification. It allows you to direct the client through different branches of the scenario depending on the presence or absence of specific tags.
You can check for multiple tags within a single condition.
It’s important to understand two parameters:
Is – the condition will be met only if the client has all the selected tags. For example, if you’re checking for two tags, the condition will trigger only if the client has both of them.
Contains – the condition will be met if the client has at least one of the selected tags. For example, if you’re checking for three tags, the condition will trigger as long as the client has any one of them.
How to set it up
Create the condition in your automation scenario.
In the condition parameters, choose "Assigned tags."
Select the tags you want to check (you can choose multiple tags).
Choose the parameters that fits your task:
"Is" – use this if the client must have all the selected tags.
"Contains" – use this if it’s enough for the client to have at least one of the tags.
Examples of use in automation
Preventing the automation from restarting
Use case: This condition is perfect for preventing the automation from restarting for clients who have already gone through it. For example, you can set up a check at the beginning of the scenario: if the client already has the tag "completed test" or "received article," the scenario will not launch again.Example: Insert the condition at the beginning of the scenario: if the tag “received article” is present, do not send any further messages (don’t add a connection arrow when the condition is met).
If the tag is not present, send the full scenario to the client, and at some point, use the “Add Tags” action to assign a tag that marks the completion and prevents the user from repeating the flow.
Segmenting clients by interests
Use case: This can be used to send different message flows to clients based on the tags they have.Example: Previously, the client went through a scenario where they indicated their age group and received a corresponding tag. Now, by checking tags in a new automation or mailing list, you can deliver personalized content to the client.
Task completion check
Use case: This condition allows you to check whether a client has previously completed a task (such as sharing a post with a tag in Stories) before giving them bonus points or bonus content.Example: Set up a condition in your automation: if the client has the tag "points for reposting", either send nothing or display a message saying the task has already been completed.
If the tag is not present, you can award points, add a tag to record the completion, and inform the client in a message.
You might find it useful: