The great value of a multi checkbox property is that a contact can get multiple values at the same time: 1k values vs other properties that can hold 1 value at the time - Contacts into a company like the one I am working for need to be enriched with multiple info from different teams and for different purposes at different time. All these info are necessary to feed the complex # of processes we have put in place in years of automations.
All these bits of info cannot end up in a dedicated property every time, we would not have that amount of properties for that + these info expire within time!
When I say info/tag I mean any information that can be used to characterize the contact and address it to lists, views, reports, WFs, etc. Contacts need to be tagged for different reasons and creating a property for each and every reason is not right/possible.
We have some multi checkbox properties called TAG SO, TAG CX, TAG LG (Sales Operations, Customer Experience, Lead Generation): these teams tags contacts for different reasons.
E.G: take the property we have called Marketing action tag, you have there:
- ppl that participated to an offline event
- some internal technical info: contact for which we changed emails
- contacts then won awards
- contacts for which we performed some internal activities and need to be included/excluded from other frameworks
As you can see, the reasons are multiple and this will help us:
- expand our WF capacity
- increase the # of info simultaneously in a single property
- decrease the # of properties