Overview
Last updated:2024-11-27

Overview

A user refers to the end-user initiating a conversation with the Bot. GPTBots supports developers in setting unique identity IDs for different users. Through this user ID (UserId), user identity can be associated across different channels, enabling cross-channel user identity merging, business queries via Tools, maintenance of user attributes, chat records, and more.

Definitions

User:
A user refers to the end-user initiating a conversation with the Bot.
Anonymous ID:
When a user initiates a conversation with the Bot on a non-API channel platform, the system generates an Anonymous ID containing the information of the channel platform where the user is located.
UserId:
A unique identity ID for users, customized by enterprise developers. Developers assign a UserId to an Anonymous ID. The level of UserId is higher than Anonymous ID, and multiple Anonymous IDs can belong to a single UserId. For usage scenarios and advanced applications of UserId, refer to Set User ID.
Conversation ID:
The Conversation ID (conversationID) is used to identify a single conversation between an Anonymous ID and the Bot. The automatic expiration time for conversationID is 60 minutes, after which a new conversationID is generated to identify another conversation between the Anonymous ID and the Bot.

When developers initiate a conversation using the conversationID via API, the expiration logic for conversationID does not apply.

Generation Principle of Conversation ID

The GPTBots platform currently supports numerous third-party channel platforms (intercom, webchat, livechat, telegram, WhatsApp, etc.) and self-built channels (Bubble Widget, iframe, API, etc.).
When an end-user initiates a conversation with the Bot through these channel platforms, the system generates an Anonymous ID containing the information of the channel platform where the user is located. Based on the Anonymous ID, a conversationID is generated. The conversationID is used to identify a single conversation between the Anonymous ID and the Bot. The automatic expiration time for conversationID is 60 minutes, after which a new conversationID is generated to identify another conversation between the Anonymous ID and the Bot. user-management

  • When developers use the API, they must generate the conversationID themselves and pass the conversationID parameter to initiate a conversation with the Bot.
  • For non-API channels, GPTBots automatically generates the conversationID. The specific business process for generation is as follows: