Output tables

When Event Stitching is enabled, DinMo exposes event profile outputs in the connected source, typically in the dinmo_identity dataset or schema.

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

Tables

Table	What it contains	Main use
identity_event_profiles	Current and merged event profiles.	Inspect the event profile graph.
identity_event_profile_attribution	Processed events with their assigned dinmo_stitched_profile_id and attribution status.	Join events to event profiles.
identity_event_profile_identifier_values	Identifier values observed on each event profile.	Audit which identifiers explain a profile.
identity_event_profile_audit_events	Profile creation, merge, identifier, and exclusion events.	Explain graph changes across runs.
identity_event_profile_redirects	Event profile redirects after merges.	Resolve older event profile IDs to the current profile.
identity_event_profile_run_metrics	Warehouse-native summary metrics per run, scoped by project, source, identifier, exclusion reason, or audit event type.	Power UI and API summary reporting without scanning the full event history.

identity_event_profiles

Use identity_event_profiles to inspect the current state of the event profile graph.

Important columns include:

Column	Description
dinmo_stitched_profile_id	Event profile key produced by Event Stitching.
created_sequence	Monotonic sequence assigned when the event profile was created.
created_at	Timestamp used when the event profile was first created.
first_seen_at	Earliest event timestamp on the event profile.
last_seen_at	Latest event timestamp on the event profile.
status	Event profile lifecycle status. Values include active, merged, and inactive_lost_active.
merged_to_dinmo_stitched_profile_id	Surviving event profile when this profile was merged.
resolved_dinmo_stitched_profile_id	Current event profile to use for downstream joins.

identity_event_profile_attribution

Use identity_event_profile_attribution to attach processed events to event profiles.

Important columns include:

Column	Description
source_model_id	Event source model.
event_key_value	Event primary key value.
event_timestamp	Timestamp of the event.
dinmo_stitched_profile_id	Event profile assigned to the event.
resolved_dinmo_stitched_profile_id	Current event profile after redirects. Use this column for downstream joins.
attribution_status	Whether the event was stitched or excluded.
run_id	Run that processed the event.
reason	Explanation when the event was excluded or handled by a guardrail.

Common attribution_status values:

Value	Meaning
stitched	The event was attached to an event profile.
excluded	The event was processed but not attached to an event profile. Check reason for the cause.

Common reason values:

Value	Meaning
no_matchable_identifier	The event did not contain a usable identifier value after standardization, blocking, and stitching lifetime checks.
conflicted_identifier_value	The event depended on an identifier value quarantined because it connected too many profiles.
limit_conflict	The event could not be stitched without violating a configured identifier policy.

identity_event_profile_identifier_values

Use identity_event_profile_identifier_values to understand which identifiers belong to each event profile.

Important columns include:

Column	Description
dinmo_stitched_profile_id	Event profile that currently owns the identifier value.
identifier_name	Configured identifier name.
identifier_value	Standardized identifier value.
identifier_status	Whether the value is active, blocked, expired, or demoted. See values below.
first_seen_at	First event-time observation for the identifier value.
last_seen_at	Latest event-time observation for the identifier value.
active_from	Start of the identifier matching window.
active_until	End of the identifier matching window, when configured.
priority	Identifier priority used by the matching policy.
status_reason	Reason the identifier is active or inactive.
resolved_dinmo_stitched_profile_id	Current event profile after redirects.

Common identifier_status values:

Value	Meaning
active	The identifier value is currently active for matching on this event profile.
inactive_expired	The identifier value has fallen out of its configured stitching lifetime and no longer creates new matches.
inactive_demoted	The identifier value was kept as evidence but removed from active matching by a protection, such as a conflict guardrail or active-value capacity limit.
blocked	The identifier value is on the configured blocked_values list and is ignored for matching.

identity_event_profile_run_metrics

Use identity_event_profile_run_metrics to power UI and API summary reporting without scanning the full event history. The table is built in the warehouse after durable Event Stitching state and outputs are published for a run, and is append-style per run.

Important columns include:

Column	Description
run_id	Run that produced the metric.
metric_scope	Grouping dimension for the metric row. See values below.
metric_scope_value	Stable grouping key for the row.
source_model_id	Populated when metric_scope = source.
identifier_name	Populated when metric_scope = identifier.
attribution_status	Reserved for attribution-status scoped metrics. Empty in the standard public metric rows.
identifier_status	Reserved for identifier-status scoped metrics. Empty in the standard public metric rows.
audit_event_type	Populated when metric_scope = audit_event_type.
metric_name	Name of the aggregated metric.
metric_value_numeric	Numeric value of the metric.
metric_unit	Unit of the metric.
recorded_at	Timestamp when the metric row was produced.

Common metric_scope values:

Value	Meaning
project	One metric row per project, e.g. total stitched events.
source	One metric row per source_model_id.
identifier	One metric row per identifier_name.
exclusion_reason	One metric row per exclusion reason.
audit_event_type	One metric row per audit event type.

This table intentionally exposes aggregated counts and rates, not raw event keys or raw identifier values.