Explain the role and capabilities within Contact Builder.
Contact Builder consists of various tools to manage the data model and data records in Marketing Cloud. It only supports Contacts and Data Extensions and cannot be used with Lists.
The Data Designer tool can be used to manage Data Extensions, Attributes, Attribute Groups, Events, Relationships, and Populations.
Data Extensions can be created, edited, and deleted within Attribute Groups. All elements of Data Extensions can be modified, including properties, data retention, attributes, and relationships.
Data Extension and Contact Attributes can be created, edited, and deleted. If a Data Extension has a relationship to Contact, its attributes become Contact Attributes.
Attribute Groups can be created, edited, and deleted to organize Contact Attribute. An Attribute Group can contain several Data Extensions, including their attributes and relationships.
Events can be created, edited, and deleted to segment Contacts based on behavior. They monitor actions performed by Contacts or changes occurred in Contact records, and trigger marketing automations, such start a journey in Journey Builder.
Relationships between Data Extensions and Contact can be created, edited, and deleted. For each relationship, the cardinality needs to be specified. The cardinality defines how many sources records can be related to how many destination records.
Populations can be created, edited, and deleted to segment large groups of Contacts. They create a one-to-one relationship between Contacts and a Data Extension, formerly called root relationship. It is not recommended to create more than three Populations within a Marketing Cloud account.
The All Contacts tool in Contact Builder can be used to manage Contact data stored in Marketing Cloud across channels.
For each Contact and marketing channel, the tools centralize information about related marketing activities, membership in Lists, and Data Extension attributes.
The Engagement tab shows the last marketing activities related to a Contact for each channel.
The Membership tab displays the opt-in status of a Contact in Lists for each channel.
The Attributes tab summarizes all Data Extension attributes related to a Contact.
Data Sources indicates the location where Contact attributes are stored. Attributes can be stored in system, synchronized, and custom data sources.
System Data Sources are default data structures created by Marketing Cloud. Those Data Sources depend on the Marketing Cloud functionalities in use and cannot be modified.
Synchronized Data Sources represent Marketing Cloud Connect data from related Salesforce orgs. Marketing Cloud Connect can regularly sync data from standard and custom objects in Salesforce to data extensions in Marketing Cloud. Field-Level Encryption in Salesforce is maintained when syncing this data to Marketing Cloud.
Custom Data Sources consist of the Data Extension attributes defined in Contact Builder. Multiple Custom Data Sources can be created and individual attributes defined in Contact Builder can be assigned to them.
The Data Extension tool in Contact Builder can be used to manage Data Extension structures and records. This tool supports more functionalities than the similar Data Extension tool in the Email Studio application.
The Data Extension tool in Contact Builder can be used to create, edit, and delete attributes in Data Extensions.
The Data Extension tool in Contact Builder can be used to create, edit, delete, import, and export data in Data Extensions.
The Imports tool in Contact Builder displays all data import definitions used to import data from external sources into Marketing Cloud. The tool can also be used to create new import definitions, to import data into Data Extensions or Lists. Import definitions can either be started manually or references in Automation Studio workflows.
The Contacts Configuration tool can be used to define how Contact Builder handles new information from imported Contacts or interactions with other applications.
The Channel Address Order defines which address field is prioritized in send activities. For example, if a single Contact record has multiple email address associated in various related Data Extensions, the Channel Address Order defines which email address should be used in email sends.
The Channel Address Order configuration was deprecated as part of the April 2019 release. The Default Email Address setting in Journey Builder allows to specify an email address from the Entry Source or Contact Model to be used for email sends in a journey.
The ContactID Mapping feature can be used to link the unique identifier used by Marketing Cloud for Contacts to data extracted from Marketing Cloud. Any data linked with ContactID Mapping must include the ContactID or SubscriberID generated by Marketing Cloud.
There are no practice questions for this objective.