# Output tables

Identity Resolution writes output tables to the connected source, typically in the `dinmo_identity` dataset or schema. These outputs are generated by an [identity graph](/identity-resolution/identity-graph.md) and should be reviewed alongside the UI metrics in [Review and monitor](/identity-resolution/review-and-monitor.md).

Physical table names may include the project ID. The examples below use the logical table names for readability.

## Profile Resolution outputs

| Table                         | What it contains                                                                                                                  | Main use                                                 |
| ----------------------------- | --------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------- |
| `identity_golden`             | One canonical [golden record](/identity-resolution/golden-record.md) per resolved [`dinmo_id`](/identity-resolution/dinmo-id.md). | Use as the unified profile table.                        |
| `identity_matched_ids`        | Identifier values linked to each resolved profile.                                                                                | Inspect the identity footprint of a profile.             |
| `identity_unresolved_records` | Records excluded from final outputs.                                                                                              | Investigate data quality issues and conflict guardrails. |
| `identity_lookup`             | Standardized source identifiers and rule keys.                                                                                    | Debug what entered the matching graph.                   |
| `match_pairs`                 | Pairwise explanation of records that matched.                                                                                     | Audit why two records were linked.                       |
| `identity_golden_report`      | Compact run summary.                                                                                                              | Review high-level metrics.                               |

## Event Stitching outputs

When [Event Stitching](/identity-resolution/event-stitching.md) is enabled, DinMo exposes event-to-profile outputs.

| Table                                | What it contains                                                                  | Main use                                       |
| ------------------------------------ | --------------------------------------------------------------------------------- | ---------------------------------------------- |
| `identity_event_profile_attribution` | Event-to-`dinmo_id` links with attribution status and matched identifier details. | Join events to resolved profiles.              |
| `identity_unstitched_events`         | Events that could not be safely attached.                                         | Improve identifier coverage and configuration. |
| `identity_event_stitching_metrics`   | Event coverage metrics by source, status, and identifier.                         | Monitor stitching quality over time.           |

## identity\_golden <a href="#identity_golden" id="identity_golden"></a>

`identity_golden` is the main table for consuming golden records.

Important columns include:

| Column                            | Description                                                                                             |
| --------------------------------- | ------------------------------------------------------------------------------------------------------- |
| `dinmo_id`                        | Resolved profile ID.                                                                                    |
| `representative_entity_key_name`  | Source key name of the representative source record.                                                    |
| `representative_entity_key_value` | Source key value of the representative source record.                                                   |
| `resolution_status`               | Whether the emitted profile is matched or unique.                                                       |
| `updated_at`                      | Latest known update timestamp for the resolved profile.                                                 |
| identifier columns                | Configured identifiers exposed in the golden record.                                                    |
| golden fields                     | Configured profile fields selected by [survivorship rules](/identity-resolution/survivorship-rules.md). |

## identity\_unresolved\_records

Use `identity_unresolved_records` to understand records that were excluded from the final profile output. These records often point back to missing identifiers, duplicate primary keys, or [matching rule](/identity-resolution/matching-rules.md) guardrails.

Common unresolved reasons include:

| Reason                | Meaning                                                                   |
| --------------------- | ------------------------------------------------------------------------- |
| `missing_data`        | The record does not contain enough usable identifier data to be resolved. |
| `identifier_conflict` | The matched profile violated an identifier guardrail.                     |

## identity\_event\_profile\_attribution

This table attaches events to resolved profiles.

Recommended columns include:

| Column                     | Description                                                         |
| -------------------------- | ------------------------------------------------------------------- |
| `dinmo_id`                 | Resolved profile ID attached to the event.                          |
| `event_source_model_id`    | Source model that produced the event.                               |
| `event_key_name`           | Event primary key name.                                             |
| `event_key_value`          | Event primary key value.                                            |
| `event_timestamp`          | Timestamp of the event.                                             |
| `attribution_status`       | Whether the event was stitched, unstitched, ambiguous, or excluded. |
| `matched_identifier_name`  | Identifier used to attach the event, when available.                |
| `matched_identifier_value` | Identifier value used to attach the event, when available.          |

## Which output should you use?

| Need                                             | Recommended output                                                  |
| ------------------------------------------------ | ------------------------------------------------------------------- |
| Use one row per resolved customer                | `identity_golden`                                                   |
| Understand which identifiers belong to a profile | `identity_matched_ids`                                              |
| Investigate unresolved records                   | `identity_unresolved_records`                                       |
| Explain why records matched                      | `match_pairs` and `identity_lookup`                                 |
| Join events to profiles                          | `identity_event_profile_attribution` filtered to stitched events    |
| Monitor Event Stitching coverage                 | `identity_event_stitching_metrics` and `identity_unstitched_events` |


---

# 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/output-tables.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.