Hello Community,
I have the following questions regarding discarded profiles that are logged in the Journey Step Event dataset/schema:
How can I obtain detailed information about why a profile was discarded? We have the eventType(has Reason shortform) in the schema under serviceEvent.stateMachine and serviceEvent.dispatcher, but I'm having trouble understanding the reasons.
What is the difference between the serviceEvent.stateMachine and serviceEvent.dispatcher objects in the Journey Step Event dataset/schema?
Once an event hits AEP and is eligible to enter the Journey but somehow gets discarded, how can I capture that information and send it back to a third-party platform to retrigger? The Journey Step Event only contains the Profile ID, so how can I identify the specific event associated with that profile?
Solved! Go to Solution.
Views
Replies
Total Likes
I guess that you have already verified the namespace of the profile with the unitary event as well for these profiles that didn't enter the journey. However, if you still believe the profile event is carrying the correct information but is not qualifying for the event and not entering the journey, please reach out to the Adobe support team for further assistance.
Kindly note that if profiles do not enter the journey, any audit information for those profiles will not be recorded in the journey_step_events
table.
Hi Avinash,
Check out AJO schema dictionary for a detailed description of fields https://experienceleague.adobe.com/tools/ajo-schemas/schema-dictionary.html?lang=en
Check out actionExecutionErrorCode, actionExecutionError from journey_step_events fields to understand error . Once http error code is known, can understand a bit more info on the error's root cause in general.
sample query
select
_experience.journeyOrchestration.stepEvents. actionExecutionErrorCode,
_experience.journeyOrchestration.stepEvents.actionExecutionError,
_experience.journeyOrchestration.stepEvents.stepStatus
from journey_step_events
where
_experience.journeyOrchestration.stepEvents.journeyVersionID IN ('b2433e9c-6711-404e-813e-c38fba02ec83')
You can use custom action to share info with 3rd party system or store the failed events back into AEP data set to trigger journey again. Check out
Views
Replies
Total Likes
Hello @Anuhya-Y ,
Thanks for your thought, I will elaborate the the problem statement here,
so By below Query i am getting Discarded profiles (event ingested in Experience Schema but not entered in Journey).
Views
Replies
Total Likes
Couple of questions regarding the journey setup:
A quick note: If a specific event type is not qualified by the profile or system action, the profile will not enter the journey where the event is used. Consequently, any audit information for such profiles will not be captured in the journey_step_events table.
Additionally, if the event is not the first in the journey, it might be helpful to enable the event timeout path and include a custom action to send data back to the third-party system
Views
Replies
Total Likes
Hi @Anuhya-Y ,
We are using a unitary rule-based event action in the journey, which is the first activity. Discarded profiles are eligible for the rules applied in this event.
The event rule used is 'eventType = 'Letter_Name'. Approximately 80 to 90% of profiles are able to enter, while the remaining profiles are discarded.
Views
Replies
Total Likes
I guess that you have already verified the namespace of the profile with the unitary event as well for these profiles that didn't enter the journey. However, if you still believe the profile event is carrying the correct information but is not qualifying for the event and not entering the journey, please reach out to the Adobe support team for further assistance.
Kindly note that if profiles do not enter the journey, any audit information for those profiles will not be recorded in the journey_step_events
table.
Views
Replies
Total Likes
@Avi_Barge yes, if a profile is not entered in the Journey, then the Journey step event schema won't capture the audit.
I do not find documentation specific to "UNEXPECTED_EVENT_IN_CURRENT_STEP" and "notSuitableInitialEvent"
Views
Replies
Total Likes
Views
Likes
Replies