When Klaviyo goes live, a typical member will interact with all three systems. So, Flexie's developers want to make sure that their systems recognize each person as one person, and not three.
Understand the identifier hierarchy
When two profiles share a matching identifier, Klaviyo merges them in two steps. First, it confirms the profiles belong to the same person. Second, it picks one profile to keep (the destination) and merges the other into it (the source).
Klaviyo matches profiles on identifiers, not names. When one action sends identifiers that both profiles already hold, Klaviyo can merge them. A shared phone number, like a family landline, can wrongly merge two different people.
In an automatic merge, the identifier hierarchy decides which profile becomes the destination. The other profile's history, properties, consent, and suppression move into it. Manual merges let you choose the destination yourself.
Priority | Identifier | What it means |
|---|---|---|
1 | Profile ID | Klaviyo's own ID for the profile. |
2 | External ID | A stable ID assigned by an outside system, such as Mindbody or a point-of-sale system. |
3 | An email address associated with the profile. | |
4 | Phone number | A phone number associated with the profile. |
5 | Anonymous mobile app ID | An identifier for an unidentified mobile app profile. |
Use email as the primary identifier whenever possible. External ID is appropriate for specific identity architectures, but introducing it without a clear strategy can create duplicate profiles, especially when other integrations identify customers by email. Profiles can use External ID, email, or both. If a profile uses External ID as its identifier, pass the same External ID on every call for that profile.
If you use an external ID, make sure your source system owns a durable, person-level customer ID and a strategy for authoritative member mapping. That means an upstream record that explicitly connects that ID to the person's email or phone number.
See Understanding identity resolution in Klaviyo for more information.
Here is what profile merging looks in practice
A new member, Priya, joins Flexie. Here's what happens across three touchpoints.
Day 1: Priya books her first class through Mindbody using her phone number. This is her first interaction with Klaviyo, so it creates a new profile with just her phone number.
Day 2: Priya buys a yoga mat on Flexie's site. She enters her email for her shipping notification. Klaviyo has never seen this email before, so right now, Flexie has a duplicate in the system: Priya with just a phone number, and Priya with just an email.
Day 84: Priya checks in for her first class (...New Years resolutions are hard!) and adds her email and phone number together, in a single record update. That single record, holding both identifiers, is what tells Klaviyo the day 1 and day 2 profiles are the same person, and merges them.
The surviving profile is the one that held the email, because email outranks phone number.
Now say the front desk assigns Priya a Member ID (an External ID) at signup, sent to Klaviyo along with her phone number. Separately, she signs up for the Flexie newsletter through a pop-up on the site, using her email. Again, Priya has two profiles.
Profile A: External ID + phone number
Profile B: email only
Both profiles now hold a high-priority identifier. External ID outranks email, and Profile B has no External ID to match against. These two profiles will not merge on their own, no matter how many classes Priya books.
It gets messier from here. If a later request comes in carrying both the external ID and the email, say the front desk updates her record, that email gets written onto Profile A. Now Profile A and Profile B both hold the same email address, split across two separate profiles. Flexie now has one person represented by two profiles with an identical email on file
Where possible, use email and phone as the primary identifiers when creating or updating profiles in Klaviyo. External ID can reliably match and update a profile when it's consistently present on every call, but it won't reconcile a profile that was already created separately under a different identifier, which is exactly what happened to Priya. If an external ID is required for reference, consider storing it as a custom profile property instead of setting it as the External ID field, so a mismatch never leaves two profiles stranded like this.
If someone opts into SMS with a phone number Klaviyo hasn't seen before, and nothing in that opt-in identifies their email profile, Klaviyo creates a new profile for just that phone number. For example, texting a keyword sends only a phone number.
Later, if that same person checks out and their existing email and the same phone number are sent together, Klaviyo can merge the two profiles. If the checkout only sends one of the two, the profiles stay separate.
These are the steps to take if Flexie confirms that both profiles belong to the same person. Who owns these steps depends on the merge method. Merges made with the Merge Profiles API are owned by the developer team. Manual merges in the Klaviyo UI can be done by the team that manages the profiles.
Identify the system that maintains the person’s account.
Confirm that it is stable, person-level, and mapped to exactly one member.
Compare identifiers, event history, properties, list memberships, consent, suppression, and flow-entry history.
Choose the profile with the correct source-system identity and the most appropriate data. Use profile age only as a tie-breaker. If it's unclear, confirm with your team which system is the source of truth for customer records.
Use the Merge Profiles API, or merge manually in the Klaviyo UI. Merging is permanent and can't be undone, so only merge once you've confirmed both profiles belong to the same person.
Add missing identifiers to the destination profile, record the source and destination Profile IDs, and monitor for new duplicates.
To prevent the duplicate from returning, make the reconciliation logic idempotent.