Skip to main content

Hello everyone,

I'm contacting you to get your opinion on the subject of tags. Currently we create different tags for each of our campaigns. Example: if we have an “End Survey” tag, we have a “Campaign A - End Survey” tag “Campaign B - End Survey” tag etc... 


The advantages are as follows:

  • We can create very precise conditions and send flows when we want.
  • We can keep track of which ambassadors have carried out which campaigns.

The disadvantages are as follows: 

  • We have to recreate tags for each new campaign.
  • We have to modify these same tags in flow templates
  • We have a very large number of tags in our database.


My idea was to create a single specific tag for each campaign (e.g. “Campaign A”) and use generic tags for all tags. However, this approach seems to pose two problems:

If there are two campaigns running at the same time, the tags will interfere with each other.
I'm obliged to delete the person's tags for the next campaign, thus losing the history.
What do you think of my approach? Is it really a hassle to have specific tags all the time? If it's a good approach, how can I overcome the problems I mentioned above?

Thank you in advance for your answers.

@Cm13000 you can use User Fields, and concatenate data on the fields to create a more dynamic system that doesn't overlap and makes it easier to duplicate campaigns.

For example, let's say that you have 2 steps on your campaigns, you can create 2 fields (Step 1 and Step 2), and concatenate the information.

So if a user has the fields set as:

Step 1: Campaign1;Campaign2;Campaign4;

Step 2: Campaign1;Campaign4;

You'd know that this person went through step 1 of campaigns 1, 2 and 4. And through step 2 of campaigns 1 and 4.

Does this make sense?

It's kinda complicated to explain here… But if you need help setting this up let me know.

 


Thank you very much for your reply. It's a great idea!


Reply