> For the complete documentation index, see [llms.txt](https://docs.dinmo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dinmo.io/identity-resolution/overview.md).

# 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 helps you turn fragmented warehouse records and event streams into trusted profile and journey outputs that can be reused across Customer Hub, Segments, Activations, analytics, and downstream models.

For the business background on why identity resolution matters, see DinMo's guide to the [identity graph](https://www.dinmo.com/cdp/customer-data/identity-resolution/identity-graph/) and the [single customer view](https://www.dinmo.com/cdp/customer-data/single-customer-view-scv/).

<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 data into reusable profile and journey outputs.</p></figcaption></figure>

## Capabilities

DinMo Identity Resolution has two independent capabilities. Choose based on the grain of the data you want to resolve.

| Capability                                                       | Use it when you need                                                    | Main ID                     | Main output               |
| ---------------------------------------------------------------- | ----------------------------------------------------------------------- | --------------------------- | ------------------------- |
| [Profile Resolution](/identity-resolution/profile-resolution.md) | A trusted one-row-per-customer profile spine from profile-like records. | `dinmo_id`                  | `identity_golden`         |
| [Event Stitching](/identity-resolution/event-stitching.md)       | A behavioral journey graph across anonymous and known events.           | `dinmo_stitched_profile_id` | Event profile attribution |

You can use one capability without the other. When you use both, they stay independent and can be joined in your warehouse on identifiers you trust.

## Workflow paths

Profile Resolution and Event Stitching follow separate workflows with independent outputs.

<figure><img src="/files/OzI3H29qPpKXImrRRhVo" alt="Identity Resolution workflow paths for Profile Resolution and Event Stitching"><figcaption><p>Profile Resolution creates the customer profile spine. Event Stitching creates event profile attribution for behavioral journeys.</p></figcaption></figure>

## Where to start

| Your first question                                                 | Start with                                                               |
| ------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| Which customer records describe the same person?                    | [Profile Resolution](/identity-resolution/profile-resolution.md)         |
| How do I create a clean customer table for activation or analytics? | [Profile Resolution](/identity-resolution/profile-resolution.md)         |
| Which events belong to the same behavioral journey?                 | [Event Stitching](/identity-resolution/event-stitching.md)               |
| How do anonymous events connect to known activity after login?      | [Event Stitching](/identity-resolution/event-stitching.md)               |
| I am not sure which one fits my use case.                           | [Choose your project type](/identity-resolution/choose-your-approach.md) |

## How the pieces relate

The main difference is the input grain:

* **Profile Resolution** resolves profile-like records such as customers, contacts, accounts, subscribers, or app users.
* **Event Stitching** stitches event-like records such as purchases, page views, sessions, app events, support interactions, or product usage events.

Profile Resolution creates `dinmo_id`. Event Stitching creates `dinmo_stitched_profile_id`. These IDs are separate by design because a customer master profile and a behavioral event journey have different lifecycles.

For the shared vocabulary, see [Identity Resolution concepts](/identity-resolution/concepts.md).

## Next steps

| If you want to...                           | Read                                                                                                           |
| ------------------------------------------- | -------------------------------------------------------------------------------------------------------------- |
| Compare the two capabilities                | [Choose your project type](/identity-resolution/choose-your-approach.md)                                       |
| Build your first Profile Resolution project | [Create your first Profile Resolution project](/identity-resolution/profile-resolution/get-started.md)         |
| Configure Profile Resolution matching       | [Matching rules](/identity-resolution/profile-resolution/matching-rules.md)                                    |
| Review Profile Resolution outputs           | [Output tables](/identity-resolution/profile-resolution/output-tables.md)                                      |
| Prepare event data                          | [Prepare event data for Event Stitching](/identity-resolution/event-stitching/event-stitching-prepare-data.md) |
| Create an Event Stitching project           | [Create an Event Stitching project](/identity-resolution/event-stitching/event-stitching-create-project.md)    |
| Understand Event Stitching behavior         | [How Event Stitching works](/identity-resolution/event-stitching/event-stitching-how-it-works.md)              |
| Review Event Stitching outputs              | [Event Stitching output tables](/identity-resolution/event-stitching/event-stitching-output-tables.md)         |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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.