Can AJO Message Feedback Dataset Events Trigger Another Journey Using a Unitary Event? | Community
Skip to main content
R
ramadevi
Level 1
June 11, 2026
Question

Can AJO Message Feedback Dataset Events Trigger Another Journey Using a Unitary Event?

  • June 11, 2026
  • 3 replies
  • 29 views

Hi Adobe Community / Support Team,

I am testing a use case in Adobe Journey Optimizer / AEP and need confirmation on whether this architecture is supported.

Scenario:

I have two journeys.

Journey 2 is triggered by a unitary event. Once the event qualifies, Journey 2 sends an email using an email action node.

After Journey 2 sends the email, I can see send/bounce/message feedback events written into the AJO Message Feedback Experience Event dataset. This dataset is enabled for Profile.

I created Journey 3 with a unitary event trigger. The intention is for Journey 3 to listen for new message feedback records written after Journey 2 sends the email, filtered by Journey 2’s journeyVersionID. Once Journey 3 is triggered, it uses a custom action to send the latest message feedback data to an external system for immediate feedback of email.

What I observed:

1. Journey 2 is successfully triggered by the unitary event.
2. Journey 2 successfully sends the email.
3. Message feedback events are generated for the email send.
4. The message feedback records eventually appear in Query Service.
5. Query visibility is delayed. It takes around 30 minutes for the records to show up in query results, even though the event insertion timestamp appears to be earlier.
6. Journey 3 does not trigger when I configure the unitary event using the message feedback dataset and filter by Journey 2’s journeyVersionID.

Questions:

1. Is it supported to use the AJO Message Feedback Experience Event dataset as a unitary event source to trigger another journey?
2. Are message feedback dataset records emitted through the same real-time event ingestion path that Journey Optimizer unitary event triggers listen to?
3. What is the correct identity namespace to use for message feedback events to when a unitary event is created on it in the journey canvas? Should the namespace be based on the identityMap field?
4. If this pattern is not supported, what is the recommended architecture for sending AJO email send/bounce/error feedback to an external system in near real time?


Actual behavior:
The feedback event is eventually visible in the message feedback dataset through Query Service, but Journey 3 does not trigger from that feedback event.

My assumption:
The message feedback dataset may be intended for reporting/query/profile history and may not be a supported real-time event source for Journey unitary event triggers. Could someone confirm whether this design is supported and what the recommended approach should be?

3 replies

A
adesrala1
Level 2
June 12, 2026

Based on Adobe documentation and the behavior described, this pattern is not currently supported.

Journey Optimizer unitary events can only be triggered by events arriving through the real-time streaming event ingestion pipeline. Internal AJO datasets, such as Message Feedback and Email Tracking, are intended for reporting, profile enrichment, and analytics, but are not supported sources for triggering journeys.

This aligns with the observed behavior:

  • Journey 2 is triggered and sends the email successfully.

  • Message Feedback records are generated and eventually appear in Query Service.

  • Journey 3 does not trigger from those records.

Because of this limitation, the issue is not related to the identity namespace used when configuring the event. The Message Feedback dataset itself is not a supported journey trigger source.

For near real-time integration with external systems, Adobe generally recommends using platform integration/export patterns rather than attempting to trigger a second journey from Message Feedback events.

Documentation:

    SatheeskannaK
    Community Advisor
    SatheeskannaKCommunity Advisor
    Community Advisor
    June 12, 2026

    ​@ramadevi 

    • AJO out-of-the-box datasets—such as the message feedback event dataset—cannot be used as unitary event triggers. This guardrail prevents message feedback from accidentally triggering journeys.

    https://experienceleague.adobe.com/en/docs/journey-optimizer/using/get-started/essentials/guardrails#events-g

    • To send this data to external systems, you can export it using cloud storage destinations for near-real-time delivery, though true real-time processing is not supported.

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

     

    Thanks, Sathees
      DavidKangni
      Community Advisor
      DavidKangniCommunity Advisor
      Community Advisor
      June 12, 2026

      ​@ramadevi 
      You can’t trigger events from AJO ootb system datasets.

      Also The AJO Message Feedback Event Dataset is transitioning from streaming to batch ingestion mode. This change is to ensure that data ingestion does not exceed streaming ingestion limits. If you use this dataset expect an increase in data latency of up to 2 hours going forward.

      Your best option to send data to external is destination and you can schedule incremental exports every 3 hours.

      Thanks,

      David

      David Kangni
        Terms & ConditionsAccessibility statement

        Loading footer...