Luxury Retailers created a segment targeting high value customers that it activates through Marketing Cloud for email communication. The company notices that the activated count is smaller than the segment count.
What is a reason for this?
The reason for the activated count being smaller than the segment count is A. Data Cloud enforces the presence of Contact Point for Marketing Cloud activations. If the individual does not have a related Contact Point, it will not be activated. A Contact Point is a data model object that represents a channel or method of communication with an individual, such as email, phone, or social media. For Marketing Cloud activations, Data Cloud requires that the individual has a related Contact Point of type Email, which contains a valid email address. If the individual does not have such a Contact Point, or if the Contact Point is missing or invalid, the individual will not be activated and will not receive the email communication. Therefore, the activated count may be lower than the segment count, depending on how many individuals in the segment have a valid email Contact Point.
A customer has a custom Customer Email c object related to the standard Contact object in Salesforce CRM. This custom object
stores the email address a Contact that they want to use for activation.
To which data entity is mapped?
The Contact Point_Email object is the data entity that represents an email address associated with an individual in Data Cloud. It is part of the Customer 360 Data Model, which is a standardized data model that defines common entities and relationships for customer data. The Contact Point_Email object can be mapped to any custom or standard object that stores email addresses in Salesforce CRM, such as the custom Customer Email__c object. The other options are not the correct data entities to map to because:
A . The Contact object is the data entity that represents a person who is associated with an account that is a customer, partner, or competitor in Salesforce CRM. It is not the data entity that represents an email address in Data Cloud.
C . The custom Customer Email__c object is not a data entity in Data Cloud, but a custom object in Salesforce CRM. It can be mapped to a data entity in Data Cloud, such as the Contact Point_Email object, but it is not a data entity itself.
D . The Individual object is the data entity that represents a unique person in Data Cloud. It is the core entity for managing consent and privacy preferences, and it can be related to one or more contact points, such as email addresses, phone numbers, or social media handles. It is not the data entity that represents an email address in Data Cloud.
A consultant is connecting sales order data to Data Cloud and considers whether to use the Profile, Engagement, or Other categories to map the DLO. The consultant chooses to map the DLO called Order-Headers to the Sales Order DMO using the Engagement category.
What is the impact of this action on future mappings?
Data Lake Objects (DLOs) and Data Model Objects (DMOs): In Salesforce Data Cloud, DLOs are mapped to DMOs to organize and structure data. Categories like Profile, Engagement, and Other define how these mappings are used.
Engagement Category: Mapping a DLO to the Engagement category indicates that the data is related to customer interactions and activities.
Impact on Future Mappings:
Engagement Category Restriction: When a DLO like Order-Headers is mapped to the Sales Order DMO under the Engagement category, future mappings of the Sales Order DMO are restricted to Engagement category DLOs.
Category Assignment: The Sales Order DMO is assigned to the Engagement category, meaning only DLOs categorized as Engagement can be mapped to it in the future.
Benefits:
Consistency: Ensures consistent data categorization and usage, aligning data with its intended purpose.
Accuracy: Helps in maintaining the integrity of data mapping and ensures that engagement-related data is accurately captured and utilized.
A customer has a requirement to receive a notification whenever an activation fails for a
particular segment.
Which feature should the consultant use to solution for this use case?
The feature that the consultant should use to solution for this use case is C. Activation alert. Activation alerts are notifications that are sent to users when an activation fails or succeeds for a segment. Activation alerts can be configured in the Activation Settings page, where the consultant can specify the recipients, the frequency, and the conditions for sending the alerts. Activation alerts can help the customer to monitor the status of their activations and troubleshoot any issues that may arise.
A customer has a requirement to be able to view the last time each segment was published within their Data Cloud org.
Which two features should the consultant recommend to best address this requirement?
Choose 2 answers
: A customer who wants to view the last time each segment was published within their Data Cloud org can use the dashboard and report features to achieve this requirement. A dashboard is a visual representation of data that can show key metrics, trends, and comparisons. A report is a tabular or matrix view of data that can show details, summaries, and calculations. Both dashboard and report features allow the user to create, customize, and share data views based on their needs and preferences. To view the last time each segment was published, the user can create a dashboard or a report that shows the segment name, the publish date, and the publish status fields from the segment object. The user can also filter, sort, group, or chart the data by these fields to get more insights and analysis. The user can also schedule, refresh, or export the dashboard or report data as needed.
