Well, we have merely provided these 4 vendors with several fields to pass along to us (name, email, company, title, state, phone) |
Across just those 5 fields, would you even want to have a less granular dedupe key than Email? If your dedupe key were Email + Company, that would lead to more duplicates, not fewer.
Generally the desire for a compound dedupe key (Email + something else), or a single dedupe field other than Email, comes when there's another string field that's unique when Email isn't. For example, if your db had a Member ID field sync'd in from an outside system and (as long it didn't get edited in Marketo) it could be guaranteed to be unique, then you'd want to dedupe on the combo Email + Member ID or just Member ID.
So, by not specifying, is the default only the email? |
Yes.
If there are more than one record with duplicate emails in Marketo, which one does it map to? |
Please read this post for more on that: The Unintended Consequences of Duplicates in Marketo