Best Match Strategy

Unique IDs Login IDs On New Known User On Logout
None None N.A. N.A.

Use Cases

The Best Match strategy does not apply any special business logic. It suits device-centric business models that do not rely on uniquely identifying users. Four general use cases are suited to the Best Match strategy.

  • Brands that do not support login behavior.
  • Brands that do support login but always assign a primary unique ID to users on first contact.
  • Brands that provide their apps core features to users without requiring them to create an account.
  • Brands that require users to create an account before the app can be used at all.

Requests

Since the Best Match strategy does not support Login IDs, there are no login or logout requests, only identify, for identifying a user based on your configured Identity Priority and the information in the request, and modify for altering an identity for a given MPID.

Identity Flow

Example Identity Priority:

  1. Email Address
  2. IDFV
  3. Android ID
Scenario Initial Profile Request New Profile
First App Launch
User launches the app and the mParticle SDK
none Identify
IDFV: 9876
Profile 1
mParticle ID: 1234
IDFV: 9876
Add additional ID
User provides email address.
Profile 1
mParticle ID: 1234
IDFV: 9876
Identify
Email: ed.hyde@example.com
IDFV: 9876
Profile 1
mParticle ID: 1234
IDFV: 9876
Email: ed.hyde@example.com
User Updates Email
User changes their email address
Profile 1
mParticle ID: 1234
IDFV: 9876
Email: ed.hyde@example.com
Modify
mParticle ID: 1234
Identity Type: email
Old Value: ed.hyde@example.com
New Value: h.jekyll.md@example.com
Profile 1
mParticle ID: 1234
IDFV: 9876
Email: h.jekyll.md@example.com
Shared Device: Second User
A new user provides an email on the same device.
Profile 1
mParticle ID: 1234
IDFV: 9876
Email: h.jekyll.md@example.com
Identify
Email: poole@example.com
IDFV: 9876
Profile 1
mParticle ID: 1234
IDFV: 9876
Email: h.jekyll.md@example.com
Email: poole@example.com

Since the Best Match strategy doesn’t enforce uniqueness of IDs, this profile now has 2 email lookups.
Second User: New Device Initialize none Identify
Android ID: 8765
Profile 2
mParticle ID: 2345
Android ID: 8765
Second User: New Device Provide Email Profile 2
mParticle ID: 2345
Android ID: 8765
Identify
Android ID: 8765
Email: poole@example.com
Profile 1
mParticle ID: 1234
IDFV: 9876
Android ID: 8765
Email: h.jekyll.md@example.com
Email: poole@example.com

Now that we have the email, it’s higher rank in the Identity Priority means we’re back to profile 1. A new Android ID lookup has been added for profile 1.

Was this page helpful?