FAQ about Identity Resolution Management

Prev Next

What is the anonymous or unknown user?

A user is unknown when they have not provided any login details or are browsing as a guest.

What is the registered or known user?

A user is known or registered when they have provided PII data like an Email address, phone number, or UserID to sign up or log in. A registered user must be assigned a unique identifier. The identifier can be set differently depending on the platform and integration methods.

Which identifiers should I use?

It is based on your business requirements. Insider is flexible on the usage of the identifiers.

I have set the email limit to 2, but I do not see both values under User Profiles. What is the reason?

User Profiles show user attributes and events. Attributes are the latest values so that you will see the most recent values of related identifiers, not both.

I want to change the priorities, limits, or blocked values I set. How should I proceed?

Since it involves highly critical settings, Insider will be available throughout the process to help avoid mistakes. Contact the Insider One team with your inquiries.

Which blocked values should I use to avoid any faulty merging?

Based on previous experiences, values such as “undefined,” “anonymous,” “0”, “1”, and “null” should be blocked to avoid unwanted merging scenarios.

How does Insider prevent duplicate users from being created?

If an attribute in the IRM is added as an identifier, it is written to the profile only from the identity flow, which prevents the creation of duplicate users.

If you make changes to the settings, the identity associations of existing users will not be affected.

How does Insider use identifiers to unify user profiles across online and offline touchpoints?

Insider uses identifiers, such as email, phone number, or UUID, to recognize and merge user interactions across different channels into a single, unified customer profile. When a user interacts anonymously (for example, by browsing a website), Insider creates an anonymous profile for them. Once the user provides an identifier, such as an email address, Insider matches it against existing records in the Unified Customer Database (UCD). If a match is found, the data is merged into that profile; if not, a new profile is created.

You can also refer to the video below to better understand how Insider uses identifiers to unify user profiles across online and offline channels:

How does Insider handle user profiles when the priority one identifier is missing?

When a priority one identifier isn’t provided, Insider uses lower-priority identifiers to match incoming requests to existing profiles. If a match is found, Insider either completes the existing profile with the missing identifier, updates it with new information, or merges multiple matching profiles, provided the combined identifiers stay within allowed limits. This ensures user profiles remain accurate and unified even without the top-priority identifier.

You can also refer to the video below to better understand how Insider handles user profiles when priority one identifiers are missing, including completing existing profiles, updating profiles without top-priority identifiers, and merging multiple profiles within identifier limits:

What should I consider when selecting and setting up identifiers, and what best practices should I follow?

Choose identifiers that are consistent, unique, and aligned with your business needs. Start with default identifiers like email, phone number, and UUID, and add custom ones only when necessary. Avoid generic or placeholder values, as they can cause incorrect merges. Leave fields blank for anonymous users instead of using placeholders. Test your setup thoroughly across all scenarios before going live, plan your identifier strategy carefully, and consult Insider’s experts when needed. Doing this ensures accurate profiles, better personalization, and more effective marketing.

You can refer to the video below to better understand how to select and set up identifiers effectively, follow best practices, and ensure they support accurate user recognition across platforms.