AJO Sending using Custom Action

[ChanuteJo]

Dear Community

I would like to ask for the best recommendations using AJO for my client requirement. So in AEP, I created two schema, Individual Profile Class, and ExperienceEvent Class. What I want to achieve is creating an Audience in AEP, then using AJO to send ExperienceEvents field to Kafka. The limitation here is that the client only has Prime License. 

Currently, my AJO journey logic is attached below. During the wait activity, I configured to be 120s. This causes the Journey to work as it should be. However, I need the latency to be lower. When the Wait activity is changed to 60s, the Journey did not work. My Audience is triggered using ExperienceEvent data. However, when an ExperienceEvent is being ingested, there are some delays until the associated profile is being included in the Audience Membership.

My question is that what would be the shortest wait time I could configure to ensure that the associated profile is included in the Audience as soon as the event is triggered?

Please do not hesitate to ask for more information

Best regards,

Sching

[Abie]

Hi @ChanuteJo ,

There are multiple spots for delay in this process -
First - The event might take upto 15 minutes to reach AEP

Audience - The audience evaluation might take additional time ( which is happening in your case).

If you requirement is to forward the event to Kafka Topic, why would you want to do using audience evaluation. I mean, as soon as the event is received, trigger the action for that profile. I am wondering why do you need the audience to forward event data to kafka, do I miss something?

About waiting time, it really depends on the system. As long as 60 seconds or 120 seconds fall within the guardrails, it is an expected behavior.

Thanks!

[SatheeskannaK]

@ChanuteJo

It appears you're using streaming ingestion to push data into AEP, and audience membership is reflecting within 60 to 120 seconds. I recommend replacing the "wait" activity with "audience qualification" after the event trigger to see if that speeds up the journey processing.

While documentation indicates streaming events should reflect on profiles in under 60 seconds, this can vary based on several factors.

https://experienceleague.adobe.com/en/docs/experience-platform/ingestion/streaming/troubleshooting

[Abie]

Hi @SatheeskannaK ,

Is it 60 seconds or upto 15 minutes? I am referring below-

https://experienceleague.adobe.com/en/docs/experience-platform/ingestion/streaming/overview

Thanks!

[SatheeskannaK]

It depends on the factors mentioned in the documentation; it could take up to 15 minutes.