Skip to content
Documentation
DropUI homepage
Topics

How DropUI identifies the same person

One person can sign up through a popup, place an order and appear in an import. DropUI matches identifiers so these events can belong to one profile. A similar first or last name alone is not enough to merge people.

What identifies a contact

Email and phone are matched within the account. Differences in email capitalization or surrounding spaces should not create another person. Use the country calling code for a phone number; comparing only its final digits is insufficient.

The same person can belong to several contact lists. A shared profile does not mean shared consent across brands or channels. Compare people and lists.

Check whether the records represent one person

  1. Search Contacts for the exact email or phone.
  2. Open the profile and compare both identifiers.
  3. Check sources and activity, including forms, imports and purchases.
  4. Review consent separately for the lists you intend to use.
Anna Demo's identifying email and phone. The name is descriptive, not an independent merging key.

Another form submission using a known email can update the existing profile. Do not expect another contact for every submission. Form responses remain separate events.

When email and phone identify different people

Suppose Anna's email belongs to one profile, but the phone in a new file belongs to Ola. There is no basis for automatically treating them as one person.

Read the affected row's explanation in the import preview. Correct the assignment in the source system and prepare another file. Depending on the conflict, a row may be skipped or a profile may require review. Do not change another person's number simply to clear the warning.

The preview helps detect repeated and invalid records before import. All records shown are demo data.

Handle duplicates without creating another identity

A repeated row does not provide another consent or recipient. For repeated entries in a file, the first valid row for the recognized email or phone is processed. Contradictory identifiers are not automatically combined.

If you cannot determine which profile is correct, send us the import or profile identifier and the discrepancy. A data correction request is different from manually adding someone to a segment.

Example of conflicting identifiers

RecordEmailPhone
Existing Annaanna@demo.example+48 500 000 101
Existing Olaola@demo.example+48 500 000 102
Incorrect rowanna@demo.example+48 500 000 102

The row combines Anna’s email with Ola’s phone. Correct it using the source records. The preview above shows file checks; this table explains the separate case of conflicting identifiers.

Have questions after reading this guide?

Get in touch. We’ll answer your questions and help you with setup, free of charge.

Patryk Surmacz

I’ll walk you through the settings, step by step.