You really have to sit down with the database manager and stakeholders to properly bucket the groups and decide on how you know certain things about them.
if Account Type=X is the primary method, then why is that not going to work?
What data is in each db?
How is it synced?
Hi Josh, thanks for your comments.
The reason this doesn't work is because there isn't a primary type of contact. We are a group insurance company so we have our B2B business contacts (our clients) and we also have our individual plan members (employees of our clients) and sometimes these contacts can be both types at once.
Our CRM database houses our lead and client information, while our in-house database is where our individual member information is stored. This data has not yet been synced, which is why I'm asking these questions now. Creating Boolean fields has been suggested and is looking like our best option at the moment. Do you have any thoughts on this?
1 of 1 people found this helpful
Yes that's tricky one, since you have crossover you can't use segments or partitions and it sounds like one field, even if it's a multi-select, isn't going to cut it. I'd explore smart campaigns that add members to static lists, master campaign membership that you can search across CRM/MKTO or sadly a group of boolean fields until you have better communication between the systems. How frequently is your in-house database being synced with CRM and/or Marketo?
Both the CRM and in-house database will be updating nightly. And yes, I'm beginning to think Boolean fields might be my best option unfortunately.