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

The identity API is used by all of mParticle’s SDKs to log users in and out of your app, to search for, and to modify a current user’s identities. It is also available as an HTTP API.

The mParticle Identity APIs surface four key operations (identify, login, logout, and modify), and in the context of UWP, all of these APIs accept an optional IdentityApiRequest object.

IDSync is the mParticle identity framework, enabling you to create a unified view of your customers, with improved data governance, policy, and security. IDSync gives visibility into, and control over, the …

The identify request should be used to establish a user identity, typically when an app is first initialized. It accepts a set of known identities and returns an mParticle ID, in accordance with an Identity Strategy.

The mParticle Identity APIs surface four key operations (identify, login, logout, and modify). In the context of the Cordova SDK, the original ‘Identify’ request should be handled in your iOS or Android …

The React Native SDK surfaces a series of APIs allowing you to manage user-identity state. These client-side APIs work in tandem with mParticle’s Identity API and your configured Identity strategy.