Kom igång med beslutsstrategier create-decision

Supported channels - Decision policies are available for Code-based Experience, SMS, Push notifications, and Email.

Push notifications SDK requirement - Experience Decisioning with push notifications requires a specific version of the Mobile SDK. Innan du implementerar den här funktionen bör du kontrollera versionsinformationen för att identifiera den version som krävs och kontrollera att du har uppgraderat därefter. Du kan även visa alla tillgängliga SDK-versioner för din plattform i det här avsnittet.

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.