As I wasn't able to find any information on that topic in the documentation, I was wondering if the "Sync Leads" REST API endpoint will honor custom deduplication rules (if set)? So, by default, the "Sync Leads" API endpoint will create or update persons based on the email address (if "lookupField" is not set). Will this default behaviour also change if a custom deduplication logic is setup by Support to e.g. "email" and "custom field" or is there any other way to set more than one "lookupField" (probably some kind of workaround as using more than one lookup field is not possible )?
As an example, let's assume we have three persons in our database with the following information.
|Id||Email Address||Custom Field|
If the custom deduplication is set to "Email Address" and "Custom Field" and I were to use the Sync Leads REST API endpoint with the following body...
would the third person (id = 3) get updated?
This field is a string type field, not an array type, so you can set only one value.
If you want to do some sophisticated deduplication logic, I recommend to use "merge" instead : http://developers.marketo.com/rest-api/endpoint-reference/lead-database-endpoint-reference/#!/Leads/...
Thanks, merging is not an option as those are not the same persons with the custom dedupe logic.
I'm more looking for an answer to the question wether or not the "Sync Leads REST API" will honor a custom dedupe logic or will still only dedupe based on the email address (which wouldn't make that much sense IMO if the deduplication is set to both email address AND another field).