Multichannel is already something natural in almost all companies when it comes to communicating with their leads or customers. We receive emails, push communications, SMS, etc. It is already little postal correspondence that we receive. In this article we are going to try to understand the contacts in Marketing Cloud and its relationships.
For these communications, there are companies that use different technologies or tools, so they lose that global photo of the user. Considering this “multi-channel”, it is increasingly essential to treat them as an individual and to be able to maintain a fluid (and not repetitive) conversation that provides maximum value. And what is also important, through the media that best suit them or that they prefer.
How do we centralize and manage all this? The solution is Marketing Cloud and within it, Contact Builder.
When you use different channels in Marketing Cloud, it is very important that you know the difference between a subscriber and a contact.
We can say that all subscribers are contacts, but not all contacts are subscribers.
There may be users that are imported (for example, in Email Studio), but do not appear in All Contacts. The reason is that if you haven't sent them any communication yet, they won't appear in All Contacts.
In short, subscribers will appear in All Contacts if some communication has been sent to them.
It's important to note that all the information you sync with the Salesforce Sales or Service Clouds will appear in All Contacts, even if you haven't sent any messages (it would be the opposite of the above).
As a centralizer of your contacts, Contact Builder logically interrelates with each of the Marketing Cloud communication tools: Mobile Connect, Mobile Push, Journey Builder and Email Studio. However, the relationship with Email Studio is somewhat more complex than with the rest. As we saw before, an Email Studio subscriber will appear in All Contacts in Contact Builder, but a contact in Contact Builder does not have to be in Email Studio (if no email has been sent or has been added by a user).
The real power and interest of all this is being able to have all the information of a user and their interactions with Marketing Cloud through their unique ID or Contact Key. If you enter a specific “Contact Record”, you will be able to see all their interactions (if it is an email, if they opened it, if they clicked on it), you will also see their associated addresses, associated mobile, etc.
And more specifically:
Email, mobile number, or device id (for PUSH notifications)
All record information in Marketing Cloud and Salesforce is managed through these identities: Contact Keys, Contact IDs, and Subscriber Keys.
A contact is managed and related to all channels through its Contact Key. This is a unique identifier that you assign and define for each of your contacts. The Contact Key identifies a contact in any of the Marketing Cloud channels.
There are many organizations that make the mistake of uploading email as Contact Key (or worse), but then upload user information for the mobile channel with the mobile number as ID. That contact, even being a single person, will not have the related data and will be considered by Marketing Cloud as 2 users. And there will be, therefore, a duplicity that we must always avoid.
The Contact ID has a one-to-one relationship with the Contact Key. The difference is that the Key is defined by you and the ID is automatically generated by Marketing Cloud.
In Email Studio the contacts are identified by the Subscriber Key, and this becomes the Contact Key in Contact Builder.
Having a Subscriber Key diferent from the email address is useful for:
Once this Subscriber Key is defined, remember to include it in all the data extensions that are sendable and relate this key to the Subscriber Key itself.