Allow duplicates between partitions but not in a given partition

[Charlotte_Berth]

Hello,

We have set-up partitions and we have asked the implementation of custom dedup in order to be able to have duplicates between our partitions. However in a given partition we want to be able to deduplicate our leads. Example:

We have a contact john.doe@company.com in partition A:

1. we want to allow to create john.doe@company.com in partition B by list import because it does not exist in that partition yet.
2. we want to prevent to create, by list import, a second lead "john.doe@company.com" in a partition where it already exists.

Concerning Marketo form, our need is the following:

We have a workspace A related to partition A.

1. we want to make sure that when using a form contained in workspace A, the flow applies only on contacts of partition A.
2. when a new contact complete a form contained in worskpace A, then the contact is only created in partition A.

Do you know how we should set it up because currently the custom dedupe implemented works between our partitions but not in a given partition as contacts are duplicated.

Do you have any ideas?

Many thanks

[Jay_Jiang]

What are your custom dedupe settings?

[Charlotte_Berth]

Hi, 

Not sure to understand completly the question as we have asked Marketo to set-up the custom dedup so to be able to create duplicates between partition (so maybe the "email address" only but not sure). That may the piece we are missing as we may have asked more but a bit in doubt on how to do so.

Many thanks

[Katja_Keesom · Accepted solution]

Hi Charlotte,

That sounds like a good idea. Normally email address would be the default single dupe key (except for your CRM sync which is generally based on the CRM Id).

When you define a custom dupe key, there's two important things

• What will be the extra field to dedupe on (in this case most likely partition id)
• For which sources should this be set up. You can set up additional dupe keys for all routes via which a person enters your database separately. So you could keep form fills unique by email address only and add partition id as dupe key for web service api or list uploads.

So it would indeed be a good idea to verify what exactly was set up and whether it is what you intended.