Adobe Experience Cloud
AJO email click follow-up needs a link-level signal
Separate a specific CTA click from a general email-click reaction before branching an AJO journey.
November 11, 2026
A customer clicking a pricing CTA is making a different choice from one clicking a help link. Yet an AJO community question describes finding only a general “Email clicked” reaction when the intended follow-up depends on one URL. Branching on any click can send the wrong message to an otherwise engaged customer.
Define the signal before building the branch
Write down the exact CTA, its destination, and whether the rule is about the URL, the link instance, or the label. Adobe’s message-tracking guidance says links with the same URL and effective label can reuse a tracking identifier. Give repeated links distinct labels when the distinction matters; enable click tracking in the message.
Test with two recipients who click different links in the same email. Inspect the tracking event or reporting field available in your tenant before declaring that a journey condition can distinguish them. The Reaction activity documentation describes reactions to clicks on a message sent in the same journey, with placement and timeout guardrails. It does not by itself prove that every link attribute is exposed to the condition builder.
Choose a safe path for the follow-up
If a link-level field is available to the journey, branch on a stable identifier and test both the target CTA and another tracked link. If it is not, evaluate an audience or event design that carries the link identity into AEP, and confirm latency and consent handling before using it for time-sensitive messaging. Keep a fallback path for clicks that cannot be classified.
Adovo’s view
An engagement event is useful only at the level of decision it supports. “Clicked” measures activity; “clicked this offer” can justify a different conversation. Make the signal precise before making the journey more elaborate.
