Prevent automatic merging of Contacts created by different live sites and having same Email ID.

Yashdeep Patidar asked on July 27, 2020 15:46

Hi Team,

I have two MVC live sites running on a same Kentico Admin instance. Currently kentico merges the contacts which are having same Email ID and even if they are created by different live sites. I have below two queries:

  1. How can I prevent merging of contacts of two different live sites even if the contact have same Email ID?
  2. Is there any way that I can assign site to contact when the contact is created, so that I can differentiate which contact belongs to which live site.

Recent Answers


Dmitry Bastron answered on July 27, 2020 18:02

Hi Yashdeep,

It is not possible. The system automatically merges contacts based on their email address and this doesn't seem to be customizable. Also, Contacts are global objects, these are not site-specific. It means if you have multiple sites sharing the same database - the contacts will be shared between sites.

I'm afraid the only option here would be completely separating two sites if this is a strict requirement.

1 votesVote for this answer Mark as a Correct answer

Yashdeep Patidar answered on July 29, 2020 09:01

Hi Dmitry,

Thank you for your support in resolving my queries.

As we also have Accounts and Contact Groups under Contact Management, So I am thinking to create either two accounts or two contact groups for my two different sites and will be adding the contacts to these two accounts or groups based on some condition using the marketing automation process. So should I use Accounts for this purpose or Accounts should only be used for some other specific use case and I should use Contact Groups instead of Accounts?

0 votesVote for this answer Mark as a Correct answer

Dmitry Bastron answered on July 29, 2020 10:46

Accounts serve a different purpose, more for B2B websites:

Accounts represent organizations, i.e. companies or other commercial or non-commercial bodies. You can use accounts to categorize your contacts based on their affiliations.

Contact Groups might work better, but I'd probably add a custom Sites field to contact class or a binding class between Contacts and Sites and fill it following your required logic. I wouldn't say this is the best way of doing things, but it should work for your case if fully separating sites is not an option.

0 votesVote for this answer Mark as a Correct answer

   Please, sign in to be able to submit a new answer.