Hey Raymond,
You'll be able to do this with a Partition Sorting program, which runs through the logic and then through a flow step moves leads to different partitions.
As part of your Lifecycle Processing program, which would sort people as they come into your system, you would create smart campaigns through a Master Router smart campaign that, based on smart list membership, chooses a child smart campaign which actually changes lead values and moves leads into the appropriate lead partition.
I know that sounds a bit cryptic and architectural, but here's a video explanation of a Master Router architecture program I did at Marketo Summit 2015: Architecting a Robust and Scalable Marketo Instance (start the video at 24:57). You'd use that Master Router campaign and just set the rules for membership in the smart lists that drive them.
You'd be creating separate lead partitions based on your business logic—I can't tell from this information exactly what they should be, because there are lots of considerations, but those partitions would make up the whole of your database. Here's a guess:
- Both News and Promo interest
- Promo interest
- News interest
- Default partition (unsorted)
Then the Workspaces, which are assigned one or multiple partitions, would be these:
- Global (all lead partitions)
- Promo (Promo interest + Both News and Promo interest)
- News (News interest + Both News and Promo interest)
The smart list for each of these is going to depend on your system proxies for each. Because the Master Router uses cascading logic (if a lead fits into multiple smart lists, the first choice that is a fit is chosen), you'll have to order the choices right, hence why in those bullet points for lead partitions "Both News and Promo interest" is the first possible option.
Marketo doesn't have a big distinction between contacts and leads, so contacts will be assigned to the right partition appropriately in the process.
When you're using lead partitions, you'll always have a greater risk of duplicates. That's a danger of using partitions (or a benefit, depending how you're looking at it)—you're purposefully slicing your database into multiple segments that are intentionally discrete. Just keep an eye on it and set a calendar alert to check duplicate lists for 1 week, 1 month, 2 months, and 3 months after putting these partitions in place. That'll get you to identify problems earlier while you can still identify sources of problems and eliminate them.
Cheers,
Edward Unthank | Founder, Etumos
.png)