Identity resolution

The problem

Your users don't always look the same to your software.

Someone visits your site before signing up. They browse, maybe see a survey. Then they create an account. Then they log in on their phone. From your app's point of view, that could look like three different people. From theirs, it's obviously one.

If you're collecting feedback, this matters. Targeting, segmentation, and response history all depend on knowing who you're talking to — even when the same person shows up at different times, on different devices, before and after they've signed in.

How getuserfeedback.com solves it

Every event that flows through getuserfeedback.com — every survey view, every response, every time you tell us who the user is — goes through identity resolution. It powers targeting, personalization, and segmentation across the entire platform.

You tell us who the user is

When a user logs in, signs up, or provides their info, your app passes identifiers to getuserfeedback.com — a user ID, an email, a phone number, or any combination. You don't have to send everything at once. Send what you have.

We connect the dots

When new identifiers come in, getuserfeedback.com checks whether any of them already belong to an existing user profile. If they do, the new activity is linked to that profile. If multiple profiles match, they're merged into one.

The match is deterministic — we only use the first-party identifiers you explicitly send. No guessing, no fingerprinting, no third-party data.

Profiles grow over time

Each interaction can add new identifiers. A user might start with just a session, then add an email when they sign up, then a user ID when they log in. All of these get linked to a single profile.

A concrete example

Jane visits your app for the first time. She hasn't signed in — she's just browsing. The widget tracks her session.

She sees a survey and submits a response.

Later, she signs up with her email. Your app tells getuserfeedback.com who she is. Now her earlier session — including that response — is linked to her profile.

A week later, Jane logs in on her phone. Different device, different session, but the same user ID. Her phone activity is linked to the same profile. One person, one profile, every device.

What this means for you

• Targeting works across the login boundary. A rule like "show this survey to Pro users who haven't responded yet" works correctly — even if the user first saw your app before signing in.
• Response history stays complete. You won't accidentally re-survey someone because their responses were split across sessions.
• Segmentation reflects the full picture. Behavioral segments include activity from every session and every device.

Reversible by design

Made a mistake in how your integration maps identifiers? Maybe a field was mapped incorrectly and unrelated users got merged. No problem — remove the integration and the impact is fully undone. Profiles are restored like it never happened.

This is rare in the industry. Most identity systems treat merges as permanent. In getuserfeedback.com, bad data doesn't permanently corrupt your user profiles.

How it's different

Most tools that offer identity resolution treat it as an add-on for specific features. In getuserfeedback.com, it runs on every incoming event. It's the foundation — not a premium tier, not an optional module.

The approach is 100% deterministic and uses only first-party data you send. The identifier mapping is configurable, custom IDs are supported, and the whole thing is reversible.

Learn more

For the exact mechanics — supported identifier types, priority order, merge behavior, and configuration options — see the identity resolution docs.