Unless stated otherwise by your account representative, your new mParticle account will be configured with the default IDSync settings, described below.
\n\nThe default identity scope is set to workspace.
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.
\nThe 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.
\nThe default identity strategy is set to profile conversion.
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.
\nThis identity strategy also supports the use of aliasing.
\nOn Anonymous Browsing
\nIf match on device ID or cookie, use existing user. Else, create new user.
On New Known User
\nConvert anonymous user to known, persist previous event history.
On Login
\nResolve existing known user. Business decision to explicitly copy event history from anonymous session to logged in user or not.
On Logout\nCreate new user.
\nThe default identity hierarchy is:
\n| Identity | \nLogin | \nUnique | \nImmutable | \n
|---|---|---|---|
| Customer ID | \nY | \nY | \nY | \n
| \n | \n | \n | |
| Apple IDFA | \n\n | \n | \n |
| Apple IDFV | \n\n | \n | \n |
| Google Advertising ID | \n\n | \n | \n |
| Android Device ID | \n\n | \n | \n |
| AMP ID | \n\n | \n | \n |
| Device Application Stamp (mParticle cookie) | \n\n | \n | \n |
Configuring multiple login IDs can result in the creation of unwanted duplicate user profiles.
\nFor example, if a user already has a 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.
","frontmatter":{"title":"Default IDSync Configuration","order":7,"seoTitle":null,"seoDescription":null},"parent":{"__typename":"File","modifiedTime":"October 12, 2026"}}},"pageContext":{"slug":"/guides/customer-360/idsync/default-strategy/"}},"staticQueryHashes":["2950460867"]}