How quickly Event reaction (open/clicks) are identified/realized in journey?

Forum|Forum|2 years ago
February 28, 2023
2 replies
2210 views

I have a journey, sending an email on an event , if email opened by user, then send second email. Journey holds event, email 1,event reaction- Read, Email-2 .

For example, first email received by user at 10 AM and opened immediately, how quickly Event open reaction is realized in journey and move towards sending second email.

Journey Optimizer

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

Best answer by nnakirikanti

@anuhya-y That will be Streaming Ingestion SLA of 2 secs to 1 minute. Let me knw if you need more details.

nnakirikanti

Accepted solution

Community Advisor

@anuhya-y That will be Streaming Ingestion SLA of 2 secs to 1 minute. Let me knw if you need more details.

Anuhya-Y

Author

Community Advisor

@nnakirikanti thanks for the reply.

May I know which dataset this info would be loaded via streaming ? is it cjm_email_tracking_experience_event_dataset ? It is been more than a day , I do NOT see tracking info of the specific journey in cjm_email_tracking_experience_event_dataset.

Have you come across issue where tracking info is not reflecting into the dataset in few hours? If yes, what are the steps taken to correct issue

nnakirikanti

Community Advisor

@anuhya-y yes it is "cjm_email_tracking_experience_event_dataset",

Check tracking enable at Email Action activity level.
Trigger an test email, get view source, decode (Quoted-Printable) email to find two types of url patterns /ee/v1/open (for email opens), /ee/v1/click (for email links click tracking)
Make sure the the "configId" param value which is the CJM datastream pre-created by Adobe service account exist.
Grab the open url and hit in browser to get image pixel render and rest is like streaming ingestion via edge.

Note: Use the datastream, dataflow attached to the stream and verify that things are flowing.

Let me know if this find's the problem of your issue that not been tracked.