Profile Isolation Strategy (Premium)

Unique IDs Login IDs On New Known User On Logout
Customer ID
Email
Customer ID
Email
Create new Identity Record Return to existing anonymous profile

Use Cases

The Profile Isolation strategy is designed to maximise the integrity of each User Profile and to prevent anonymous data from being kept together with the data of logged in users. Under the Profile Isolation strategy, any time a user creates an account, a new Identity Record and a new user profile are created. Any anonymous data collected prior to the user signing up is not carried over to the new profile.

One of the main reasons to choose the Profile Isolation strategy is to ensure compliance with consumer protection and privacy laws. For example, if your user agreement includes permission to collect user data, it may be important not to combine user data from before the user signed up, accepting the user agreement, and after.

The Profile Isolation strategy is based on building highly reliably profiles around Login IDs, so any time an identity request includes an email address or customer ID, mParticle will return a unique Identity Profile for the user, regardless of which device they are using.

Identity Flow

Example Identity Priority:

  1. Customer ID
  2. Email Address
  3. IDFV
  4. Roku ID
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: 1234
IDFV: 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: 1234
IDFV: 9876
Login
Customer ID: ABC123
Email: ed.hyde@example.com
IDFV: 9876
Profile 2 (Known User)
mParticle ID: 2345
Customer ID: ABC123
Email: ed.hyde@example.com
IDFV: 9876
User logs out
User signs out of the app on their device
Profile 2 (Known User)
mParticle ID: 2345
Customer ID: ABC123
Email: ed.hyde@example.com
IDFV: 9876
Logout
IDFV: 9876
Profile 1 (Anonymous)
mParticle ID: 1234
IDFV: 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 3 (Known User)
mParticle ID: 3456
Email: h.jekyll.md@example.com
Returning User
User logs back into the app
Profile 1 (Anonymous)
mParticle ID: 1234
IDFV: 9876
Login
Customer ID: ABC123
Email: ed.hyde@example.com
IDFV: 9876
Profile 2 (Known User)
mParticle ID: 2345
Customer ID: ABC123
Email: ed.hyde@example.com
IDFV: 9876
User Updates Email
User changes their account email to the same address they used to contact support
Profile 2 (Known User)
mParticle ID: 2345
Customer ID: ABC123
Email: ed.hyde@example.com
IDFV: 9876
Modify
mParticle ID: 2345
Customer ID: ABC123
Email: h.jekyll.md@example.com
IDFV: 9876
Profile 2 (Known User)
mParticle ID: 2345
Customer ID: ABC123Email: h.jekyll.md@example.com
IDFV: 9876

Since email must be unique, the email is removed from Profile 3, which is now an orphaned.

Profile 3 (Anonymous)
mParticle ID: 3456
New Device Launch
User downloads and launches the Roku version of the app.
None Identify
Roku ID: 8765
Profile 4 (Anonymous)
mParticle ID: 4567
Roku ID: 8765
New Device Login
User logs into the new app with email address. Server returns Customer ID
Profile 4 (Anonymous)
mParticle ID: 4567
Roku ID: 8765
Login
Customer ID: ABC123
Email: h.jekyll.md@example.com
Roku ID: 8765
Profile 2 (Known User)
mParticle ID: 2345
Customer ID: ABC123
Email: h.jekyll.md@example.com
IDFV: 9876
Roku ID: 8765

Was this page helpful?