Profile Resolution

Profile Resolution is the first layer of Identity Resolution. It deduplicates profile-like records, assigns a stable resolved profile key, and creates a canonical profile spine that can be reused across DinMo.

The output of Profile Resolution is centered on dinmo_id, the resolved profile ID.

Profile Resolution flow from profile source models to identifiers, matching graph, golden record, and activation
Profile Resolution turns duplicate profile records into a golden record keyed by dinmo_id.

What Profile Resolution does

Profile Resolution:

  • reads profile-like source models, such as CRM contacts, ecommerce customers, app users, subscribers, or support contacts

  • standardizes configured identifiers and matching rules

  • groups records that refer to the same real-world customer or entity

  • creates a golden record with one row per dinmo_id

For a step-by-step setup guide, see Create your first Profile Resolution project.

What Profile Resolution does not do

Profile Resolution does not resolve every warehouse table. Event, transaction, session, support ticket, and product usage tables should usually be modeled separately through Event Stitching or another attribution layer.

It also does not replace data modeling. Source models still need stable primary keys, useful identifiers, and fields that can support review and downstream use.

Main outputs

Output
Use it for

identity_golden

Consume one row per resolved profile.

identity_matched_ids

Inspect which identifiers belong to each resolved profile.

identity_unresolved_records

Investigate records excluded by missing data or guardrails.

identity_lookup and match_pairs

Audit how records entered and matched in the graph.

See Output tables for the full table reference and Review and monitor for validation guidance.

When to use Profile Resolution

Use Profile Resolution when you need to:

  • deduplicate customer or user records

  • create a trusted profile spine for Customer Hub, Segments, Activations, analytics, or downstream models

  • build a golden record from multiple source systems

  • make identity decisions explainable through rules, audit tables, and monitoring

For the deduplication mechanics, see How customer deduplication works.

Last updated