---
title: "Mapp Connect: Enhanced User Identifier Support"
slug: "mapp-connect-enhanced-user-identifier-support"
updated: 2024-11-25T09:30:59Z
published: 2024-11-25T09:30:59Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mapp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Mapp Connect: Enhanced User Identifier Support

**25 November 2024**: Mapp Connect has expanded its capabilities by supporting additional user identifiers for its API, improving user data management across different integrations.

## Key Benefits

- **Additional Identifiers**: Beyond `email`, Mapp Connect now supports `userID` and `mobileNumber` as unique identifiers across all user-related event types and subtypes, giving you greater flexibility in managing diverse datasets. The non-unique identifier, `externalID`, enables user tracking across external systems, enhancing integration possibilities.
- **Enhanced Event Processing**: Improved logic for identifying users through a prioritized hierarchy: `userID `is prioritized, followed by `email`, then `mobileNumber` and finally `externalID`.
- **Bulk Updates**: When using non-unique identifiers like `externalID` or custom attributes, updates apply to all users sharing that identifier, streamlining group management for campaigns and automated actions.

The feature also unlocked a new possibility to leverage custom attributes for user matching, which enables flexible targeting and user management.

## How does it work?

[2024-11 Connect Identifiers](https://player.vimeo.com/video/1032375874?badge=0&amp;autopause=0&amp;player_id=0&amp;app_id=58479)

**Processing Hierarchy**

Mapp Connect processes user events by following a prioritized identifier hierarchy:

1. **Matching Process**: When the system registers an event, it follows this sequence to find a matching user:

If the use case requires applying custom attributes, the system will prioritize matching with the specified attribute. Note that if no match is found, no fallback using unique identifiers will be applied.
  - **userID**: The system first checks for a match using the `userID`.
  - **Email**: If no `userID` match is found, it searches by email.
  - **Mobile Number**: If no email match is found, it searches by `mobileNumber`.
  - **External ID**: If no `mobileNumber` match is found, it checks for the `externalID`.
2. **Profile Creation or Update**: If no matching identifier exists, a new profile is created. Otherwise, the existing profile is updated with any new data from the event, like an added mobile number.
3. **Non-Unique Identifiers**: For events involving a non-unique identifier, updates apply to all users sharing the identifier, simplifying group actions like bulk unsubscriptions.

> To use this solution, please [create a new integration](/v1/docs/create-an-integration). It is not available in existing integrations created before this feature went live.
> 
> Also refer to our general [Mapp Connect](/v1/docs/mapp-connect-basics) online help documentation where applicable.

For use cases and further details, visit [User Identifiers in Mapp Connect](/v1/docs/user-identifiers-in-mapp-connect).

## Availability

This feature went live on November 25th, 2024, and is available by default to all Mapp Connect users.

## Related

- [User Identifiers in Mapp Connect](/user-identifiers-in-mapp-connect.md)
