> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cometly.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshoot multiple emails on a contact

> Fix multiple emails on a contact in Cometly: find out why separate people were merged into one contact and how to stop it happening again.

You open a contact (a person Cometly has identified, with their visits and conversions) and see multiple emails on a contact that should be one person. In the **Contact** panel, the **Email** row shows one address with a **+1 more** (or higher) menu next to it, and the extra addresses belong to different people.

Cometly automatically merges contacts when the pixel (the Cometly script on your website) detects that they are the same person. For example, if someone uses one email on one form and another email on a different form, Cometly merges the two entries into a single contact. This keeps your data accurate and consolidated, but sometimes contacts merge incorrectly.

This guide covers the common causes and how to fix each one.

## Common causes of incorrect contact merging

### 1. Manual data entry on pages with the Cometly pixel installed

If your internal processes involve manually entering data on forms where the Cometly pixel is installed, contacts can merge by mistake. The pixel sees the activity as coming from the same person, even when it is not.

**Solution:**

* Avoid manual data entry on pages with the Cometly pixel installed.
* To keep entering data manually, duplicate the page and make sure the duplicate does not have the Cometly pixel installed. Use the duplicate page only for internal processes.

### 2. Pixel placed on every page of a SaaS app

SaaS companies often run into this when the Cometly pixel is installed across all pages of their app, especially if the app lets users invite team members. When a user enters another email address (for example, to invite a colleague), Cometly may merge the user's contact with the newly entered email address.

**Solution:**

1. Install the Cometly pixel on your marketing site, including your blog, academy and similar pages.
2. Within your app, limit the pixel to the registration and login pages.
3. Do not place the pixel on all app pages. This prevents merging during team member invitations and similar actions.

See [Pixel setup for SaaS companies](https://docs.cometly.com/guides/tracking/pixel-setup-for-saas.md) for the full setup.

### 3. The same comet\_token used for more than one contact

The `comet_token` is the identifier the pixel gives each visitor's browser. Each contact tracked by Cometly should have a unique `comet_token`. If the same `comet_token` is sent for multiple contacts, they are merged into a single contact.

**Solution:**

1. Go to **Events Manager** > **Events Log** and review your events regularly to check that the `comet_token` is unique for each contact.
2. Update your integration so that a `comet_token` is never reused across different contacts.

> [!TIP]
>
> To see the tokens tied to one contact, open the contact from **Contacts** and look at **Comet Tokens** under **Device Data**.

## Best practices for preventing incorrect merging

1. **Audit pixel placement:** Periodically review where the Cometly pixel is installed to make sure it fits your use case and internal processes.
2. **Educate your team:** Tell team members to avoid manual data entry on pages with the pixel installed.
3. **Monitor the Events Log:** Check for anomalies or duplicate `comet_token` usage and fix them promptly.
4. **Separate internal tools:** Use pixel-free pages for internal processes like manual data entry or team member invitations.

Following these recommendations prevents incorrect contact merging and keeps your data in Cometly accurate.

## Confirm a contact no longer collects multiple emails

After you apply the fix, open a contact from **Contacts** that came in after the change. The **Email** row in the **Contact** panel shows a single address, with no **+1 more** menu beside it. In **Events Manager** > **Events Log**, each new contact's events carry their own `comet_token`.

## Frequently asked questions

### What is a comet\_token in Cometly?

It is a unique identifier that links a visitor's browser session to their attribution data. The pixel creates it, and you can send it with events from your own integration so Cometly ties each event to the right visitor. See [Comet Token](https://docs.cometly.com/concepts/comet-token.md).

### How do I remove an extra email from a contact in Cometly?

Use the [Update Contact](https://docs.cometly.com/api-reference/endpoint/update-contact.md) API endpoint and send the full list of emails the contact should keep. Any email you leave out of the list is removed, and the first one becomes the contact's primary email.

### Can I merge two contacts manually in Cometly?

Yes. Open the contact you want to keep, select **Actions** > **Merge Contacts**, and enter the email address of the contact to merge into it. A manual merge cannot be reversed, so check the email before you confirm.

## Next steps

* [Set up the pixel for a SaaS app](https://docs.cometly.com/guides/tracking/pixel-setup-for-saas.md)
* [Use the Events Log to review incoming events](https://docs.cometly.com/support/troubleshooting/general/event-log.md)
* [Learn how the Comet Token works](https://docs.cometly.com/concepts/comet-token.md)
* [Browse all troubleshooting guides](https://docs.cometly.com/support/troubleshooting/overview.md)
* [See the ways to contact support](https://docs.cometly.com/support/contact.md)

Still have questions or need a hand? We're happy to help. Reach our team at [support@cometly.com](mailto:support@cometly.com).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.