Never miss an update of the Adobe Journey Optimizer Community Lens! Subscribe now to get the latest updates, insights, and highlights delivered straight to your inbox every time a new edition drops.
I get an error in the Journey canvas about missing opt out link in the email body. Se attached image. This is not correct - since there is a opt out link present in a Footer fragment in the same template. The opt out link i coded in the fragment, and are present in the same way with the same ID-s that is needed for the link to work. But for some reason this manually coded link is not recognized as a out out link when AJO checks the code/template. Se picture of the code with the link.
It would be nice if manually placed code also could be recognized when it is actually the same code that AJO is creating. This is an unnecessary error message that cases a lot of confusion.
Yes, I also noticed this because of multiple reasons, specially if you use manual or any third party link for managing consent.
if its a "warning message", you can ignore this since Adobe sometime can't evaluate if your opt-out link works or not if the user re-directed to a landing page of One-Trust or third party consent management.
its an automated alert by evaluating your code. Similar discussions already made in many places, refer the below link as well
Even when your footer fragment contains an opt-out link with the exact HTML/ID structure required, AJO’s journey publishing validator may fail to recognize it, resulting in this error. The validator only recognizes opt-out links that match very specific placement and markup patterns, and this issue is common when you use reusable footers or code snippets instead of dragging the official opt-out/unsubscribe component into the main body of the email template.
Although the preferred way is to use the built-in opt-out block or component in Email Designer, if you must use a fragment, you can try to match the exact generated structure and data attributes of the OOTB component (this needs to be tested).
If blocked from publication, log a support ticket.