Skip to main content

User-Scoped Conversations

Providing User IDs​

The user_id must be included in the message payload metadata sent from your frontend to Rasa's input channel:

{
  "sender": "conversation_12345",
  "message": "Hello",
  "metadata": {
    "user_id": "usr_a1b2c3d4e5f6"
  }
}

Important Security Note: For data protection, user_id should be a random, non-sensitive identifier (such as a UUID). Do not use personally identifiable information like email addresses, phone numbers, or names, as user_id values may appear in logs.

The user_id is persisted in all supported tracker stores (InMemory, SQL, Redis, Mongo and Dynamo). If user_id is null, it is omitted from the serialized tracker JSON.

The tracker's current state also includes user_id:

{
  "sender_id": "conversation_12345",
  "user_id": "usr_a1b2c3d4e5f6",
  "current_session_id": "4b3c1e2a-91f0-4d8e-b123-abc123def456",
  "events": [...]
}

user_id in event broker payloads​

Every event streamed to an event broker now includes user_id alongside sender_id:

{
  "sender_id": "conversation_12345",
  "user_id": "usr_a1b2c3d4e5f6",
  "event": "user",
  "text": "Hello"
}

This allows downstream consumers (analytics pipelines, data warehouses, CRMs) to group events by user without additional joins.

Retrieving Conversations by User​

Once user_id is set, you can retrieve all conversations for that user via the tracker API endpoint(GET /users/{user_id}/trackers). The endpoint returns serialized tracker data — including events — read directly from storage without replaying conversation history through DialogueStateTracker. Call it on the server-side and expose only what the client needs. This powers use cases like conversation history lists, support dashboards, and "resume a past session" flows.

current_session_id in responses

The current_session_id field in each returned tracker is derived from the metadata of the last stored event. It is null when the last event is ConversationInactive, correctly reflecting that no active session exists at the time of the request.

Backward Compatibility​

To support user-scoped tracker querying, you must implement the get_trackers_by_user_id() method in your custom tracker store. This method enables efficient retrieval of all conversations for a specific user with pagination and ordering support. More details can be found in the Rasa Pro Migration Guide.

Last updated on