Adobe Journey Optimizer

DN1191 · 11/27/25

Hi All,

We have event data coming from marketo using the OOTB Marketo source connector to AEP. This data is mapped to B2B Activities schema (Experience Event type) in AEP. I am trying to use this event data to trigger a journey and created an AJO event for the same. I see there are many profiles which has event posted under the event section in UI and the event attribute values are exactly matching the event condition I set up but the journey is not getting triggered. Also I set up an audience with same event conditions and the profiles are getting qualified in the audience. Also I am able to trigger the journey using test events in test mode. Can anyone please help me understand why event data from marketo is not triggering my journey ?

Below is my audience condition:

There are a few profiles qualified for this audience.

Below is my event condition:

The event posted on a profile qualified for the audience:

@SatheeskannaK Any help here ?

SatheeskannaK · 12/8/25

@DN1191 Just wanted to callout a few things to consider,

The mechanism by which Marketo data integrates into Adobe Experience Platform (AEP) requires a nuanced understanding, particularly regarding the distinction between person activities and the person record itself. While the connection from Marketo to AEP is streaming connection, the way individual customer data points tie back to a unified profile in AEP differs significantly for activities versus the core person record.

Consider a scenario where a known individual submits a form on a website managed through Marketo. This action, categorized as a "person activity" (e.g., Form Submission, Email Clicked), is immediately captured within Marketo. This activity data then flows into AEP via the established streaming connection, arriving in near real-time.

Crucially, the static person record data—containing attributes like name, email address, company, and other profile fields—flows separately from the activities. Both the activities and the person record data arrive in AEP's Data Lake. It is within AEP that the critical process of Profile Merge takes place.

AEP's Real-Time Customer Profile service takes these separate streams of data (the dynamic activities and the static profile attributes) and uses defined Identity and Merge Policies to stitch them together into a single, unified customer profile. This consolidation is not instantaneous, despite the streaming nature of the connection. The system requires a short duration to ingest both sets of data, process the identity graphs, and complete the profile merge operation. Based on current system observations and architecture, this merge can take approximately a maximum of 15 minutes before the fully unified, merged profile is updated and ready for use across all AEP services.

Therefore, the recommendation is to use these streaming Marketo events not as immediate journey triggers, but rather as data points for Audience Qualification Activity within a journey. Instead of starting a journey with the form submission event, the activity data should be allowed to enrich the profile first. The journey can then be triggered by an audience segment that qualifies an individual based on the attribute derived from or associated with the activity.

Hope this helps.

Thanks, Sathees

View solution in original post

parmeshwarr3905 · 12/1/25

Hi @DN1191 would you mind sharing journey screenshots, just to take a look at the configuration and get idea what you are trying to achieve?

DN1191 · 12/1/25

@parmeshwarr3905 I am just using the above shown event to trigger my journey.

Anuhya-Y · 12/1/25

@DN1191 Unitary journeys listen for streaming events into AEP, batch data ingested from Marketo will not trigger a unitary event journey by default.

https://experienceleague.adobe.com/en/docs/journey-optimizer/using/configure-journeys/events-journey...

DN1191 · 12/1/25

@Anuhya-Y We are using the OOTB Marketo source connection to AEP which is a streaming one.

Anuhya-Y · 12/1/25

@DN1191 Yes, only incremental records are ingested through streaming using the Marketo source connection.
Are the incoming events incremental that you are validating against the Unitary Event journey?

DN1191 · 12/1/25

@Anuhya-Y Yes, I am looking at the new records flowing from Marketo to AEP and not the historical ones. I created an audience with the same conditions (as shown in my screenshots above) and I see the audience is getting populated with new profiles everyday, but event is not triggering my journey for these profiles.

Anuhya-Y · 12/1/25

How quickly are these new records getting evaluated for the streaming audience? If the records are flowing via streaming ingestion, these profiles will get evaluated for the audience within 60 sec.

DN1191 · 12/1/25

@Anuhya-Y I have not tracked the timing of audience evaluation. But I see the event is posted on the AEP profile in less than 1 minute.

Anuhya-Y · 12/1/25

@DN1191

I suspect that the incoming incremental data is not landing as a streaming ingestion type. This can be cross-verified by checking the audience evaluation latency for the incremental records/profiles.

If you believe the above points are working as expected, then please follow up with Adobe Support on the issue, as all other configurations appear to be correct.

DN1191 · 12/1/25

Thank you @Anuhya-Y for your inputs. I will look into the latency for audience evaluation and go from there. Thank you !

MarcSt5 · 12/5/25

Hi, just a general comment around this, which may or may not have any relevance.

unitary events listen to the stream, not the dataset, so they react super fast and dont require data to be processed through the datalake. Also, using enrichment like data distiller and loading data into a schema / dataset will never fire a unitary evet (i know you arent doing this, just for reference )

streaming data sources, from my experience, hit the lake and profile store at pretty much the same time (so looking on profile you will see the data there on the hub), but for the audience (streaming) it still needs to process thorugh the lake and graph. From what I know the segment eval runs every 15 minutes for streaming. I've always worked on 30 minutes to be sure for streaming segment evaluation (so something like abandoned basket use cases with a 10 minute window juist wont work with a stream, which is why those events are on edge).

I know that doesnt help with your use case, just some extra info for reference.

sounds to me that you need to look at the marketo feed and the audience using it to make sure AEP recognises the feed as a stream and the audience is set as a streaming audience as well. Easy test for the marketo stream would be to put a unitary event on it and see that it fires (it will be super quick). If that works, its streaming perfectly, then you need to check the audience setup. If that is also streaming and there are no condiitions that would stop profiles executing, then its a support call i would think. Lots of very sharp people on the Adobe help desks

good luck

DN1191 · 12/11/25

Thank you for the response, this helps!

SatheeskannaK · 12/8/25

@DN1191 Just wanted to callout a few things to consider,

The mechanism by which Marketo data integrates into Adobe Experience Platform (AEP) requires a nuanced understanding, particularly regarding the distinction between person activities and the person record itself. While the connection from Marketo to AEP is streaming connection, the way individual customer data points tie back to a unified profile in AEP differs significantly for activities versus the core person record.

Consider a scenario where a known individual submits a form on a website managed through Marketo. This action, categorized as a "person activity" (e.g., Form Submission, Email Clicked), is immediately captured within Marketo. This activity data then flows into AEP via the established streaming connection, arriving in near real-time.

Crucially, the static person record data—containing attributes like name, email address, company, and other profile fields—flows separately from the activities. Both the activities and the person record data arrive in AEP's Data Lake. It is within AEP that the critical process of Profile Merge takes place.

AEP's Real-Time Customer Profile service takes these separate streams of data (the dynamic activities and the static profile attributes) and uses defined Identity and Merge Policies to stitch them together into a single, unified customer profile. This consolidation is not instantaneous, despite the streaming nature of the connection. The system requires a short duration to ingest both sets of data, process the identity graphs, and complete the profile merge operation. Based on current system observations and architecture, this merge can take approximately a maximum of 15 minutes before the fully unified, merged profile is updated and ready for use across all AEP services.

Therefore, the recommendation is to use these streaming Marketo events not as immediate journey triggers, but rather as data points for Audience Qualification Activity within a journey. Instead of starting a journey with the form submission event, the activity data should be allowed to enrich the profile first. The journey can then be triggered by an audience segment that qualifies an individual based on the attribute derived from or associated with the activity.

Hope this helps.

Thanks, Sathees