[Limited Availability]{class="badge informative"}
Create decision policies create-decision
Decision policies are containers for your offers that leverage the experience decisioning engine in order to pick the best content to deliver, depending on the audience.
Decision policies contain all of the selection logic for the decisioning engine to pick the best content. Decision policies are campaign specific. Their goal is to select the best offers for each profile while the campaign authoring allows you to indicate how the selected decision items should be presented, including which item attributes to be included in the message.
Add a decision policy to a code-based campaign add-decision
To present the best dynamic offer and experience to your visitors on your website or mobile app, add a decision policy to a code-based campaign. To do so, follow the steps below.
-
Create a campaign and select the Code-base experience action. Learn more
-
From the code editor, select the Decision policy icon and click Add decision policy.
-
Fill in the details for your decision policy: add a name and select a catalog.
note note NOTE Currently only the default Offers catalog is available. 
-
Select the number of items you want to be returned back. For example, if you select 2, the best 2 eligible offers will be presented for the current surface. Click Next
-
Use the Add strategy button to define the selection strategies for your decision policy. Each strategy consists of an offer collection associated with an eligibility constraint and a ranking method to determine the offers to be shown. Learn more
note note NOTE At least one strategy is required. You cannot add more than 10 strategies. -
From the Add strategy screen, you can also create a strategy. The Create selection strategy button redirects you to the Experience decisioning > Strategy setup menu. Learn more
-
When adding several strategies, they will be evaluated in a specific order. The first strategy that was added to the sequence will be evaluated first, and so on. Learn more
To change the default sequence, you can drag and drop the strategies and/or the groups to reorder them as wanted.
-
Add a fallback. A fallback item will display to user if none of the above selection strategies are qualified.
You can select any item from the list, which displays all the decision items created on the current sandbox. If no selection strategy is qualified, the fallback is displayed to the user no matter the dates and eligibility constraint applied to the selected item.
note note NOTE A fallback is optional. If no fallback is selected and if no strategy is qualified, nothing will be displayed by Journey Optimizer. -
Save your selection and click Create. Now that the decision policy is created, you can use the decision attributes inside your code-based experience content. Learn more
Evaluation order evaluation-order
As described above, a strategy consists of a collection, a ranking method, and eligibility constraints.
You can:
- Set the sequential order you want for the strategies to be evaluated,
- Combine multiple strategies so they are evaluated together and not separately.
Multiple strategies and their grouping determine the priority of the strategies and ranking of eligible offers. The first strategy has the highest priority and the strategies combined within the same group have the same priority.
For example, you have two collections, one in strategy A and one in strategy B. The request is for two decision items to be sent back. Let’s say there are two eligible offers from strategy A and three eligible offers from strategy B.
-
If the two strategy are not combined or in sequential order (1 and 2), the top two eligible offers from the first strategy will be returned in the first row. If there are not two eligible offers for the first strategy, the decision engine will move on to the next strategy in sequence to find as many offers are still needed, and ultimately will return a fallback if needed.
-
If the two collections are evaluated at the same time, as there are two eligible offers from strategy A and three eligible offers from strategy B, the five offers will all be stack ranged together based on the value determined by the respective ranking methods. Two offers are requested, therefore the top two eligible offers from these five offers will be returned.
Now let’s consider an example where you have multiple strategies divided into different groups.
You defined three strategies. Strategy 1 and Strategy 2 are combined together in Group 1 and Strategy 3 is independent (Group 2).
The eligible offers for each strategy and their priority (used in the ranking function evaluation) are as follows:
-
Group 1:
- Strategy 1 - (Offer 1, Offer 2, Offer 3) - Priority 1
- Strategy 2 - (Offer 3, Offer 4, Offer 5) - Priority 1
-
Group 2:
- Strategy 3 - (Offer 5, Offer 6) - Priority 0
The highest priority strategy offers is evaluated first and added to the ranked offers list.
Iteration 1:
Strategy 1 and Strategy 2 offers are evaluated together (Offer 1, Offer 2, Offer 3, Offer 4, Offer 5). Let’s say the result is:
Offer 1 - 10
Offer 2 - 20
Offer 3 - 30 from Strategy 1, 45 from Strategy 2. The highest of both will be considered, so 45 is taken into account.
Offer 4 - 40
Offer 5 - 50
The ranked offers are now as follows: Offer 5, Offer 3, Offer 4, Offer 2, Offer 1.
Iteration 2:
Strategy 3 offers are evaluated (Offer 5, Offer 6). Let’s say the result is:
- Offer 5 - Will not be evaluated since it already exists in the result above.
- Offer 6 - 60
The ranked offers are now as follows: Offer 5 , Offer 3, Offer 4, Offer 2, Offer 1, Offer 6.
Use the decision policy in the code editor use-decision-policy
Once created, the decision policy can be used in the personalization editor. To do so, follow the steps below.
-
Click the Insert policy button. The code corresponding to the decision policy is added.
note note NOTE This sequence will be repeated the number of times you want the decision policy to be returned. For example, if you chose to return back 2 items when creating the decision, the same sequence will be repeated twice. -
Now you can add all the decision attributes you want inside that code. The available attributes are stored in the Offers catalog’s schema. Custom attributes are stored in the
_<imsOrg> folder and standard attributes in the_experiencefolder. Learn more on the Offers catalog’s schema
note note NOTE For decision policy Item tracking, the trackingTokenattribute needs to be added as following for decision policy content:trackingToken: {{item._experience.decisioning.decisionitem.trackingToken}} -
Click each folder to expand it. Place the cursor of your mouse at the desired location and click the + icon next to the attribute you want to add. You can add as many attributes as you want to the code.
-
You can also add any other attribute available in the personalization editor, such as profile attributes.
Reporting in Customer Journey Analytics cja
If you are working with Customer Journey Analytics, you can create custom reporting dashboards for your code-based campaigns leveraging Experience Decisioning.
The main steps are listed below. Detailed information on how to work with Customer Journey Analytics is available in the Customer Journey Analytics documentation.
-
Create and configure a connection in Customer Journey Analytics. This allows you to connect to the dataset you want reports for. Learn how to create a connection
-
Create a data view and associate it to the connection created earlier. In the Components tab, choose the relevant schema fields you want to show up in reporting. For Experience Decisioning, make sure you include the propositioninteract and propositiondisplay fields. Learn how to create and configure data views
-
Combine data components, tables and visualizations in workspace projects to create and share reports for your code-based campaign.Learn how to create workspace projects