Clarification on Feedback Data Storage and Webhook Configuration in AJO | Community
Skip to main content
N
Nikhil70326
Level 2
April 27, 2026
Question

Clarification on Feedback Data Storage and Webhook Configuration in AJO

  • April 27, 2026
  • 2 replies
  • 31 views

Hi Team,

In AJO, I have created an API-triggered campaign for OTP delivery, which is used for application login. While setting up the campaign, I enabled the webhook option to capture the customer status.

I have a couple of questions:

  1. Where is the feedback data stored in AJO? Specifically, which dataset contains the email/SMS tracking or feedback events?

  2. I have configured the feedback webhook as well. For this, do we need to create and host the webhook URL externally, or is there a way to generate it within Adobe?

Could you please help clarify these points?

Regards,
Nikhil

    2 replies

    I
    IamCGK
    Level 2
    April 27, 2026

    Hey ​@Nikhil70326 

    1. This is the dataset you’re looking for: Message Feedback Event Dataset
      This dataset contains Message delivery logs. Information on all message delivery from Journey Optimizer for reporting and audience creation purposes. Feedback from Email ISPs on bounces is also recorded in this dataset.
    2. Yes, we need to have an external webhook url with authentication if required. AJO will then send the payload to the endpoint you’ve configured (provided that you’ve enabled webhooks in campaigns)

    Hope this helps!

     

    Regards,

    Ganesh Kumar

    SatheeskannaK
    Community Advisor
    SatheeskannaKCommunity Advisor
    Community Advisor
    April 27, 2026

    ​@Nikhil70326 To add more details,

    1. Where is the feedback data stored in AJO? Specifically, which dataset contains the email/SMS tracking or feedback events?

    AJO automatically populates system-generated datasets in AEP store tracking and feedback 

    events. The primary datasets relevant to message delivery and user interaction are:

    Dataset Name

    Purpose

    Channels Covered

    Key Details

    Message Feedback Event Dataset

    Stores message delivery logs for reporting and audience creation. It includes feedback from Email ISPs (e.g., bounces).

    Email, SMS, etc. (All channels)

    Can be queried directly in AEP Query Service using the table name: ajo_message_feedback_event_dataset. Uses the AJO Message Feedback Event Schema.

    Email Tracking Experience Event Dataset

    Stores user interaction logs for the Email channel.

    Email Only

    Captures user actions like opens and clicks for reporting and audience creation.

     

    https://experienceleague.adobe.com/en/docs/journey-optimizer/using/data-management/datasets/export-datasets

    Note on High Throughput Campaigns:

    If the High Throughput transactional messaging add-on is enabled, profile creation at execution is not available because this mode bypasses the reliance on Adobe profiles. Consequently, the system does not verify profile existence for these campaigns.

    1. I have configured the feedback webhook as well. For this, do we need to create and host the webhook URL externally, or is there a way to generate it within Adobe?

    For API-triggered campaign feedback webhooks, the option exists to provide an externally owned or configured AEP HTTP API streaming ingestion endpoint. It is recommended to test the AEP HTTP API streaming inlet as a viable solution.

    Configuration Details:

    • Endpoint: You supply your own hosted URL in the "Webhook URL" field.
    • Action: AJO will send (POST) feedback events to this external endpoint immediately after message execution.
    • Hosting Requirement: You can setup endpoint using services like AEP HTTP API Streaming Inlet, Azure Functions, AWS Lambda, or any other controlled HTTPS server.
    • Security: You have the option to configure authentication (None or JWT) and custom headers.

    https://experienceleague.adobe.com/en/docs/experience-platform/sources/ui-tutorials/create/streaming/http

    Thanks, Sathees
    Terms & ConditionsAccessibility statement

    Loading footer...