Decisioning in code-based experience implementations code-based-decisioning-implementations
When using Decisioning in code-based experiences, consider adding the following flags to your client implementation in the cases described below.
➡️ Learn more about configuring the Web SDK for code-based experiences and decisioning in these tutorials.
Testing code-based experiences using decisions code-based-test-decisions
When testing code-based experience with decisioning, the dryRun flag can be used to supress feedback events for both reporting and capping counters.
After publishing your campaign, add the dryRun flag into the XDM event data block in your client implementation:
{
"data": {
"__adobe": {
"ajo": {
"dryRun": true
}
}
}
}
Deduplication of decision items in code-based implementations code-based-decisioning-deduplication
When using decision policies in your code-based experiences, you can apply deduplication to your decisioning requests in your client implementation.
Decisioning requests (through Konductor) accept the deduplication flag, which handles uniqueness of decision items in a single request comprised of multiple decision policies or placements.
Deduplication logic deduplication-logic
For any decisioning request, you can have one or more decision policies/placements based on setup.
-
For a single decision policy and placement in a request, all items in the response are unique (by default). Two decision items cannot be the same in a single request.
-
For multiple decision policies/placements in a request:
-
If
allowDuplicateDecisionItemsis set tofalse: all items in the response are unique (regardless of which message/decision policy/placement the item is for). -
If
allowDuplicateDecisionItemsis set totrue(default): items in the response can be duplicate (if multiple messages/decision policies/placements qualify for the same decision item for that request).
-
Apply deduplication in a request deduplication-in-request
By default, the deduplication flag is set to true.
In a Konductor request, you can pass the deduplication flag if you want unique elements in the response. In that case, set it to false.
{
"data": {
"__adobe": {
"ajo": {
"allowDuplicateDecisionItems": false
}
}
}
}
| code language-none |
|---|
|
Deduplication response deduplication-response
Let’s say you have the same decision policy with header and footer placement in a single request.
-
Decisioning returns two propositions.
-
If
itemId-Xis the single decision item that qualifies for both decision policy and placement combination:-
If
allowDuplicateDecisionItemsistrue(default):itemId-Xis returned back for both propositions in a single response. -
If
allowDuplicateDecisionItemsisfalse:-
itemId-Xis returned back for the first proposition. -
The fallback decision item (also unique) or an empty decision item is passed for the second proposition.
-
-
allowDuplicateDecisionItems = true)| code language-none |
|---|
|
allowDuplicateDecisionItems = false)| code language-none |
|---|
|
Tutorials tutorials
Learn how to fetch, display and track code-based experiences using the Adobe Journey Optimizer extension for Adobe Experience Platform Mobile SDKs in this tutorial.
Learn how to use decisioning in Journey Optimizer to personalize content offers on your website, with a focus on Web SDK configuration, in this tutorial.
Learn how to configure the Web SDK and use decisioning with code-based experiences to personalize offers using real-time weather data and contextual information in this tutorial.