Skip to main content

Streamlining Customer Data: Merging Independent Contacts in Sitecore

Streamlining Customer Data: Merging Independent Contacts in Sitecore

In my project, I had a requirement involving a form that collected the first name, last name, and email address, with the email serving as the unique identifier. Additionally, there was a separate login portal that required a username and password, where the username was the unique identifier. When a user submitted the form, their first name, last name, and email were displayed in the Experience Profile. When the user logged into the portal, their username (in the custom tab), along with their first and last name, was displayed in the Experience Profile.

Since the email and username were different identifiers, Sitecore was creating two separate contacts in the Experience Profile. However, the client's requirement was to have a single contact for the same user. The Experience Profile should display the first name, last name, email, and username (in a custom tab) all under one unified contact.

To achieve this functionality I have done the following:

Create Form Contact

  • In the form, before creating a contact, you can check if  'userIdentifier' exists in Tracker.Current.Session.Contact?.Identifiers 
 var loginIdentifier = Tracker.Current.Session.Contact?.Identifiers?.FirstOrDefault(x => x.Source == 'userIdentifier')?.Identifier;  

  • In the form, create a new contact if it doesn't already exist in xDB.
  • Identify the user by their email address, so if the same user submits the form from multiple devices, Sitecore will merge all contacts into a single contact.
  • After creating the formContact, check if both the loginIdentifier and formContact are not null. If both are valid, retrieve the login contact from xDB. Once you have both contacts, you can proceed to merge them.
  •  if (loginIdentifier != null && formContact!=null)  
           {  
             var loginTrackerIdentifier = new IdentifiedContactReference("loginUser", loginIdentifier);  
             if (loginTrackerIdentifier != null)  
             {  
               var contactExpandOptions = GetContactExpandOption();  
               Contact loginContact = client.Get(loginTrackerIdentifier, new ContactExpandOptions(CollectionModel.FacetKeys.PersonalInformation));  
               client.MergeContacts(loginContact, formContact);  
               client.Submit();  
             }  
           }  
    

Create Login Contact

  • In the form, before creating a contact, you can check if  'loginIdentifier' exists in Tracker.Current.Session.Contact?.Identifiers 
  var formIdentifier = Tracker.Current.Session.Contact?.Identifiers?.FirstOrDefault(x => x.Source == 'formIdentifier')?.Identifier;   

  • In the login portal, create a new contact if it doesn't already exist in xDB.
  • Identify the user by their username, so if the same user submits the form from multiple devices, Sitecore will merge all contacts into a single contact.
  • After creating the loginContact, check if both the formIdentifier and loginContact are not null. If both are valid, retrieve the form contact from xDB. Once you have both contacts, you can proceed to merge them.
  •  if (formIdentifier != null && loginContact!=null)   
         {   
          var formTrackerIdentifier = new IdentifiedContactReference("formUser", formIdentifier);   
    if (formTrackerIdentifier Identifier != null)
    { var contactExpandOptions = GetContactExpandOption(); Contact formContact = client.Get(loginTrackerIdentifier, new ContactExpandOptions(CollectionModel.FacetKeys.PersonalInformation)); client.MergeContacts(formContact , loginContact);
    client.Submit(); } }

Comments

Popular posts from this blog

Sitecore 10.2 - “Failed to start service ‘Sitecore Marketing Automation Engine’” on Windows 11

Sitecore 10.2 - “Failed to start service ‘Sitecore Marketing Automation Engine' ” on Windows 11 Today I started to install Sitecore 10.2 using Sitecore Instance Manager on Windows 11 and I got this issue “Failed to start service ‘Sitecore Marketing Automation Engine' ” . Error : On event viewer it was showing the below error: I also tried to run ‘ Sitecore.MAEngine.exe ’ like this C:\Windows\system32>C:\inetpub\wwwroot\sclocal102xconnect.dev.local\App_Data\jobs\continuous\AutomationEngine\Sitecore.MAEngine.exe Which was throwing below error: Starting Marketing Automation Engine... 2022-01-29 22:21:11 ERR Error initializing XConnect client. System.AggregateException: One or more errors occurred. ---> Sitecore.XConnect.XdbCollectionUnavailableException: An error occurred while sending the request. ---> System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The underlying connection was closed: An unexpected err

Sitecore Custom API Issue with Federation Authentication

Sitecore Custom API Issue with Federation Authentication In earlier segments, detailed in Part 1 and Part 2 of the blogs on Keycloak Integration with Sitecore, I introduced Keycloak functionality for CM login. Concurrently, I addressed a necessity to develop custom APIs for retrieving Sitecore users and roles. Following the development of custom APIs, during authentication failures, the API erroneously returned a status code of 200 instead of 401. The problem arose because API requests were being routed through the "owin.identityProviders" pipeline, which was not intended for API usage. Solution: When OWIN identifies a 401 response and the AuthenticationMode is set to "Active," it fails to capture the URL hash included in the request. Another choice is to activate the "Passive" AuthenticationMode, wherein OWIN refrains from actively intercepting 401 responses. In passive mode, your application needs to explicitly issue a Challenge to trigger the OWIN aut

Azure AD Integration with Sitecore 10.2

 Azure AD Integration with Sitecore 10.2 Sitecore identity server that comes with Sitecore 9.1 allows you to log in through an external identity provider like Azure Active Directory, Facebook, Apple, or Google. It is built on Federation Authentication. What is Federation Authentication? Federation authentication is a technology to allows users to access multiples application, tools, and domains using one credential. Using one set of credential user can access multiple applications, and resources after authentication.  Federation authentication consists of two systems, the Identity provider and the Service provider. Identity providers that maintain/create/manage identity information like name, email address, device, and location. Some examples of identity providers are Azure AD, Google, Facebook, and Apple. Service providers basically refer to a website, software, or app that the user is trying to access and SP basically relies on the identity provider to authenticate the user and provi