Hi community! We are aiming at configuring a simple pressure rule for marketing emails. I want to use the build in functionality for this, however, it seems that it is a requirement that you specify a contact date on the delivery itself. That kind of does not comply with our way of working. We alway...

Hi @SHausmann!  I Know this question comes a bit late, but hopefully you will still be able to answer: Can you put some words into how the new Campaign Web UI is different from AJO? I am especially thinking about, what are the pros/cons of using AJO vs. Campaign Web UI if you are implementing AEP al...

Hi @_Pascal1976_1!  Sure thing: List-Unsubscribe: <https://domain.com/oneClickOptOut.jssp?id=@7JBrzEYGpnDQTlgR/wJarr39JJASszYx96q1rsins6v219OK4XNHGCRnu3A8svZT>, < mailto:tv2@domain.com?subject=unsubscribeMESSAGEID> List-Unsubscribe-Post: List-Unsubscribe=One-Click 

HI Community! We have been working on a list-unsubscribe hybrid solution supporting both one-click as well as mailto: options.  While testing this however, I am experiencing that the unsubscribe link is not consistently appearing in the emails, but only sometimes. I am really puzzled about why this ...

It seems that it was in the end a simple mistake. The rule has to be applied in the phase: "At the start of targeting" which solved the issue. So the phase perspective was correct!  Thanks  

Hi @DavidKangni Thanks for the response! That makes total sense! Right now I am struggling to disable the use of salt. I am currently doing this in the typology rule, but it keeps giving different results each time it is run for the same input:  // Define the unsubscribe URL var headerUnsubUrl ="htt...

Hi @Amine_Abedour  Thank you very much for the reply! The rule is applied at personalization phase.  For reference, this is the code that is implemented for the rule: // Define the unsubscribe URL var headerUnsubUrl ="https://tv2-mkt-prod1.campaign.adobe.com/tv2/oneClickOptOut.jssp?id=<%= cryptStri...

Hi community! I am attempting to implement list-unsubscribe and list-unsubscribe POST in all our email smtp headers. The approach is that I have a webApp that accepts a POST call with an encrypted userId that I then decrypt in order to decline permission in our backend system. This all works when I ...

Thanks!

Thanks for the suggestion, this seems to solve the challenge at hand!