Loading

Data 360: Related Attributes in Activation have No Values

Fecha de publicación: Dec 5, 2025
Descripción

Add Related Attributes to an Activation outlines the steps to create an activation in Data 360 and add attributes from a related data model object (DMO) to the activation data.

When an activation is configured in this way and a segment is published, the population of a segment will be sent to the associated activation target. So for example, if the activation is configured for Salesforce Marketing Cloud, a data extension will be created and record added for members of the segment. For any related DMO there will be a field on the data extension and the related attributes on that DMO will be added in JSON format.

If you publish a segment and the data activated to your target does not have any values for related attributes, check the following details.

Solución

Consider the effects of the Activation Lookback Window

If the related attributes you are activating are from an Engagement category DMO or the selected path to the DMO containing the attributes referenced an Engagement DMO, then only attributes linked to Engagement events within the lookback window of 90-days will be activated. This is documented in Considerations for Selecting Related Attributes:

For engagement data, activation supports a 90-day lookback window. If related attributes are selected for an activation with a rapid segment publish, the lookback window is seven days. Activation considers engagement data within this window, and any records outside of this window aren't considered when selecting your output values.

When creating an Engagement category data stream and mapping it to a DMO, you must select an Event Time time field. It is the value in this field that will be checked to confirm if the record is within the lookback window. If you are seeing related attributes activating successfully for some profiles but not for others this may be the cause.

Note: Another cause may be due to DateTime offsets when using date expressions in the segment.


Confirm that values exists on the related DMO using Data Explorer

View Your Data in Data Explorer outlines how to use the Data Explorer tab to check the data present in Data 360, including in data model objects. Use Data Explorer to confirm that values exist in the related attributes for profiles that were activated. So for example, if you activated a segment on the Individual DMO and the activation was configured to activate related attributes from a Sales Order DMO, make note of some IDs from the activation data and apply a filter on Sales Order DMO in Data Explorer to confirm that values exist for those Individual IDs.

Note: You will need to know what fields are used to link the Individual DMO to the Sales Order DMO to know what fields to filter on in Data Explorer. You can check this by opening the Data Model tab, searching for Individual or Sales Order and checking the Relationships tab to confirm what field on Sales Order relates that DMO to the Individual DMO.


Check the Container Path for the Related Attributes

Considerations for Selecting Related Attributes provide some details on how different paths to data model objects exist based on the configuration of relationships between objects in the Data Model. In some scenarios, multiple paths to the same DMO may exist and can result in missing related attributes if the wrong path is selected.

For example, you could configure the data model to have the following relationships:
 

ObjectFieldCardinalityObjectField
IndividualIndividual Id1:MSales OrderBill To Contact
IndividualIndividual Id1:1AccountParty
Sales OrderBill To Account1:1AccountAccount Id


In this scenario when adding related attributes from the Sales Order DMO to an activation for an Individual segment, you will have the option to choose a container path. You can check what path is configured by following these steps:

  • In Activations, select your activation.
  • Click Edit.
  • Click Continue or Next until you see the Add Attributes button.
  • Click the Path drop down for any related attributes to check the path that is used.

In the above example, if a profile exists on the Individual DMO and a record exists on the Sales Order DMO with that profile's Individual ID in the Bill To Contact field, then the activation should be able to successfully retrieve attributes from the Sales Order DMO. However, if the path Sales Order.Bill To Contact > Account.Party > Individual.Individual ID is selected and no record exists in the Account DMO with the Individual ID in the Party field then no attribute values will be returned from the Sales Order DMO and the Sales Order data will be missing in the activation.
Incase you are have enabled Key Qualifier please ensure that the Data across the key qualifier field matches.

Use Data Explorer to confirm if records exist in any intermediary DMOs in the container path. If you suspect the wrong path was selected when first configuring the activation, test a different path to confirm if the related attributes populate when that path is selected.

Número del artículo de conocimiento

000396114

 
Cargando
Salesforce Help | Article