Configuring contact recognition

Most 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. The contact recognition in Xperience is configured so that it best covers these scenarios – Xperience does not 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 and registering a custom implementation of the ICurrentContactProvider interface:

1. Open your live site project in Visual Studio.

2. Create a class that implements the ICurrentContactProvider interface (we recommend adding the class within a custom Code Library).

3. Implement your own logic for contact recognition.

   Copy

   
   
   
    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();
        }
    }
   
   
    

4. Register the class using the RegisterImplementation attribute.