Conversation Grouping

Group related requests together so logs and analytics can be viewed at the conversation level.

How It Works

Pass an X-Conversation-Id header on every request that belongs to the same conversation. The gateway attaches the ID to each log entry and uses it to combine those entries into a single conversation view in the dashboard.

X-Conversation-Id: chat_2025_04_29_alice_001

The header is optional by default. If Enforce conversation ID is on for the app, requests without it are rejected.

The gateway also accepts Conversation-Id and conversation_id as header names. See Agent Monitoring for the other correlation headers.

ID Format

Allowed characters: alphanumeric, -, _, and .. The ID is generated by your application, typically once per chat session, and reused across every turn in that session.

Enforce Conversation ID

Mode	Behavior
Enabled	Every request must include a valid X-Conversation-Id. Requests without it are rejected.
Disabled (default)	Header is read and used for grouping if present, otherwise the request is logged on its own.

Turn it on in the app's Settings > Identity Aware > Enforce conversation ID. See Identity Aware.

Conversations appear in the app's Activity > Interactions view.

Correlate full agent runs

To tie related requests to agent runs, traces, and workflows - beyond a single conversation - see Agent Monitoring.