For the complete documentation index, see llms.txt. This page is also available as Markdown.

Overview

Identity Resolution is available on Business and Enterprise plans. Reach out to your dedicated account manager to enable it in your workspace.

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 and the single customer view.

Identity Resolution overview showing warehouse data resolved into a unified profile and synced to destinations
Identity Resolution turns fragmented warehouse data into reusable profile and journey outputs.

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

A trusted one-row-per-customer profile spine from profile-like records.

dinmo_id

identity_golden

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.

Identity Resolution workflow paths for Profile Resolution and Event Stitching
Profile Resolution creates the customer profile spine. Event Stitching creates event profile attribution for behavioral journeys.

Where to start

Your first question
Start with

Which customer records describe the same person?

How do I create a clean customer table for activation or analytics?

Which events belong to the same behavioral journey?

How do anonymous events connect to known activity after login?

I am not sure which one fits my use case.

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.

Next steps

If you want to...
Read

Compare the two capabilities

Build your first Profile Resolution project

Configure Profile Resolution matching

Review Profile Resolution outputs

Create an Event Stitching project

Understand Event Stitching behavior

Review Event Stitching outputs

Last updated