Working with a duplicate rule with Workspaces and Partitions

John_M
Marketo Employee
Marketo Employee

You may be using Workspaces and Lead Partitions in Marketo, but here's a twist. If you are separating both Marketo Assets with Workspaces and Marketo Leads using Lead Partitions, you may also have a deduplicate rule in place (which we'll deal with in a separate blog) to allow fully separate leads with the same email address to exist in the different partitions. You might, for example have a line of business that targets individuals, and one that targets enterprises, and you want people to be able to exist in both.

In this case, you can have support alter the custom duplicate rule to be Email Address + Lead Partition so you can target the partitions with the API and with list uploads, but the question may come up about whether you need to apply this duplicate rule to form submissions.. after all, its not as if you want to have the partition ID in every form as a hidden field right?

Here's the scenario:

If you have a lead in Partition A with a particular email address, and then that same lead fills out Form B, which only exists in Workspace B, which only has access to Partition B, what happens is curious. Even though the form is in another partition, the lead in Partition A will be updated, which is no good. If however you simply apply the custom dedupe rule to forms, marketo knows enough to also submit the partition ID, and a duplicate lead is added to Partition B.

So, in short, in this situation you don't need to supply the partition ID in every form, but you do need to set the custom deduplicate rule to apply to forms.

7355
13
13 Comments
Anonymous
Not applicable

No need to be sorry! Thanks so much for the response, John Mattos (W)​! I spoke with a member of the support team (Matthew Smith) and another forum member (Hussam AlMukhtar) and they had helped clarify outstanding questions I had with respect to dupes and dupe rules. (Thanks again, both!)

Yes, I am really trying to advocate against any rules that will create additional dupes in our instance. Because we're integrated with Salesforce there are already some dupes in our instance based on how the dupe rules work with a Salesforce integration, but I'd prefer to move towards a 1:1 system with respect to e-mail addresses and leads. (That is, encourage users to provide unique addresses, so that we can provide them with tailored services and also collect more useful information related to their interactions with our content, better manage event registrations, and so on.)

John_M
Marketo Employee

That would be my recommended approach. You also have the ability to create a custom sync filter, meaning that you could create a field on the Lead and Contact with the same API name like "Sync_to_Mkto__c", and support or consulting could configure the sync so that we only sync down those entities where sync to marketo = true.

Anonymous
Not applicable

Thanks again, John Mattos (W)! All good input/perspectives. Really appreciate all the help!