{"componentChunkName":"component---src-templates-markdown-template-jsx","path":"/guides/customer-360/idsync/identify-users/","result":{"data":{"pageMetadata":{"title":"Identify Users","path":"/guides/customer-360/idsync/identify-users/","sourceCode":null,"metadataParent":{"title":"IDSync","path":"/guides/customer-360/idsync/","sourceCode":null,"hasVersionPicker":null,"metadataChildren":[{"title":"IDSync Overview","path":"/guides/customer-360/idsync/introduction/","order":1,"label":null},{"title":"Use Cases for IDSync","path":"/guides/customer-360/idsync/use-cases/","order":2,"label":null},{"title":"Components of IDSync","path":"/guides/customer-360/idsync/components/","order":3,"label":null},{"title":"Store and Organize User Data","path":"/guides/customer-360/idsync/user-data/","order":4,"label":null},{"title":"Identify Users","path":"/guides/customer-360/idsync/identify-users/","order":5,"label":null},{"title":"Default IDSync Configuration","path":"/guides/customer-360/idsync/default-strategy/","order":7,"label":null},{"title":"Profile Conversion Strategy","path":"/guides/customer-360/idsync/profile-conversion-strategy/","order":8,"label":null},{"title":"Profile Link Strategy","path":"/guides/customer-360/idsync/profile-link-strategy/","order":9,"label":null},{"title":"Profile Isolation Strategy","path":"/guides/customer-360/idsync/profile-isolation-strategy/","order":10,"label":null},{"title":"Best Match Strategy","path":"/guides/customer-360/idsync/best-match-strategy/","order":11,"label":null},{"title":"Aliasing","path":"/guides/customer-360/idsync/aliasing/","order":12,"label":null}],"metadataParent":{"title":"Customer 360","path":"/guides/customer-360/","metadataChildren":[{"title":"Overview","path":"/guides/customer-360/overview/","order":0.5,"label":null},{"title":"User Profiles","path":"/guides/customer-360/profiles/","order":1,"label":null},{"title":"Identity Dashboard","path":"/guides/customer-360/identity-dashboard/","order":2,"label":null},{"title":"Identity Resolution Log","path":"/guides/customer-360/identity-resolution-log/","order":3,"label":null},{"title":"Household Reach","path":"/guides/customer-360/household-reach/","order":4,"label":null},{"title":"Calculated Attributes","path":"/guides/customer-360/calculated-attributes/","order":5,"label":null},{"title":"Predictions","path":"/guides/customer-360/predictions/","order":6,"label":null},{"title":"IDSync","path":"/guides/customer-360/idsync/","order":7,"label":null}],"metadataParent":{"title":"Guides","path":"/guides/","metadataChildren":[{"title":"Platform Overview","path":"/guides/platform-overview/","order":0.5,"label":null},{"title":"Getting Started","path":"/guides/getting-started/","order":1,"label":null},{"title":"mParticle Agent","path":"/guides/mparticle-agent/","order":1.5,"label":null},{"title":"Oversight","path":"/guides/oversight/","order":2,"label":null},{"title":"Data Platform","path":"/guides/data-platform/","order":3,"label":null},{"title":"Data Warehouse","path":"/guides/data-warehouse/","order":4,"label":null},{"title":"Customer 360","path":"/guides/customer-360/","order":5,"label":null},{"title":"Analytics","path":"/guides/analytics/","order":6,"label":null},{"title":"Audiences","path":"/guides/audiences/","order":7,"label":null},{"title":"Settings","path":"/guides/settings/","order":8,"label":null},{"title":"Troubleshooting mParticle","path":"/guides/troubleshooting/","order":10,"label":null},{"title":"Default Service Limits","path":"/guides/default-service-limits/","order":11,"label":null},{"title":"Glossary","path":"/guides/glossary/","order":12,"label":null}],"metadataParent":null}}}},"markdownRemark":{"html":"

mParticle is a customer data platform. This means all the data you collect with mParticle is either triggered by one of your customers (or users), or it describes one of your users.

\n

The primary purpose of IDSync is to ensure that you are attributing data to the correct user, which requires you to successfully identify the current user of your app or website. This process is often called identity resolution.

\n

\n \n \n \n \n \n \n \n Identity resolution

\n

Every piece of data collected is attributed to a user. This data attribution is stored in a user profile. Identity resolution is the process of determining which user profile incoming data should be added to. This process also includes:

\n\n

\n \n \n \n \n \n \n \n How mParticle identifies users

\n

At a high level, there are three steps in the mParticle identity resolution process:\nAn identification request is made via one of the mParticle platform SDKs or the HTTP API.

\n

\n \n \n \n \n \n \n \n 1. An identify request is made

\n

The identification request includes all available user identities, or identifiers, such as a customer ID, email address, or phone number.

\n

\n \n \n \n \n \n \n \n 2. mParticle looks for a matching user profile

\n

mParticle iterates through your account’s identity priority in ascending order, comparing the identifiers included in the request with each identifier in your identity priority.

\n

Remember, your identity priority is a list of identifiers organized according to their ability to confidently find the right profile for the user in question. For example, a customer ID or email address is more likely to be unique to a single user than a device ID, because a device ID could be shared by multiple users.

\n

\n \n \n \n \n \n \n \n 3. mParticle returns a matching profile if one is found, or it creates an anonymous profile

\n

Depending on the identity strategy configured for your account, mParticle returns the user profile matching the identifiers provided in the request.

\n

If mParticle finds an existing user profile for the user you are trying to identify, then this profile is returned to the SDK or API and the event and user data collected will be attached to this profile.

\n

If no existing profiles match the supplied identifiers (according to your identity priority), then mParticle will either create a new user profile to use, or it will do nothing. Whether or not a new profile is created (and how data is attached to that profile) is determined by your identity strategy.

\n

\n \n \n \n \n \n \n \n Example: tracking a new user through a signup flow

\n

Let’s look at an example using the profile conversion identity strategy. Remember that the profile conversion strategy is designed to create a complete record of a user’s journey through a common signup funnel.

\n

The following example is broken down into 5 basic stages, beginning with a new user navigating to an ecommerce app and ending the creation of an account while purchasing a product.

\n

\n \n \n \n \n \n \n \n 1. A new user opens your app

\n

Imagine that a new user navigates to your ecommerce app and begins to browse different products. Let’s say that the user does not have an account, nor do they create one.

\n

\n \n \n \n \n \n \n \n 2. mParticle attempts to identify the user

\n

As soon as the user opens your app, an identity request is automatically made to mParticle to look for a matching user profile.

\n

The identity priority for this example is:

\n
    \n
  1. Customer ID
    2. \n
  2. Email address
    3. \n
  3. Username
    4. \n
  4. Phone number
    5. \n
\n

Since the user hasn’t logged in or created an account yet, no customer ID, email address, or username is provided with the identification request.

\n

\n \n \n \n \n \n \n \n 3. mParticle creates an anonymous profile for the user

\n

mParticle iterates through the identity priority, but since no identifiers are provided that match any existing profiles, mParticle creates a new anonymous user profile based on the user’s device ID. Like all user profiles, this new anonymous profile is assigned a unique MPID (mParticle ID).

\n

mParticle continues to collect data about the user’s behavior and stores it in the new anonymous profile.

\n

\n \n \n \n \n \n \n \n 4. The user signs up for an account

\n

Imagine that the user picks out a product they want, they add it to their cart, and then they begin the purchase flow. Before they complete their purchase, they create an account.

\n

\n \n \n \n \n \n \n \n 5. mParticle adds the login ID to the anonymous profile, making it a known profile

\n

At this point, mParticle has finally received a login ID (the username or email address provided when the user signs up). Since the profile conversion strategy is designed to track users through the entire signup funnel (starting with anonymous browsing and ending with account creation), mParticle does not create a new user profile based on the newly supplied login ID.

\n

Instead, mParticle adds the provided login ID to the existing anonymous profile created in step 3 that was used to store the user’s browsing activity leading to the final purchase and account creation. This guarantees the creation of a complete record of the customer’s journey, providing more valuable insights into your customer’s behavior and your app’s performance.

","frontmatter":{"title":"Identify Users","order":5,"seoTitle":null,"seoDescription":null},"parent":{"__typename":"File","modifiedTime":"October 12, 2026"}}},"pageContext":{"slug":"/guides/customer-360/idsync/identify-users/"}},"staticQueryHashes":["2950460867"]}