Pipeline Object Tags: Increased Limits

Trisha Merriam asked if we had covered this one yet, and we had not. Pipeline object tag limits per portal go up: Starter from twenty to thirty, Professional from forty to fifty, Enterprise from eighty to one hundred, still none in Free, and the limit applies across all object types in a portal.

Trisha's question was whether these are different from deal tags. Casey had the answer: they are the evolution of deal tags. Tags started on deals, and now you can tag anything that lives in a pipeline. I think the increase follows the recent change from a per-pipeline limit per object to a portal limit, and I am curious how they decide on forty to fifty and eighty to one hundred.

What I want people to know is that there is a lot behind tags. When you set them up they work very much like scoring and segmentation, using a lot of that functionality, so presenting a Kanban board with tags can get pretty complex. They are available through the API now too. As I was building out a new chunk of my data model with AI last night, it suggested some tags, and I do not see the ones it suggested in the system, so I am checking whether they got built a different way. For the deep version, find the episodes where I talk about it with Joshua Oakes. He is the deal tag guy.

Who should act: admins who were bumping the old limit, and anyone running tags on more than deals. Who can skip it: Free portals, which still have no tags, and teams that have never used a tag.