@Nutsa9858 Kindly try replicating it in https://experienceleague.adobe.com/en/apps/journey-optimizer/ajo-personalization?lang=en# and see if you run into the same error.

@HardikJa4  You can use the following expression  SUM -> {%= context.productprice + context.tax + context.deliverycost %} Personalization editor playground https://experienceleague.adobe.com/en/apps/journey-optimizer/ajo-personalization?lang=en#   

can you share the screenshot of personalization editor where name attribute is being accessed ?

Consent policies can be leveraged in your case https://experienceleague.adobe.com/en/docs/journey-optimizer/using/privacy/consent/consent  Note - Consent policies are currently only available for organizations that have purchased the Adobe Healthcare Shield or Privacy and Security Shield add-on offe...

This won't be feasible in the expression editor (in custom actions, conditions etc.,) and will have to be pre processed while brining it into AEP or derived using Data distiller (say, for example)

@dmoorethree Currently, non-HTML content type offer placements are filtered out in email. Kindly log an enhancement for the same

@Silvio6 You can validate it on the lines of the following expression  toString((indexOf(serializeList([ "2026-01-02", "2026-01-05", "2026-01-06", "2026-01-07", "2026-01-08", "2026-01-09", "2026-01-12", "2026-01-13", "2026-01-14", "2026-01-15", "2026-01-16"], "", false),"2026-01-06"))/(length...

can you share the curl ?

@AvaniJain Here is one of the examples of custom Authorization payload and it needs to be adapted based on what you have working in postman. Can you validate with this ? { "type": "customAuthorization", "authorizationType": "Bearer", "endpoint": "<your_auth_endpoint>", "method": "POST", "header...

can you share the payload you are using in custom authentication ?