> 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/dinmo-id.md). # dinmo\_id `dinmo_id` is the resolved profile ID assigned by DinMo during [Profile Resolution](/identity-resolution/profile-resolution.md). It is the primary key of the resolved profile spine and the main key used to join the [golden record](/identity-resolution/golden-record.md), matched identifiers, audit tables, and downstream profile use cases. ## Where `dinmo_id` appears `dinmo_id` appears in: * `identity_golden` * `identity_match` * `identity_matched_ids` * `identity_unresolved_records`, when relevant * Customer Hub, Segments, Activations, analytics, or downstream models that consume resolved profiles See [Output tables](/identity-resolution/profile-resolution/output-tables.md) for the full warehouse reference. [Event Stitching](/identity-resolution/event-stitching.md) produces `dinmo_stitched_profile_id`, not `dinmo_id`. ## How `dinmo_id` is created DinMo creates `dinmo_id` by applying [matching rules](/identity-resolution/profile-resolution/matching-rules.md) inside an [identity graph](/identity-resolution/identity-graph.md). Records that match according to the configured rules are grouped into one resolved profile and receive the same `dinmo_id`. ## ID continuity `dinmo_id` is designed to remain stable across normal runs. In most cases, existing resolved profiles keep the same `dinmo_id` as new source records are added or updated. A `dinmo_id` may change only when the resolved identity graph itself changes, for example when two previously separate profiles are merged after new matching evidence appears, or when matching rules or source data are materially changed. Downstream systems should treat `dinmo_id` as the current resolved profile key and use [Review and monitor](/identity-resolution/profile-resolution/review-and-monitor.md) to track identity changes over time. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.dinmo.io/identity-resolution/dinmo-id.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.