Account Number and Email Address Reconcilation

[vikramcl]

Dear Community,
Greetings! 
I have setup an event that triggers the journey. The event has the 'accountNumber' and 'phoneNumber' attributes. 
Now, I need to find the 'email address' associated with the 'accountNumber' or 'phoneNumber' and send out an email to the user. 
Account Number is the primary key here. 
How can we accomplish this within the journey? 
Thanks in advance. 

[SashankaBi1]

Hi @vikramcl,

Imagine the data in AEP as being stored in two tables: 

1. Profile table

2. Event table.

The primary key namespace defines the join between these two tables.

A unitary event monitors the Event table. Once the defined condition defined in the event is met, it triggers the journey and brings the guest into the Journey flow.

At this point, all profile attributes - including personalEmail.address - are available for personalization, provided they exist in the profile.

The Email action in AJO can then use this email attribute to send the communication.

Hope this helps visualize the scenario.

Thanks a lot!

Sashanka B

[vikramcl]

Thank you @SashankaBi1 for your kind response. 

Below is the attached sample journey snapshot I am testing out for this PoC. 

As you could notice, we are using 2 unitary events from 2 different APIs.
Both the events doesnt contain the emailAddress. 

1st event contains the accountNumber which is a primary key in the schema we have used. This data is being stored in let's say dataset1.  2nd event also doesnt contain email address as well. accountNumber is the primary key here too. Both the events are using the same schema which is profile enabled. Also, have a separate dataset. 

I feel I would like to fetch profile level data in this case. Can I add a node in between these 2 events to pull the email address and pass on to send out an email as soon as the 2nd event gets triggered? 

[SashankaBi1]

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

[SatheeskannaK · Accepted solution]

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

[Sukrity_Wadhwa]

Hi @vikramcl,

Were you able to resolve this query with the help of the provided solutions, or do you still need further assistance? Please let us know. If any of the answers were helpful in moving you closer to a resolution, even partially, we encourage you to mark the one that helped the most as the 'Correct Reply.'

Thank you!