|Unique IDs||Login IDs||On New Known User||On Logout|
|Customer ID||Customer ID||N.A.||Create new MPID|
Unless stated otherwise by your account representative, your new mParticle account will be configured with the default IDSync settings, described below.
Configuring multiple login IDs can result in the creation of unwanted duplicate user profiles.
For example, if a user already has already created profile using their email address as a login ID, but your app allows them to login using a different unique ID, then IDSync might create a new profile using the alternative unique ID. This would result in the user data for that customer becoming split between two profiles.
The default identity scope is set to
Recall that all data in mParticle is organized in three tiers: an organization can contain one or more accounts, and each account can contain one or more workspaces. Your identity scope determines if user data can be shared between different workspaces and accounts.
The workspace identity scope means that user profiles and known users are only required to be unique within the scope of a single workspace. This helps to prevent any unwanted data corruption that could result from using IDSync in multiple workspaces.
The default identity strategy is set to
The profile conversion strategy is designed to help you build a complete record of a user’s journey through the entire signup funnel, from an initial page view or app load to the creation of an account.
This identity strategy also supports the use of aliasing.
The default identity hierarchy is:
Was this page helpful?