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 ?

While it is technically feasible it is not recommended due to shared reputation and governance risks. Any deliverability issues from other platforms using the same subdomain can directly impact communications. Using a dedicated subdomain ensures reputation isolation, controlled warm-up, and long-ter...

Yes, it holds good for non adobe campaign tools as well.

It is not recommended and the usual practice is to procure a newer subdomain and then use the same for ip rampup and eventual sendouts.     https://experienceleague.adobe.com/en/docs/journey-optimizer/using/configuration/delegate-subdomains/delegate-custom-subdomain#:~:text=Access%20the%20Administr...

@AkshithaPo  You can validate with the following curl by selecting the file   curl --location 'https://platform.adobe.io/ajo/config/suppression/uploads' \ --header 'Authorization: Bearer <token>' \ --header 'x-api-key: <x-api-key>' \ --header 'x-gw-ims-org-id: <x-gw-ims-org-id>' \ --header 'x-sandb...