# Overview

{% hint style="info" %}
Identity Resolution is available on Business and Enterprise plans. Reach out to your dedicated account manager to enable it in your workspace.
{% endhint %}

Identity Resolution is the DinMo identity layer for customer data. It turns fragmented records from your warehouse into resolved profiles that can be reused across Customer Hub, Segments, Activations, analytics, and downstream models.

Use this section to understand what Identity Resolution does, what is available today, and which page to read next depending on what you want to configure or inspect.

<figure><img src="/files/CkzUS4VYVdrmI9sxfB6e" alt="Identity Resolution overview showing warehouse data resolved into a unified profile and synced to destinations"><figcaption><p>Identity Resolution turns fragmented warehouse records into a unified profile that can be reused across business destinations.</p></figcaption></figure>

## At a glance

| Topic              | Details                                                                                                                                        |
| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| Main goal          | Resolve duplicate profile records into a trusted [profile spine](/identity-resolution/profile-resolution.md).                                  |
| Project model      | An [identity graph](/identity-resolution/identity-graph.md), which groups the source, models, identifiers, rules, golden fields, and schedule. |
| Primary ID         | [`dinmo_id`](/identity-resolution/dinmo-id.md), the resolved profile ID assigned by DinMo.                                                     |
| Main output        | [`identity_golden`](/identity-resolution/golden-record.md), one row per resolved profile.                                                      |
| Best first users   | Data teams configuring source models and marketers consuming resolved profiles.                                                                |
| Required inputs    | Profile-like source models with stable keys and useful identifiers.                                                                            |
| Optional extension | Event Stitching, used to attach event records to known profiles.                                                                               |

## Available capabilities

**Identity Resolution** is split in focused layers so the product stays explainable and reliable.

| Layer                                                            | What it covers                                                                         |
| ---------------------------------------------------------------- | -------------------------------------------------------------------------------------- |
| [Profile Resolution](/identity-resolution/profile-resolution.md) | Deduplicate profile-like records, assign `dinmo_id`, and create a golden record table. |
| [Event Stitching](/identity-resolution/event-stitching.md)       | Attach events to already resolved profiles when the event carries a known identifier.  |

## What Identity Resolution does

Identity Resolution links records that refer to the same real-world entity, such as a person, company, or household.

For example, the same person may appear as:

* a CRM contact
* an e-commerce customer
* an app user
* a support contact
* an anonymous visitor who later logs in

DinMo uses configured [identifiers and matching rules](/identity-resolution/matching-rules.md) to decide which records belong together. The result is a resolved profile represented by `dinmo_id`.

## How the flow works

<figure><img src="/files/SMMpq0f09FnToCJDiKge" alt="Identity Resolution five-step flow from source models to identifiers, profile resolution, golden record, and event stitching"><figcaption><p>The Identity Resolution workflow connects sources, maps identifiers, resolves profiles, builds the golden record, and stitches behavior.</p></figcaption></figure>

The usual workflow is:

1. **Prepare profile models**\
   Select the source models that contain customer, user, subscriber, account, or contact records.
2. **Map identifiers**\
   Tell DinMo where to find values such as email, phone, user ID, customer ID, anonymous ID, or device ID.
3. **Define matching rules**\
   Configure how identifiers, rules, and criteria should be used to connect records.
4. **Create the golden record**\
   Choose which fields appear in the golden record table and how winning values should be selected with [survivorship rules](/identity-resolution/survivorship-rules.md).
5. **Review quality and coverage**\
   Inspect match rates, unresolved records, rule contribution, identifier quality, and suspicious clusters in [Review and monitor](/identity-resolution/review-and-monitor.md).
6. **Attach events when ready**\
   Use Event Stitching to connect purchases, sessions, support events, or product usage to the resolved profile spine.

## What Identity Resolution produces?

When Profile Resolution runs, DinMo produces:

* `identity_golden`, the canonical golden record table
* `identity_matched_ids`, the identifier footprint for each resolved profile
* `identity_unresolved_records`, records excluded from the final profiles
* `identity_lookup` and `match_pairs`, audit tables that explain matching behavior
* run metrics that help monitor identity quality over time

When Event Stitching is enabled, DinMo also produces:

* event-to-profile links
* attribution status for each event
* unstitched-event reporting for events that could not be attached

See [Output tables](/identity-resolution/output-tables.md) for the full table reference.

## What to read next

| If you want to...                                      | Read                                                                                |
| ------------------------------------------------------ | ----------------------------------------------------------------------------------- |
| Create your first profile spine                        | [Create your first Profile Resolution project](/identity-resolution/get-started.md) |
| Understand Profile Resolution                          | [Profile Resolution](/identity-resolution/profile-resolution.md)                    |
| Understand customer deduplication                      | [How customer deduplication works](/identity-resolution/customer-deduplication.md)  |
| Understand the project-level identity graph            | [Identity graph](/identity-resolution/identity-graph.md)                            |
| Configure identifiers, rules, criteria, and guardrails | [Matching rules](/identity-resolution/matching-rules.md)                            |
| Configure fuzzy match logic                            | [Fuzzy matching](/identity-resolution/fuzzy-matching.md)                            |
| Understand the canonical profile output                | [Golden record](/identity-resolution/golden-record.md)                              |
| Choose winning field values                            | [Survivorship rules](/identity-resolution/survivorship-rules.md)                    |
| Understand the resolved profile ID                     | [`dinmo_id`](/identity-resolution/dinmo-id.md)                                      |
| Understand the matching mechanics                      | [How Identity Resolution works](/identity-resolution/how-it-works.md)               |
| Validate runs and monitor quality                      | [Review and monitor](/identity-resolution/review-and-monitor.md)                    |
| Attach events to resolved profiles                     | [Event Stitching](/identity-resolution/event-stitching.md)                          |
| Query the warehouse outputs                            | [Output tables](/identity-resolution/output-tables.md)                              |

## Current boundaries

Identity Resolution works best when the first project stays narrow and high confidence.

Current recommended scope:

* resolve profile-like records first
* start with high-quality identifiers
* keep the golden record focused on fields that are useful downstream
* validate unresolved records and sample clusters before activation
* enable Event Stitching after the profile spine is trusted

Not every related table should participate in Profile Resolution. Transactions, invoices, page views, support tickets, and product usage records are better handled through Event Stitching or later attribution capabilities.

## Core concepts

| Concept           | Meaning                                                                                                                                         |
| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| `dinmo_id`        | The resolved profile ID assigned by DinMo.                                                                                                      |
| Identity graph    | The project-level configuration that defines source models, identifiers, matching rules, golden fields, outputs, and schedule.                  |
| Identifier        | A value used to connect records and build rules, such as email, phone, user ID, account ID, anonymous ID, or device ID.                         |
| Criterion         | One condition inside a matching rule. A criterion selects one or more identifiers and a match type, such as exact email or fuzzy name matching. |
| Matching rule     | A configured rule that defines which identifiers must match for records to be linked.                                                           |
| Golden record     | The canonical one-row-per-`dinmo_id` profile generated after records have been resolved.                                                        |
| Survivorship rule | The logic used to choose the winning value for each golden record field.                                                                        |
| Unresolved record | A record excluded from the final golden record because it lacks usable data or violates a conflict rule.                                        |
| Event Stitching   | The process of attaching events to existing resolved profiles.                                                                                  |

***

## Ready to get started?

Book a demo and we will walk through the best way to launch your first DinMo use case.

[Book a demo](https://www.dinmo.com/contact/)

## Need help?

Our team is here to help with setup, modeling, activation, and troubleshooting.

[Contact us](mailto:hello@dinmo.com?subject=Docs%20help)

## Feature requests?

Tell us which connector, workflow, or improvement would make DinMo more useful for your team.

[Request a feature](mailto:hello@dinmo.com?subject=Feature%20request)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.dinmo.io/identity-resolution/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.