Data-Cloud-Consultant Reviews Questions

The most likely cause of this issue is that value suggestion is still processing and takes up to 24 hours to be available. Value suggestion is a feature that enables you to see suggested values for data model object (DMO) fields when creating segment filters. However, this feature needs to be enabled for each DMO field, and it can take up to 24 hours for the suggested values to appear after enabling the feature1. Therefore, if a user is not seeing suggested values from newly-modeled data, it could be that the data has not been processed yet by the value suggestion feature. References:

Use Value Suggestions in Segmentation

 Engagement-based related attributes are attributes that describe the interactions of a person with an email message, such as opens, clicks, unsubscribes, etc. These attributes are stored in the Engagement data model object (DMO) and can be added to an activation to send more personalized communications. However, there are some considerations and limitations when using engagement-based related attributes, such as:

For engagement data, activation supports a 90-day lookback window. This means that only the attributes from the engagement events that occurred within the last 90 days areconsidered for activation. Any records outside of this window are not included in the activation payload. Therefore, the consultant should review the event time of the related engagement events and make sure they are within the lookback window.

The correct path to the related attributes must be selected for the activation. A path is a sequence of DMOs that are connected by relationships in the data model. For example, the path from Individual to Engagement is Individual -> Email -> Engagement. The path determines which related attributes are available for activation and how they are filtered. Therefore, the consultant should review the path selection and make sure it matches the desired related attributes and filters.

The other two options are not relevant for this issue. The activations can reference segments that segment on profile data rather than engagement data, as long as the activation target supports related attributes. The activated profiles do not need to have a Unified Contact Point, which is a unique identifier for a person across different data sources, to activate engagement-based related attributes. References: Add Related Attributes to an Activation, Related Attributes in Data Cloud activation have no values, Explore the Engagement Data Model Object

To personalize the content of the email with five "fun" trip statistics, the consultant should recommend using adata transformto aggregate the statistics and map them to direct attributes on theIndividualobject for inclusion in the activation. Here’s why:

Understanding the Requirement

The rideshare company wants to send personalized emails to customers with aggregated trip statistics (e.g., destination, distance traveled).

The raw data is not aggregated at the source, so it must be processed in Data Cloud.

Why Use a Data Transform?

Aggregating Statistics:

Adata transformcan aggregate the raw trip data (e.g., summing distances, counting destinations) into meaningful statistics for each customer.

This ensures that the data is summarized and ready for personalization.

Mapping to Direct Attributes:

The aggregated statistics can be mapped todirect attributeson theIndividualobject.

These attributes can then be included in the activation and used to personalize the email content.

Other Options Are Less Suitable:

B. Create five calculated insights for the activation and add dimension filters: While calculated insights are useful, creating five separate insights is inefficient compared to a single data transform.

C. Use a data action to send each ride as an event to Marketing Cloud Engagement, then use AMP script to summarize this data in the email: This approach is overly complex and shifts the aggregation burden to Marketing Cloud, which is not ideal.

D. Include related attributes in the activation for the last 365 days: Including raw data without aggregation would result in unprocessed information, making personalization difficult.

Steps to Implement the Solution

Step 1: Create a Data Transform

Use a batch or streaming data transform to aggregate the trip statistics (e.g., total distance, unique destinations) for each customer.

Step 2: Map Aggregated Data to Individual Object

Map the aggregated statistics to direct attributes on theIndividualobject in Data Cloud.

Step 3: Activate the Data

Include the aggregated attributes in the activation for the email campaign.

Step 4: Personalize the Email

Use the activated attributes to personalize the email content with the trip statistics.

Conclusion

Using adata transformto aggregate the statistics and map them to direct attributes on theIndividualobject is the most efficient and effective solution for personalizing the email content.

When disconnecting a data source in Salesforce Data Cloud, the system checks for active dependencies that rely on the data source. Based on Salesforce’s official documentation (Disconnect a Data Source), the error occurs if the data source has data streams or segments associated with it. Here’s the breakdown:

Key Dependencies That Block Disconnection

Data Stream (Option B):

Why It Matters:A data stream is the pipeline that ingests data from the source into Data Cloud. If an active data stream is connected to the data source, disconnecting the source will fail because the stream depends on it for ongoing data ingestion.

Resolution:Delete or pause the data stream first.

Documentation Reference:"Before disconnecting a data source, delete all data streams that are associated with it." (Salesforce Help Article)

Segment (Option C):

Why It Matters:Segments built using data from the source will reference that data source. Disconnecting the source would orphan these segments, so the system blocks the action.

Resolution:Delete or modify segments that depend on the data source.

Documentation Reference:"If there are segments that use data from the data source, you must delete those segments before disconnecting the data source." (Salesforce Help Article)

Why Other Options Are Incorrect

Activation (A):Activations send segments to external systems (e.g., Marketing Cloud) but do not directly depend on the data source itself. The dependency chain is Segment → Activation, not Data Source → Activation.

Activation Target (D):Activation targets (e.g., Marketing Cloud) are destinations and do not tie directly to the data source.

Steps to Disconnect a Data Source

Delete Dependent Segments:Navigate to Data Cloud > Segments and remove any segments built using the data source.

Delete or Pause Data Streams:Go to Data Cloud > Data Streams and delete streams linked to the data source.

Disconnect the Data Source:Once dependencies are resolved, disconnect the source via Data Cloud > Data Sources.