Hi @kaio61751785,This is a good question! That syntax is used by Target for dynamic data in offers which is why it's getting removed/replaced. I couldn't find any info on how to "escape" the format for a literal print. However, I was able to hack a solution that worked for me you might try.Create a ...

Hi @ambikaTewari_ATCI, The best solution would be to pass the profile data in the initial global mbox request. However, I'm guessing you have some constraints that prevent you from doing that in this case. If that's true you could possibly recall the global mbox in your getOffer (instead of the cust...

Hi @lonestarspock,If firing a custom mbox via a trackEvent "viewed an mbox" is the correct conversion metric setting. Some follow up questions I have to help you get this sorted:Have you confirmed you are entering and seeing activity experiences?Is this activity using Analytics reporting (A4T) or Ta...

As a point of clarification, the targetGlobalSettings of secureOnly: true does not impact the Target set cookies (mbox, etc.) it forces all the requests made from at.js to always be over HTTPS (secure protocol). Noted here in help: https://experienceleague.adobe.com/docs/target/using/implement-targe...