cryptString returns different results when applied in typology rule or directly in an email
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 manually add the smtp headers in an email like so:
List-Unsubscribe-Post: List-Unsubscribe=One-Click
List-Unsubscribe: <https://tv2-mkt-prod1.campaign.adobe.com/tv2/oneClickOptOut.jssp?id=<%=cryptString(recipient.auth0)%>>
However when I implement a typology to do the same on all deliveries, the encrypted string is different, and I am no longer able to decrypt it in the webApp.
Any pointers to why this might happen and possibly how I can solve it?
I am using decryptString(encryptedString) to solve the task in the webApp.