# Real Time Observability Event Tracking

Treasure AI reserves the event column name **`td_rt_tracking_id`** for correlating an event with everything the real-time system did while processing it.

When you pass an event Universally Unique Identifier (UUID) with this column name into the real-time system, the column is written to your event table as normal and copied onto the log rows produced while processing that event. Joining on this column gives you traceability for each event ingested to Treasure AI, rather than having to correlate by timestamp and payload alone.

**Example Activation Log Table:**

![Activation log table row with the td_rt_tracking_id column populated alongside the td_c360_operation, pubname, and time columns](/assets/realtime-observability-event-tracking.502f96bfc00d0cd489884f57734e0f1e2387fc8cc219f032441091b18a7ac143.cf3845cb.png)

## Where the Tracking ID Appears

The tracking ID reaches three log surfaces, so a single value follows one event across activation, identity, and validation outcomes:

- **`activations`** — the activations triggered by the event. See [Reviewing Real Time Triggered Activation Logs](/products/customer-data-platform/real-time/reviewing-real-time-triggered-activation-logs).
- **`id_changes`** — the identity-graph changes the event caused, including profile merges and evictions at the 200-association limit.
- **`validation_failures`** — the key/value pairs on the event that failed validation and were excluded from stitching.


For the columns in the last two tables and queries that use them, see [Real Time Identity Log Tables](/products/customer-data-platform/real-time/real-time-identity-log-tables).

Attaching the tracking ID is optional. Events that do not carry the column behave exactly as before, and the column is null on the resulting log rows.