When targeting an audience generated using composition workflows, custom (CSV file) audience, or Federated Audience Composition, you can leverage enrichment attributes from these audiences to build your journey and personalize your messages.
Audiences created via CSV file custom upload before October 1, 2024, are not eligible for personalization. To use attributes from these audiences and take full advantage of this feature, please re-create and re-upload any external CSV audience imported prior to this date.
Consent policies do not support enrichment attributes. Therefore, any consent policy rules should be based only on attributes found in the profile.
Here are the actions you can perform using audiences’ enrichment attributes:
Create multiple path in a journey based on rules that leverage the targeted audience’s enrichement attributes. To do this, target the audience using a Read audience activity then create rules in a Condition activity based on the audience’s enrichment attributes.
Personalize your messages in journeys or campaigns by adding enrichment attributes from the targeted audience in the personalization editor. Learn how to work with the personalization editor
To use enrichment attributes from audiences created using composition workflows, ensure that they are added to a Field Group within the “ExperiencePlatform” Data Source.
Detailed information on data sources is available in these sections:
Enrichment attributes are additional attributes that are contextual and specific to an audience. They are not associated with the profile, and are typically used for personalization purposes.
Enrichment attributes are linked to an audience via an Enrich activity in audience composition or through the custom upload process.
Enrichment attributes from audience composition can be leveraged in the following areas. Learn how to use audiences enrichment attributes
To use enrichment attributes from audiences created using composition workflows, ensure they are added to a Field Group within the “ExperiencePlatform” Data Source. Information on how to add enrichment attributes to a Field Group is available in this section
Currently no. Even after wait or event nodes, enrichment attribute values remain the same as they were when the journey started.