Configuring contact recognition

Most current sites need to deal with contact recognition scenarios involving visitors with the same IP addresses. Visitors often come from shared networks, such as company or municipal networks. Kentico's contact recognition is configured so that it best covers these scenarios. This means that Kentico doesn't automatically assign contacts to anonymous visitors based on their:

  • Browser user agent
  • IP addresses

The system also remembers contacts until their cookies are deleted or until a different contact is determined for the visitor.

If this behavior does not suit your needs, developers can change it programmatically by creating a custom implementation of Kentico's ICurrentContactProvider interface:

MVC sites

For sites built using the MVC development model, add the custom class to your MVC live site project (not the Kentico administration project).

Kentico EMS required

Features described on this page require the Kentico EMS license.

  1. Create a class that implements the ICurrentContactProvider interface.
  2. Implement your own logic for contact recognition.

    using System;
    
    using CMS;
    using CMS.Membership;
    using CMS.ContactManagement;
    
    [assembly: RegisterImplementation(typeof(ICurrentContactProvider), typeof(CustomCurrentContactProvider))]
    
    /// <summary>
    /// Summary description for CustomCurrentContactProvider
    /// </summary>
    public class CustomCurrentContactProvider : ICurrentContactProvider
    {
        public ContactInfo GetCurrentContact(IUserInfo currentUser, bool forceUserMatching)
        {
    		// Implement your contact recognition logic
            throw new NotImplementedException();
        }
    	
    	public ContactInfo GetExistingContact(IUserInfo currentUser, bool forceUserMatching)
    	{
    		// Implement your contact recognition logic
    		throw new NotImplementedException();
    	}
    
        public void SetCurrentContact(ContactInfo contact)
        {
    		// Implement your logic for storing information about the current contact
            throw new NotImplementedException();
        }
    }
  3. Register the class using the RegisterImplementation attribute.


Was this page helpful?