Adovo

Adobe Experience Cloud

AJO WhatsApp CTA opens the page but leaves no click event

Trace WhatsApp CTA URL tracking from template and channel settings through reports and AEP datasets.

November 8, 2026

A WhatsApp Call to action URL can redirect correctly while the team sees no corresponding click in AEP. That is the symptom in an unresolved Experience League report: Quick Reply interactions appeared as tracking events, but CTA URL clicks did not. Adobe’s WhatsApp authoring documentation says supported template buttons, including CTA URL, are tracked. The mismatch deserves a controlled trace before anyone labels it a platform bug.

Record a single test journey

Use one consented test profile, one approved Meta template, one CTA URL button, and a unique destination URL parameter. Record the campaign or journey ID, message ID, sandbox, send time, click time, and profile identity. In the WhatsApp action, inspect the Actions tracking setting for links. Check that the configured channel and webhook are active. Adobe documents webhook behavior across sandboxes, so record which sandbox owns inbound events and which receives feedback events.

Compare reporting surfaces

Check the campaign or journey report for the click before querying raw datasets. Adobe lists the Reporting - Email Tracking Experience Event Dataset for email interaction logs and WhatsApp context, while the AJO Channel Tracking Event Dataset captures inbound WhatsApp responses. Those are different event families; do not treat an empty response dataset as proof that a CTA click did not occur. Query the relevant interaction record using the test message and time window, accounting for data latency. Keep the raw event or query that proves the absence.

Separate Test Mode from delivery behavior

The thread specifically asks whether tracking is supported in Journey Test Mode. We found no definitive answer in the cited documentation. Run a small approved production-mode test with an internal profile if permissible, and compare with the Test Mode result. If one mode tracks and the other does not, submit the IDs, configuration, report screenshots, and dataset query to Adobe Support; avoid changing live campaign decisions from an unverified test-mode assumption.

Adovo’s view

A working redirect is not a measured response. Conversion teams need the same event definition from message to report to profile. Make one traceable click the acceptance test before using WhatsApp response rates to optimize spend or audiences.

Continue exploring

Adobe Experience Cloud

Adobe Journey OptimizerJourney entry

AJO event appears on a profile but never enters the journey

Separate profile event visibility from eligible streamed journey entry.

Read more

Adobe Experience Cloud

Adobe Journey OptimizerWeb Push

AJO Web Push custom data is absent from the service worker payload

Contract-test Web Push metadata before putting routing or personalization behind it.

Read more

Adobe Experience Cloud

Adobe Journey OptimizerJourney Governance

An AJO daily entry cap does not protect a 14-day wait

Separate AJO entry limits from concurrent enrollment and journey timeout when one profile qualifies for competing journeys.

Read more
Explore Adobe services →