I have two contacts : In Audience Manager DB, its showing 2069(test1 user) and 2070(test2 user) ids for these two contacts while in Subscription DB its showing 2070(test1 user) and 2071(test2 user) for the same contacts. When I am trying to change the profile of test2 user(2070 of AM DB) from website, its showing me information of test1 user(2069 of AM DB) which is wrong. How can I resolve the same, Sync service is already running.


Keep in mind that the database IDs will not match across the two databases. That is perfectly normal.

What matters is the identification key(s) that you provide. They should be the same on both sides. If your problem is that they are not, you have a serious problem that we are unlikely to be able to solve through this site; you'll need to contact customer support.

If the problem is just with misunderstanding the identification of Contacts? Well, hopefully you are now the wiser :)

  • Contact_ID field in CONTACTS_EXTENDED_DETAILS is having different values in both the DBs. – user918 Mar 21 '14 at 7:03
  • As mentioned, that is perfectly normal. How are you loading the Contacts? If you used the sample pages as a starting point, you should be loading the contacts using the identification keys - which will match on both sides. – Peter Kjaer Mar 21 '14 at 8:44
  • I need to pick the contact using TCMID of the contact in one of the scenario so I am using something like Contact.GetFromContactIdentificatonKeys(new string[] { Context.User.Identity.Name }) and Contact.GetFromInternalContactId(TCMURI); in second case I am getting the wrong user because of Contact_ID differences in DBs – user918 Mar 21 '14 at 11:36
  • Indeed that will not work. You should use the identification keys to read the correct Contact. You cannot expect the same URI on CD and CM - that's not going to happen. – Peter Kjaer Mar 24 '14 at 11:03
  • Thanks Peter, I am not using Contact URI now. – user918 Mar 27 '14 at 4:56

I don't have a running AM setup to check right now, but I think that the IDs in the subscription management database do not necessarily match those in the CM side database.

The reason for this is that contacts can be created both on back and front ends so trying to have a unique single column index for both would be impractical, especially as you could have multiple front-end databases.

You need to identify which columns identify a contact uniquely as defined in the documentation [login required]. The sync process probably uses those to sync, rather than IDs.

  • Contact_ID field in CONTACTS_EXTENDED_DETAILS is having different values in both the DBs. – user918 Mar 21 '14 at 7:02

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.