Get started with decision policies create-decision
Decision policies are containers for your offers that leverage the Decisioning engine to dynamically return the best content to deliver for each audience member. Their goal is to select the best offers for each profile, while the campaign/journey authoring allows you to indicate how the selected decision items should be presented, including which item attributes to be included in the message.
➡️ Discover this feature in video
Guardrails & limitations
-
Supported channels - Decision policies are available to all customers for Code-based Experience, SMS, and Push notifications. Decisioning for the Email channel is available in Limited Availability only.
-
Push notifications SDK requirement - Experience Decisioning with push notifications requires a specific version of the Mobile SDK. Before implementing this feature, check the release notes to identify the required version and ensure you have upgraded accordingly. You can also view all available SDK versions for your platform in this section.
-
Email mirror pages - For now, decision items do not render in email mirror pages.
-
Tracking & links type - To track links generated by decisioning, define them in the schema as “Decisioning Assets”. Attribute-based links are not trackable.
-
Decision policy nesting in emails - You cannot nest multiple decision policies within a parent email component that already has an associated decision policy.
-
Duplicated journeys/campaigns with decisioning – If you duplicate a journey or campaign that includes a decision policy, the duplicated version references the original email or code-based experience, causing errors. Always reconfigure the decision policy after duplication.
-
Consent policies – Updates to consent policies take up to 48 hours to take effect. If a decision policy references an attribute tied to a recently updated consent policy, the changes will not be applied immediately.
Similarly, if new profile attributes that are subject to a consent policy are added to a decision policy, they will be usable, but the consent policy associated with them will not be enforced until the delay has passed.
Consent policies are only available to organizations with the Adobe Healthcare Shield or Privacy and Security Shield add-on.
-
AI Ranking - For now, AI ranking is not supported for the Email channel in journeys with decisioning.
-
Content templates - Any decision policy configured within your content will not be saved in the template. If you apply the template to another action, you need to re-configure the policy.
Key steps key
The main steps to leverage decision policies in messages are as follows:
-
Create a decision policy
Add a decision policy in your message and configure the number of items to return, the selection strategy and fallback options.
-
Use the decision policy in your content
Personalize your content with the decision policy output by inserting the attributes from the decision items you want to display in the message
How-to videos video
Learn how to use Decisioning to personalize emails for your audience.
Learn how to use Decisioning to personalize push notifications for your audience.
Learn how to use Decisioning to personalize SMS messages for your audience.