Expand my Community achievements bar.

Join us on September 25th for a must-attend webinar featuring Adobe Experience Maker winner Anish Raul. Discover how leading enterprises are adopting AI into their workflows securely, responsibly, and at scale.
SOLVED

Unitary event use in journey

Avatar

Level 3

Hi,
I am trying to send an email in journey based on an unitary event. I am able to work on the journey and get the email in test mode. After publishing the journey I am not seing profiles being qualified.

Also, these profiles didn't already exist in AEP. We are sending an event when user performs the action which basically creates the profile and adds the event to the profile. Does the profile need to already exist in AEP for the unitary event to work in journeys?

Thanks in Advance.
@SatheeskannaK  @Anuhya-Y @Mohan_Dugganab @DavidKangni 



1 Accepted Solution

Avatar

Correct answer by
Level 3

Thanks for the early response, I was missing the eventType field in the event configuration. After updatig that journey worked.

View solution in original post

6 Replies

Avatar

Community Advisor

@dhanesh04s Profiles do not need to pre-exist in AEP.

Check Namespace and Profile identifier used in the unitary event that data should be available/compatible with the incoming profile

Avatar

Level 3

Thanks @Anuhya-Y  for the response, we are using customer id as namespace in the event and same id is part of the identities for the profile.

Avatar

Employee Advisor

Try validating the namespace and the event definition with the actual event data that is coming in, to see if that meets the criteria.

 

Also, by default email execution address is set to personalEmail.address  - you may want to overwrite it (if this is not being populated) with the attribute that contains the email value.

Avatar

Level 3

@Mohan_Dugganab  I validated both the things and I have changed the email execution address in email parameters.

Avatar

Employee Advisor

Can you share the journey flow ?

Avatar

Correct answer by
Level 3

Thanks for the early response, I was missing the eventType field in the event configuration. After updatig that journey worked.