Hi @vikramcl ,
Please find the details of the events as given below.

When the unitary event triggers the journey, the associated guest profile and all its attributes become available within the Journey conditional activities and actions like email.
The key is to ensure that the conditions applied within the journey are well-aligned, covering all possible scenarios that might fail due to data inconsistencies or conditional logic gaps.
We need not carry the email id within the event so long it is available in the guest profile table.
Please review and let me know if this helps.
Thanks a lot.
Sashanka B
@vikramcl @sashankabi1
- If the emailaddress for the account number is already part of the unified profile in AEP, then you don't have to do anything.
- If that link between the account number and the email address doesn’t yet exist, you need to have a profile dataset ingested with the accountNumber(as the primary identity),phoneNumber, and emailAddress for each customer.
- For example, AEP already knows that "Account 12345" belongs to "Jonny," whose email is jonny@email.com, and phone number is 111-222-3333.
- But if that connection hasn’t been made yet, you can't identify the email address for the account number/phone number that comes in as part of the event.