# Event Stitching
Event Stitching attaches event records to known profiles resolved by an [identity graph](/identity-resolution/identity-graph.md).
It lets you analyze behavior, build segments, and activate audiences using the same [`dinmo_id`](/identity-resolution/dinmo-id.md) profile spine.
Event Stitching uses identifiers on each event to attach behavior to the existing resolved profile spine.
## What Event Stitching does
Event Stitching answers:
* which `dinmo_id` does this event belong to?
* which event identifier created the link?
* which events could not be attached?
* how complete is event coverage by source?
## What Event Stitching does not do
Event Stitching does not:
* create new profiles
* merge existing profiles
* make event tables participate in Profile Resolution
* resolve arbitrary multi-hop warehouse relationships
[Profile Resolution](/identity-resolution/profile-resolution.md) creates the profile spine. Event Stitching uses that spine. For the profile matching rules that create the spine, see [Matching rules](/identity-resolution/matching-rules.md).
## Event model requirements
Each event model should include:
| Requirement | Why it matters |
| ------------------- | ------------------------------------------------------------- |
| Event key | Makes each event row addressable and auditable. |
| Event timestamp | Supports recency, freshness, and downstream time windows. |
| Event identifiers | Provide values that can link the event to a resolved profile. |
| Optional event type | Helps analyze coverage by behavior. |
Common event identifiers include:
* email
* user ID
* customer ID
* anonymous ID
* device ID
## Attribution statuses
Event Stitching should make the result clear for each event.
| Status | Meaning |
| ---------- | ----------------------------------------------------------------------------------- |
| stitched | The event was attached to one known `dinmo_id`. |
| unstitched | The event could not be attached to a known profile. |
| ambiguous | The event matched more than one candidate profile and could not be safely assigned. |
| excluded | The event was excluded by configuration or policy. |
## How to use stitched events
Use stitched events to:
* build behavior-based segments on resolved profiles
* analyze purchases, sessions, support interactions, or product usage by customer
* enrich Customer Hub or downstream analytics
* activate audiences using unified profile and event context
## Validation checklist
Before relying on stitched events, review:
* stitched rate by event source
* unstitched event count
* ambiguous event count
* top unstitched reasons
* sample stitched events for each identifier type
* changes in event coverage after Profile Resolution rule changes
For ongoing validation, include Event Stitching coverage in the [Review and monitor](/identity-resolution/review-and-monitor.md#production-monitoring-checklist) checklist.
---
# 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/event-stitching.md?ask=
```
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.