Currently context parameters can already be used in Offer eligibility rules but only via the API and not via the UI. It should be possible to also use them via the UI.Full use of the UI potential in daily operations, without having to create ourselves an API interface fur daily operational tasks.

Currently the language parameter in the content definition screen is not of any use. It is not possible to have more than one content per Offer per Placement, even if they are in a different language. So content differentiation on language needs to be done through if statements in the same single JS...

Currently Offer Decisioning context parameters cannot be used to personalize content. It should be possible to use Offer Decisioning context parameters in content personalization.In some cases we want to differentiate content based on context parameters of the Offer Decisioning Request. E.g. languag...

Currently when within an Offer Decisioning call deduplication is required between decision scopes a Round Robin principle is applied between scopes, meaning that every scope in turn gets an Offer assigned, even if the first scope in the decision requires two or more Offers. It should be possible to ...

During the discovery phase of the project, our company has stated that the banners/offers proposed to an actor/customer may vary in case the customer is at a certain stage of a given customer journey (also called digital experience). Our requirements state: - We want to make changes on priority or e...