Data 360: Rejected Count in Marketing Cloud Engagement Activation has no Information about Skipped Records

Some reasons why you may see duplicates are outlined below:

• If a field is configured as the primary key on the activation data extension in Marketing Cloud Engagement, then each row that is added to the data extension via import must have a unique value in the primary key field. If the activation data set contains multiple rows with the same value in the primary key field this will result in some rows being skipped as duplicates.
• As outlined in Data 360: Common causes of activation counts exceeding segment counts on Unified Individual, the cardinality of relationships in the Data Model can lead to an activation generating multiple records for records that only exist once in the DMO being segmented and activated on. See this example scenario where this would happen.
  • Create a many-to-one relationship from the Individual DMO to another DMO.
  • Ingest some test records and map to the Individual DMO and the related DMO. Ensure that there is one record for each Individual ID on the Individual DMO but multiple records with the same Individual ID on in the related DMO.
  • Create a segment on the Individual DMO and a corresponding activation. Add a field from the related DMO as an additional attribute in the activation.
  • Publish the activation.
  • If no primary key is configured on the data extension in Marketing Cloud, you will observe that multiple records with the same Individual ID get added to the data extension. If a primary key is configured, only 1 record per Individual ID can be added and the other records will be skipped as duplicates, which can lead to the rejected counts with no rejected reason described previously.