#Teamlist vs. #Teamtag: Which Pardot Team Are You On?

Share this article...

‘Should you use Pardot lists or Pardot tags?’ is the real question being asked here. When creating Engagement Studio rule steps, or segmenting prospects in Pardot generally, you have more than one option.

This often sparks the lists vs. tags question, just like what happened at the most recent London Marketers Group (Pardot). It turned into a little fun as we discussed the differences. Which team do you choose? Are you #teamlist, or #teamtag?


Quick Overview of Pardot Lists

Pardot lists group prospects together. Lists can be used when sending an email, running automation, and more. Lists can be static or dynamic. Static lists are those lists you add or remove prospects manually, or by using an automation rule – but they require some input from a user. Dynamic lists, on the other hand, update automatically based on prospect criteria.

Overview of Tags

Pardot Tags are an underrated feature. Using Tags properly presents a nifty way to stick a label on to any record or asset in Pardot, for quick segmentation, organisation and identification.

The reality is that Tags are often created in a ‘Quick & Dirty’ way to serve a one time purpose – a use, abuse and abandon way with little strategy.

What if you decided that you and your team could commit to a tagging strategy? Could you use tags to segment prospects down yes and no paths as they progressed through an engagement program?

Or could using lists be a better option?

Using Lists Over Tags – Why #teamlist is the Winner

Lists are generally more friendly to work with. Not only can the list name be more descriptive than that of a tag, but the list interface tells you more information like % mailable.

“I like to be utilitarian”, said Safiyyah, Pardot Consultant and PUG co-leader, “you will often need to make a list to send an email, so then you’re adding an unnecessary step to create a list from a tag using an automation rule” – which, as you may know, have a limited number per Pardot account (Growth edition: 50, Plus edition: 100, Advanced: 150, Premium, 150).

There are also reasons why #teamtag lost due to the downsides of using tags:

  • Case-sensitive: tags are case-sensitive meaning that ‘Tradeshow2019’ is considered a different tag to ‘tradeshow2019’ – very easy to overlook! Tags are also prone to spelling errors (thanks for flagging these points, Triana!)
  • Cannot Undelete: the greatest downside for using tags, in my opinion, is when you (or another user) clicks ‘delete’. Tags are gone forever, you cannot simply fetch them out of the recycle bin! At least with lists, you can undelete them.
  • Easy to overlook: it’s easier than you may think to accidentally remove a tag from an engagement program, automation rule etc. I’ve seen it happen before while working with organisations!


After such an interesting conversation at the London Marketers Group (Pardot) meetup, I wanted to share this insight with everyone. Of course, there are benefits to using tags and ways you should look to get more out of them, but for important segmentation use cases (eg. Rule steps in Engagement Studio), the verdict is out – #teamlist won.

Which team do you choose? Are you #teamlist, or #teamtag? Are there any points that we forgot about?

2 thoughts on “#Teamlist vs. #Teamtag: Which Pardot Team Are You On?

  1. I use both. Tag are specially important when you need to organize your assets. Maybe you have a 50 forms or 200 lists and you need look one up fast. The Tag allows you that.

    But also makes sens combine dinamic lists and Tag to automate criteria. For instance, you Tag a prospect when a form is fill out or when visit an specific Page Action or click in a Custom Redirect.

    So, you can segment this prospects in a quick way. I think you can use both. For me are complementary but depend on your strategy.

    1. Thanks for sharing your thoughts Christian! I will add your thoughts into the post, crediting you too. You should have come to our London Pardot user group meet up! It was a great discussion 🙂

Add Comment