How does identity resolution select attributes for unified individuals when there Is conflicting information in the data model?
A customer has outlined requirements to trigger a journey for an abandoned browse behavior. Based on the requirements, the consultant determines they will use streaming insights to trigger a data action to Journey Builder every hour.
How should the consultant configure the solution to ensure the data action is triggered at the cadence required?
A consultant is helping a beauty company ingest its profile data into Data Cloud. The company's source data includes several fields, such as eye color, skin type, and hair color, that are not fields in the standard Individual data model object (DMO).
What should the consultant recommend to map this data to be used for both segmentation and identity resolution?
A customer has a calculated insight about lifetime value.
What does the consultant need to be aware of if the calculated insight.
needs to be modified?
Existing dimensions cannot be removed. If a dimension is removed from the SQL expression, the calculated insight will fail to run and display an error message. This is because the dimension is used to create the primary key for the calculated insight object, and removing it will cause a conflict with the existing data. Therefore, the correct answer is B.
New dimensions can be added. If a dimension is added to the SQL expression, the calculated insight will run and create a new field for the dimension in the calculated insight object. However, the consultant should be careful not to add too many dimensions, as this can affect the performance and usability of the calculated insight.
Existing measures can be removed. If a measure is removed from the SQL expression, the calculated insight will run and delete the field for the measure from the calculated insight object. However, the consultant should be aware that removing a measure can affect the existing segments or activations that use the calculated insight.
A user has built a segment in Data Cloud and is in the process of creating an activation. When selecting related attributes, they cannot find a specific set of attributes they know to be related to the
individual.
Which statement explains why these attributes are not available?
The correct answer is C, the desired attributes reside on different related paths. When creating an activation in Data Cloud, you can select related attributes from data model objects that are linked to the segment entity. However, not all related attributes are available for every activation. The availability of related attributes depends on the container path, which is the sequence of data model objects that connects the segment entity to the related entity. For example, if you segment on the Unified Individual entity, you can select related attributes from the Order Product entity, but only if the container path is Unified Individual > Order > Order Product. If the container path is Unified Individual > Order Line Item > Order Product, then the related attributes from Order Product are not available for activation. This is because Data Cloud only supports one-to-many relationships for related attributes, and Order Line Item is a many-to-many junction object between Order and Order Product. Therefore, you need to ensure that the desired attributes reside on the same related path as the segment entity, and that the path does not include any many-to-many junction objects. The other options are incorrect because they do not explain why the related attributes are not available. The segment entity can be any data model object, not just profile data. The attributes are not restricted by being used in another activation. Activations can include one-to-many attributes, not just one-to-one attributes.Reference:
Related Attributes in Activation
Considerations for Selecting Related Attributes
Salesforce Launches: Data Cloud Consultant Certification
Create a Segment in Data Cloud
Alexa
1 months ago