Unitary event use in journey | Community
Skip to main content
Level 3
December 12, 2024
Solved

Unitary event use in journey

  • December 12, 2024
  • 3 replies
  • 1182 views

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 



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 DhaneshSh2

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

3 replies

Anuhya-Y
Community Advisor
Community Advisor
December 12, 2024

@dhaneshsh2 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

Level 3
December 12, 2024

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.

Mohan_Dugganab
Adobe Employee
Adobe Employee
December 12, 2024

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.

Level 3
December 12, 2024

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

Mohan_Dugganab
Adobe Employee
Adobe Employee
December 12, 2024

Can you share the journey flow ?

DhaneshSh2AuthorAccepted solution
Level 3
December 16, 2024

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