If an existing user chats to you in the Messenger anonymously, via incognito browser mode for example, a new lead profile will be created for them in Intercom. This means you’ll have both a lead and user profile for the same person. 

Note: You can learn more about how leads and users work in Intercom here.

When this happens, you can merge the lead profile with the user profile, so all of their information is tracked and stored in one place. Here’s how:

Merging lead and user profiles

A lead can be merged into an existing user’s account either manually, automatically or via the REST API. Merging a lead into a user means that any information associated with the lead will be transferred over to the user profile. 

There are certain types of profiles you can (and can’t) merge:

  • A lead can be merged into a user profile.
  • 2 leads cannot be merged.
  • 2 users cannot be merged. 
  • A user profile cannot be merged back into a lead profile

Here’s how to merge two profiles:

Manually merge profiles

You can trigger a manual merge by importing the lead via a CSV import. 

Note: The lead will need to have the same email address as that of an existing user in order for a merge to happen. 

You can read more about importing leads and users via CSV here.

Automatically merge profiles

Automatic merges require no action on your part. When a person visits your website in a logged-out state, they’re given an Intercom cookie to uniquely identify them. Once they start a conversation or reply to a message, they become a lead. 

If they log in or sign up to your product while the Intercom cookie is present, their lead profile will be automatically merged with their user profile. 

Merge profiles using the API

You can also use the REST API to convert a lead to user. Read more about it here.

Common questions about merging profiles

What data is included in the merge?

  1. Attributes from the lead profile (only if the existing user profile contains no value for those attributes)
  2. Conversations (all conversations associated with the lead and user profile will be included)
  3. Events (the first/last occurred and the event count; no metadata is included)

Why didn’t a lead merge?

Most of the time, lead and user profiles merge immediately. But since it's an asynchronous process, small delays can occur. For example, when a user logs in and there are one or more leads marked as requiring merging (based on cookie or email), the automatic merging process will begin on that user's next ping (page refresh). 

For leads created via our REST API:

  • If you create a lead via the API, and then a user with the same email address who didn't previously exist sends in a ping (by logging into your app), the lead and user profiles will merge automatically.
  • If you create a lead via the API and a user with the same email address already exists, then when that existing user sends in a ping (by logging into your app), the lead and user records will not merge automatically.
  • If you create a lead via the API, then create a user via the API, the lead profile won’t be merged automatically into the user profile when this user sends in a ping (by logging into your app).

If you’re still experiencing issues with merging profiles, reach out to us in the Messenger and we’d be happy to help 😊 

Did this answer your question?