Loading

Data 360: How to Check Logs for Activation to Marketing Cloud Personalization

Дата публикации: Nov 14, 2025
Описание

In Customer Data 360 you have the option to activate segments to a Marketing Cloud Personalization activation target. Once you complete the steps in Set Up a Connection to Marketing Cloud Personalization an activation target should automatically be created for each dataset selected in Customer Data 360 Setup. You can view all activation targets in the Activation Targets tab. An activation can be created and Customer Data 360 will transfer data to the Marketing Cloud Personalization activation target one the associated segment is published.

When the publish occurs, as outlined in Import Data from Data 360 Into Personalization, this creates an ETL data feed in Marketing Cloud Personalization, which attempts to import the data exported from Data 360.

Follow the steps outlined below to check the Logs in Marketing Cloud Personalization for information about what records were successfully imported and the reason some records may have been skipped.

Решение
  • Log into Salesforce Marketing Cloud.
  • Select the Personalization app.
  • Select the dataset you are activating to from Data 360. The dataset can be changed by clicking the drop down on the top left. The dataset name will usually be included in the name of the activation target in Data 360.
  • Click Feeds from the Gears section of the left hand menu.
  • Click SalesforceCDPActivationETL.
  • Choose an activation run from the SalesforceCDPActivationETL History table.
  • Click the Review Execution button.
  • Click the Logs hyperlink on the bottom left to see the details of the log.
  • The Log tab in the popup includes an object with details logging and lists the counts of records that were Skipped by the ETL process and the reason for these skips.
    • If the Log tab only contains the Object and no errors are listed then most likely no errors occurred during ETL processing. Check the Summary tab to confirm that the counts look correct.
    • You can expand the Object and then expand stats > transformSkips to see more details of records that were skipped.
  • The Summary tab provides details of records that were successfully modified.
    • If all records were skipped then this tab may not contain any information.


Note: some examples of reasons a record can be skipped are as follows.
 

Row contains profileId, but missing additional identities. No match found.The record had a profileId but no other identities. However, the profileId did not match any existing user.
Row missing identities.The record was missing every identity field including profileId


When records are skipped by the ETL, some example records are listed under Object > stats > transformSkips on the Log tab - see steps listed above. Personalization expects this data to contain a SubscriberKey property, which is what is referred to as the profileId above. It also expects an email address to be sent with the property name EmailAddress. If the EmailAddress property is empty or is not present you may see some of the skip errors listed above. A common reason for the email address not being detected is a Preferred Attribute Name being specified for the Email Address in Data 360 (e.g. 'emailAddress').

Follow these steps to check if a Preferred Attribute Name is specified for the Email Address:

  • Navigate to Activations and open the activation record.
  • Click Edit.
  • Click Next.
  • Under Contact Point Email, check the Preferred Attribute Name for the Email Address attribute. If this has a value other than EmailAddress this can result in skip errors.
Номер статьи базы знаний

000395563

 
Загрузка
Salesforce Help | Article