There are many scenarios where an activation has a count that does not match up with the total segment count. Having records in a segment does not guarantee that all will have contact points (i.e. emails). Without contact points (individuals with email), we cannot generate Subscriber Keys. This can potentially generate less than expected or empty outputs. If the output is empty, the Marketing Cloud side fails and you will see a failed activation in Data 360..
Note: For S3 activations -- we do not enforce the presence of contact points (email address, Phone #). For Marketing Cloud activations, we do enforce the presence of contact points.
Scenario 1) If you have data coming from multiple sources (i.e. Sales, Loyalty, or Commerce Clouds), adding more Source entries to the Source Priority Order will allow these entries to be included in your activation.
The issue is caused by implicit Marketing Cloud data source selection (not ingesting email addresses from the Marketing Cloud into Data 360). The workaround is choosing the right source for email addresses as outlined below:
Scenario 2) If you've confirmed that all individuals should have emails and your sources are defined appropriately, lower counts in the Marketing Cloud can also be related to incorrect mappings to Contact Point Email and/or Individual.
For example, if you have a data stream mapped to contact point email, you'll want to ensure you've mapped the field Party correctly to your stream. Party is the foreign key that relates contact point email back to individuals. So the same Unique Identifier column from your data stream should be mapped into Individual.IndividualId field and ContactPointEmail.Party fields.
Further information on data mapping and party can be found on our help docs below:
Note: Future enhancements will be made to accurately display counts for the activation targets and provide clear details if zero or lower records are published.
000389678

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.