Salesforce Certified Marketing Cloud Engagement Administrator free question 2 / 10 · Domain 2: Subscriber Data Management
A company keeps separate member records for its loyalty program and its mobile app. It loaded the same person into Engagement under two Contact Keys, a loyalty number and an app ID, and both records carry the same email address. Which statement matches the Contact Builder article on how contacts are counted?
- The person isn't counted as a contact until an email is sent to one of the records
- The record that arrives later overwrites the earlier one, so the count stays at one contact
- Because the email address is the same, Engagement merges the records and counts one contact
- Because the key values differ, the person is counted as two contacts rather than one
Show the answer and explanation
Answer: D
Why this is correct
The article says Engagement groups contacts from every source by their ContactKey value, and that it automatically deduplicates multiple instances of a contact in a population based on the Contact Key value. Its own example is two records with different Contact Key values and the same email address, which count as two unique contacts. The same person with two Contact Keys is therefore two contacts.
Why the other options are wrong
"Because the email address is the same, Engagement merges the records and counts one contact" … The article bases deduplication on the Contact Key value. Its example shows that two records with different Contact Key values and the same email address count as two unique contacts.
"The record that arrives later overwrites the earlier one, so the count stays at one contact" … Records with different Contact Keys are separate contacts, so nothing is overwritten. The article counts only multiple records that share the same Contact Key value once.
"The person isn't counted as a contact until an email is sent to one of the records" … The article says contacts are created through file imports, SOAP and REST API calls, and adding them in the application. Whether a message has been sent doesn't decide whether a record is counted.
Key point
Records without a Contact Key value are counted by the channel address used to send, such as the email address, mobile number, or MobilePush device ID. A lead that becomes a contact in a synchronized data source uses a different ContactKey, so it counts as a separate contact and its tracking and attributes aren't combined.