build an audience using condition in Journey

[AvlinPr]

 Hi, I want to create an audience based on a journey condition. example invalid emails i want to create an audience for invalid email then we can send them day 10 mando comms. I have tried nodeID but it is not working. giving me 0 count. How can i do this? 

[hegi90 · Accepted solution]

Hi

I guess this is not possible, as the journey information is stored inside journey_step_events, which is not part of the profile storage and not accessible for audience creation, it's lake only. You could do a query to get the profile id's of failed journeys:

select _experience.journeyOrchestration.stepEvents.profileID, _experience.journeyOrchestration.stepEvents.nodeName,_experience.journeyOrchestration.stepEvents.nodeID from journey_step_events WHERE _experience.journeyOrchestration.stepEvents.nodeID = '{your node}'

 And then make a scheduled query which makes a CTAS for your failed profile id's and make this new dataset available to profile storage to use it in audiences. Hope that helps. Or use data distiller for a curated dataset if you have this tool lisenced. 

[SaurabhCh3]

Journey Step Events are not profile enabled, hence can't be used in Audience creation. 

It is not recommended to enable it for profile due to sheer size. 

If you have data distiller (DD) SKU, you can create a audience via DD and then activate it or use it within the journey.

https://data-distiller.all-stuff-data.com/unit-6-data-distiller-audiences/dda-200-build-data-distill...

[marc_stowe_za]

Hi, agree with the other comments you may need to run some code and build a data set.

Find the reasons you wopuld like to include in the failure list:

select distinct _experience.customerjourneymanagement.messagedeliveryfeedback.messagefailure.reason
from ajo_message_feedback_event_dataset

and then run some data distiller writing to a profile enabled enrichment table that you can query, something like:

insert into <table>
select struct <your layout, probably profile primary id and timestamp >
FROM
(
select identitymap['your primary namespace'][0].ID
from ajo_message_feedback_event_dataset
where _experience.customerjourneymanagement.messagedeliveryfeedback.messagefailure.reason in ('your','chosen','reasons')
)

something along those lines should work

Another one to try test, and I'm not sure how it will see it exactly, but on the email in the journey, click the 'other path for timeout and or error' and see if those profiles go down that leg. If so, add an update task and update the pfile with a field that marks the email as invalid and needs the second message. Not sure on that one, but also worth a try

cheers

Marc