Merging Shopify ID with Phone Number for Simplified ID Project
i i merge two profile programatically in the simpified id mearge project one is shopify id and another is phone number now i want to use phone number going forword
i i merge two profile programatically in the simpified id mearge project one is shopify id and another is phone number now i want to use phone number going forword
Hi Vaibhav S., Please stand by as I search the Mixpanel knowledge base for an AI-powered answer. I normally take about 15 seconds or so. In case AI cannot answer your question, feel free to reach out to Mixpanel support at mixpanel.com/get-support. If you have follow-up questions for this thread, please tag me again with your question: @kapa.ai <follow-up question> 👋
Feel free to ask a follow-up question once I've answered by mentioning me with @kapa.ai
You’re on a Simplified ID Merge project, so there is an important limitation: - Each identity cluster can contain only one $user_id, and
- You cannot merge two $user_ids or “swap” the $user_id. [Simplified FAQ; Migration considerations]In your case: - You already have one cluster where:
- $user_id = Shopify ID
- Phone number was previously used as another ID and got treated as a $device_id (anonymous ID) when merged. [Migration considerations]Because of this: 1. You cannot programmatically “promote” the phone number to become the new $user_id for that existing cluster in a Simplified project.
2. If you start sending events with $user_id = phone number now, Mixpanel will create a new, separate identity cluster for that phone number, not merge it into the existing Shopify-ID cluster. [Migration considerations]**Recommended approach in Simplified ID Merge:**- Pick one stable, unchanging $user_id per user (e.g., internal DB ID or Shopify ID) and keep using that going forward. [Simplified FAQ]
- Store the **phone number as a profile property (e.g. phone_number or $phone) rather than as a $user_id. [Reserved properties]
- If you truly need phone number as an alternate “login ID” that can be merged with others, that use case is better served by Original ID Merge or Legacy (using $merge / $create_alias), not Simplified. [Migration considerations; Original FAQ]So in your current Simplified project, there is no supported way (per the docs) to re-point an existing user from “Shopify ID as $user_id” to “phone number as $user_id” without creating a new identity cluster.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
Vaibhav S. What's the exact issue in this?
Ansh A. migrating a shopify store and wanted to change the identifier current identifier is shopify id and id merge is simplified id, and the new identifier is phone number so this is the isssue if i start sending the new implmentation in old project old user will have new profile if they wvisit again and no way to mearge them
curently only option is migation to new project with the transformation of identified id to new identifier but will lot the visitor acctivity on the other project