Tags are a feature of FunnelFlux funnels that let you label a visitor and then take actions on them later, using conditions, based on the presence or lack of a tag.
One simple implementation of this is tagging a user as "Has Visited Funnel Before" and using this tag to redirect them later.
I.e. their first experience is:
loads funnel > tag checked > none > gets tagged > goes to destination A
Their second experience is:
loads funnel > tag checked > tag exists > goes to destination B.
This allows for very simple routing logics such as preventing users from seeing the same landing pages twice, redirecting people who have via remarketing to different page styles and so on.
As a result, tags will work between funnels and across devices when using email, provided you pass in the flux_visitor parameter.
This makes them very effective for routing in long funnel sequences and when email is involved.
How to set up a basic tag and redirection condition
First, let's define the logic we want to achieve:
I want to send users to a funnel
When they enter, I want to check if they have visited before
If so, I want to send them to lander B.
If it is their first visit I want to send them to lander A.
You can do a lot more with tags but for now let's keep it simple.
Here is my basic funnel map:
Here we first check for the existence of the tag. If present we go down the yes path to lander B. If not we tag and head to lander A. Both then go to offer A.
The first thing I do when creating this funnel is create the tag, as it needs to exist before the condition can check for it.
To do this, right click > advanced > add visitor tag(s)
Here you can select an existing tag or just write a new name and click the add tag option in the small dropdown.
In my condition I then check for the existence of a tag I made:
Then its a simple matter of adding landers/offers and connecting the dots!
Note that you can use the same approach in a separate funnel to redirect visitors who were tagged in a completely different funnel, provided visitors ID and their cookies are intact.
Here are a few scenarios where this may be useful:
You send users to funnel A from Facebook ads and tag them. At the same time you have a similar campaign running on Facebook that sends them to funnel B. Here you check for the tag "has visited funnel A" and if present, you send them down a specific path tailored to people who have already visited your other campaign's landing page
You send users to funnel A where you add them to an email list, and you also log their FunnelFlux visitor ID in the email system. You later follow up with an email going to funnel B, you pass flux_visitor in the link, and if the user clicks through on a pre-sale lander you tag them. You later follow up with funnel C, again pass visitor ID in the link, and use the tag for "engaged with presale lander" to send them to different lander variations, thus allowing you to personalise the sales flow, which is especially useful if the email system does not have the dynamic tracking/segmentation to allow this at the email level.
You want to bounce people who visit your tracking link a lot, e.g. people trying to spy/copy or bots. You tag visitors on first entrance with "has visited lander". When they visit again you send them down a different route and tag with "repeat visitor". You then add a condition that checks for repeat visitor at the start of the funnel and if exists (third visit), you bounce to some backup/dud page to prevent obsessive viewing of your landing pages.
Hopefully you can now see the power of tags!
Use these at any part of your funnel where you want to label users. Keep in mind that tags are global, so try not to be too excessive as you will end up with a lot of tags in your system.