joychan_0-1654207746244.png

Duplicates with Partitions and Workspaces via REST API

joychan
Marketo Employee
Marketo Employee

Most of the time we encourage clients to keep duplicates out of Marketo as it can impact reporting and become difficult to work with. However, there are instances when clients will require intentional/purposeful duplicates as part of their sales process.

 

If you have intentional duplicates with partitions and workspaces – it is required having the secondary dedupe field as leadPartitionID.

Note: Marketo consulting services or support must get involved and edit the dedupe fields in the instance to add Lead Partition ID as a secondary dedupe field

joychan_0-1654207746244.png

Below is an example setup of 3 Partitions: Default, Partition A, Partition B, Broker

joychan_1-1654207755535.png

With the Get Lead Partitions Endpoint, you will retrieve the lead ids:

joychan_2-1654207764076.png

 

 

Let’s first create a new record in Partition A with a simple request with the Sync Lead endpoint:

 

joychan_3-1654207764082.png

 

 

Now let’s trying creating a duplicate record in Partition B:

joychan_4-1654207764086.png

 

 

Oh No! What happened? The previous record was updated even though we specified “partitionName” in the request to be Partition B. If we view the record in the Marketo UI, nothing was updated. Let’s try to update the record again with another field in the request:

joychan_5-1654207764091.png

 

 

joychan_6-1654207764093.png

 

As you can see the record still remains in Partition A, but updates the other fields. If you set the action = createOnly, it still won’t create a new record in Partition B.

 

 

 

In order to create a duplicate record in Partition B, you must specify the lookupField to be leadPartitionID

 

joychan_7-1654207764097.png

 

 

Now you can update duplicate records using lookupField = leadPartitionId

 

 

 

joychan_8-1654207764101.png

 

 

 

 

186
0