How to identifying the customer as a single profile in AEP ,if customer using different login methods

[vinayababu]

Hi Team,

I have one question on defining the identity. During the registration, customer will submit basic details and get the user name and password. For example from the basic details , i am considering email as primary identity and creating the profile in AEP.

If website provides other login options like Continue with google, Facebook, X, Apple id etc.

Case 1 : Same customer using all the different options at different time intervals , how i can define the identity for each login method which should create single profile. For example google will use email as login id and will consider email as Primary identity in AEP. 

Case 2 : IF same customer using different emails for different login options, how to handle this situation.

Objective : 

1) Create single profile for single customer in AEP with different login options.

2) Identify customers based on login methods

Could you please suggest best options to handle the situations.

Thanks and Regards

Vinaya babu

[AtulChavan]

Hi @vinayababu ,
As best practice customer details always should come from CRM system or any enterprise system that is responsible for storing user customer details. AEP identity service rely on identity value and its name space as its just a simple database that store this information and runs consolidation process to flash a profile on demand.

If you are having customers login with different credentials there is no way AEP can recognise it if the person is same. You may use device id and some other information but it will never be perfect. 

You may ask your client how they're identifying it at first place and how authentication is handled. Are they using any IDPs ? You can use Identity provided by IDP to create profile with.

Hope this helps.

Regards,
Atul

[Parvesh_Parmar]

Hello @vinayababu , 

As far as I understand, this should work as long as the third-party providers (Google, Facebook, etc.) provide the email address along with their unique IDs, which is crucial in your case.

Let’s say your schema has the following identities:

• Email: Primary identity
• Google login ID: Secondary identity
• Facebook login ID: Secondary identity
• X login ID: Secondary identity

1. Case 1:

User Registers with Traditional Method:

The user creates an account using an email and password. The system stores this information in the user database, using the email as the primary identifier.

Next time the user logs in with Google, Facebook, etc.:

After a successful login, these apps will typically provide:

• The login ID (e.g., Google ID, Facebook ID)
• The email address

When this data is sent to AEP, it will automatically stitch the new login ID with the existing profile based on the email, ensuring the user is identified correctly.

2. Case 2:

If the customer registers directly with Facebook or Google:

These apps will provide:

• The login ID
• The email address

A unique profile will then be created in AEP based on the email.

Since Google, Facebook, and X only allow one account per email, they will consistently use the same ID for each email. As long as the email addresses are provided by these apps, there should be no issue with stitching profiles in AEP.

Hope this helps!

Best regards,
Parvesh

[vinayababu]

Hi Parvesh,

Thanks for your response. Both the options are looking good.

For my understanding , The login id will stitch to the profile for every time login happens. Over the time stitching of more login id's to the profile will not be good(Because the login happens every day with social media flatforms). 

In the AEP database also so many records will stored for the same customer this is another challenge. 

I am looking for the mechanism , during the first login only we need to capture the details instead of every login time. is website team can handle this situation ?

Could you please share your thoughts on above points.

Thanks and Regards

Vinaya Babu