AJO WhatsApp webhook, does it persist delivery reports when the original message was sent via Custom Action?
Hi everyone,
I don’t know if you can help me with this question abount Whatsapp Native Webhook:
What we tested:
We submitted a real Meta delivery callback payload (wamid + recipient_id + status read) directly to the AJO native WhatsApp webhook URL.
The endpoint responded HTTP 200 – Webhook data processed successfully, but no event appeared in AJO Email Tracking Experience Event Dataset.
Relevant docummentation (whatsapp-configuration) mention this points:
"A profile must have at least one message sent from Journey Optimizer before incoming messages are captured in this dataset.
"Our interpretation: AJO requires having originated the message natively to register the wamid internally — without that record, it cannot correlate the Meta callback to a profile, so it accepts the payload silently (HTTP 200) but persists nothing.
Questions:
- Is the AJO WhatsApp webhook designed exclusively for messages sent through the native AJO WhatsApp channel?
-
Is
HTTP 200expected even when AJO cannot correlate or persist the event? - Has anyone successfully used it to receive feedback for Custom Action–sent WhatsApp messages?
Best Regards,
