Manage Variables
Manage Variables
Overview
Variables in Journey Builder store and manage data dynamically within conversational journeys, enabling personalization, data manipulation, and efficient bot interactions.
Variables are categorized into five types:
- Local
- Global
- System
- Constant
- CDP
Variable Types
1. Local Variables
- Purpose: Store session-based information. Eg. : API Responses, User inputs etc.
- Lifecycle: Persist until the conversation ID resets at the backend (typically after 72 hours from the last user message).
- Data Types: String, Number, JSON
2. Global Variables
- Purpose: Store persistent data associated with the user’s channel ID.
- Lifecycle: Persistent and does not clear automatically.
- Data Types: String, Number, JSON
3. System Variables
- Purpose: Provide read-only system-generated information.
| Variable Name | Description | Data Type |
|---|---|---|
| event_type | Type of incoming event (user_input, ctx, ai_intent, etc.) | String |
| user_input | Keyword or button click payload sent by user (e.g., "Hi", Button "Yes") | String |
| channel | Channel from which the event/message was received (e.g., WhatsApp) | String |
| user_channel_id | Channel ID from which the event/message was received (e.g., WhatsApp) | String |
| payloadString | Complex JSON object containing metadata of the event | String |
| timeStampEpoch | Timestamp in epoch format | String |
| user_name | Name of the user | String |
| conversation_context_type | Context type of the conversation | String |
| conversation_context_id | Context ID of the conversation | String |
| ai_inference_payload | JSON payload from AI Backend | JSON |
| ai_intent | Identified intent from user message | String |
| payloadJson | JSON payload from the backend | JSON |
| event_id | Unique ID for the event | String |
| message_metadata | Additional message metadata | JSON |
| conversation_language | Language used in the conversation | String |
4. Constant Variables
- Purpose: Store values consistent across all users, typically used for static information like interest rates, discounts, or event dates.
- Lifecycle: Values are editable from the variable management interface and persist across all conversations until manually updated.
5. CDP Variables
- Purpose: Fetch dynamic customer-specific attributes from the Personalize Module(also know as CDP) for real-time personalization.
- Lifecycle: Read-only and dynamically fetched from CDP, reflecting real-time updates.
How to Use
- Open Manage Variables in the Journey Builder.
- Select the appropriate variable type.
- Create or select existing variables.
- Map variables directly into nodes for data handling or personalization.
Updated 12 days ago