Hi team,
We’re exploring how to track and reconcile message feedbacks (delivery, bounce, etc.) with the original API triggered transactional message send requests in Adobe Journey Optimizer.
According to the feedback webhook documentation, the webhook payload includes a requestId field, which uniquely identifies the transactional send request.
However, when we query the AJO Message Feedback Event Dataset, the field requestId doesn’t seem to appear — even though the rest of the payload closely mirrors the webhook structure.
What’s the recommended way to tie a feedback event in the dataset back to the original send request?
Would really appreciate guidance or examples on how to correlate feedback dataset records with the original transactional requests.
Thanks in advance!
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hi @TapanSaikia
it's requestId from your API triggered campaign not from AJO Message Feedback Event Dataset.
Thanks,
David
Hi @DavidKangni, thanks for responding.
Yes, the requestId is from an API-triggered transactional campaign. Just to confirm — the feedback events for API-triggered campaigns should also flow into the AJO Message Feedback Event Dataset, right?
My use case is to have the requestId included in that dataset along with the other feedback attributes.
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies