Community Topics

The folder possibilities for storing Audiences in a folder structure has become a nice function. It save a lot of time to find your right Audiences when you dont know exactly the name. I would like to expand this functionality to also be able to use for Offers and Journeys. It will makes it easier t...

In the customer profile UI there is currently no possibility to quickly check Offer Rankings or Decisions (for all active Offers). It should be possible in the customer profile UI to check the Ranking of Offers and results of Offer Decisionings.Operational efficiency when performing testing or inves...

In the customer profile UI there is currently no possibility to quickly check Offer eligibilities (for all active Offers). It should be possible in the customer profile UI to check the eligibility of Offers.Operational efficiency when performing testing or investigation tasks required for a customer...

Currently even Offers with a Ranking score of 0 will be sent back as a response. It should be possible to avoid sending back Offers to the customer based on the value of the Ranking formula (e.g. if the value is 0).Some conditions need to be generally applied without having the risk that someone for...

For activation from a customer journey, policies can be applied to respect privacy and consent limitations. Currently policies cannot be applied to Offer Decisioning which means you have to include these limitations into Offer eligibility rules or decision parameters for example. It should be possib...

Currently a fall back-offer is obligatory. Fall-back Offers should be optional so that an Offer Decisionig request can be empty when there is no persoalized Offer to propose.It should remain an option not to propose anything to the customer if there is no personalized Offer to be proposed.

Currently there is only one fall-back Offer per decision, even if in the decision there are multiple Placements involved. It should be possible to indicate a fall-back Offer per Placements.If there is more than 1 Placement involved in a decision but there is only 1 fall-back Offer per decision, it m...

Currently Offer Decisionig Simulations via UI can only be executed for customers flagged as 'test' customers. It should be possible to execute Offer Decisionig Simulations via UI for all customers without having impact on for example capping parameters. It should be posible to execute an Offer Decis...

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 ...