A couple of months ago, the web channel was compatible with Decision Management, providing support for personalization via decision scopes on web pages. Recently, Decision Management support of offers for the web channel has been replaced with a new approach, enabling personalization through code-based web experiences via decision policies on inbound surfaces.
Would like to understand the reasoning behind this shift. Specifically:
- What were the challenges in leveraging the existing Decision Management capabilities (e.g., offer API, decision scope on webpages) within inbound surfaces?
- What key advantages or requirements drove the introduction of the new decisioning functionality for the web experience channel via code-based experiences?
Looking forward to any insights & thoughts.
@SatheeskannaK @dugganab @DavidKangni
