| Unique IDs | Login IDs | New Known User | On Logout |
|---|---|---|---|
| Customer ID |
Customer ID |
Create new Identity Record | Always create a new anonymous profile on each logout. |
While the profile isolation strategy aims to maximize the integrity of known user profiles, the profile link strategy is focused on tracking what drives users to create an account and make purchases, so it is particularly concerned with the transition from anonymous to known user. The profile link strategy gives you the opportunity to attribute anonymous activity in your app to the next logged-in user, by aliasing the new known user record to the previous anonymous record. Each ’Logout’ request to the identity API creates a new user profile, identified only by device ID.
Example identity priority
| Scenario | Initial Profile | Request | New Profile |
|---|---|---|---|
| First App Launch User launches the app and the mParticle SDK |
none | Identify IDFV: 9876 |
Profile 1 (Anonymous) mParticle ID: 1234IDFV: 9876 |
| User logs in User creates an account and logs in with their email address. App backend generates a Customer ID |
Profile 1 (Anonymous) mParticle ID: 1234IDFV: 9876 |
Login Customer ID: ABC123Email: ed.hyde@example.comIDFV: 9876 |
Profile 2 (Transition to Known User) mParticle ID: 2345Source: 1234Customer ID: ABC123Email: ed.hyde@example.comIDFV: 9876 |
| User logs out User signs out of the app on their device |
Profile 2 (Known User) mParticle ID: 2345Source: 1234Customer ID: ABC123Email: ed.hyde@example.comIDFV: 9876 |
Logout IDFV: 9876 |
Profile 3 (Anonymous) mParticle ID: 3456IDFV: 9876 |
| User interacts via different channel User sends an email to support but uses a different address. |
None | This interaction arrives at mParticle via a feed. No direct request is made to the Identity API. Assuming the address is unknown, a new profile is created. | Profile 4 (Known User) mParticle ID: 4567Email: h.jekyll.md@example.com |
| Returning User User logs back into the app |
Profile 2 (Anonymous) mParticle ID: 2345IDFV: 9876 |
Login Customer ID: ABC123Email: ed.hyde@example.comIDFV: 9876 |
Profile 2 (Known User) mParticle ID: 2345Source: 1234Customer ID: ABC123Email: ed.hyde@example.comIDFV: 9876 |
| User Updates Email User changes their account email to the same address they used to contact support |
Profile 2 (Known User) mParticle ID: 2345Customer ID: ABC123Email: ed.hyde@example.comIDFV: 9876 |
Modify mParticle ID: 2345Customer ID: ABC123Email: h.jekyll.md@example.comIDFV: 9876 |
Profile 2 (Known User) mParticle ID: 2345Source: 1234Customer ID: ABC123Email: h.jekyll.md@example.comIDFV: 9876Since email must be unique, the email is removed from Profile 4, which is now orphaned Profile 4 (orphaned) mParticle ID: 4567 |
| New Device Launch User downloads and launches the Roku version of the app. |
None | Identify Roku ID: 8765 |
Profile 5 (Anonymous) mParticle ID: 5678Roku ID: 8765 |
| New Device Login User logs into the new app with email address. Server returns Customer ID |
Profile 5 (Anonymous) mParticle ID: 5678Roku ID: 8765 |
Login Customer ID: ABC123Email: h.jekyll.md@example.comRoku ID: 8765 |
Profile 2 (Known User) mParticle ID: 2345Customer ID: ABC123Email: h.jekyll.md@example.comIDFV: 9876Roku ID: 8765 |
Was this page helpful?