Segment Integration
The Segment block enables seamless integration with Twilio's Segment, allowing you to send server-side events and trigger Segment workflows. Powered by the Segment Analytics Node.js library, this block supports event tracking on non-browser devices, ensuring compatibility across various platforms.
Use the Segment block in the Flow Editor to send events and trigger workflows in Twilio's Segment for enhanced analytics!
Finding Your Write Key
To configure the Segment block, you need your Write Key. Follow these steps to locate it:
- Log in to your Segment dashboard.
- Navigate to the Sources tab.
- Select the desired source and click the API Keys button to retrieve the
Write Key.
Ensure you have the correct Write Key from your Segment dashboard to enable event tracking.
Identify User
The Identify User action associates a user with a unique identifier in Segment. This action requires:
- User ID: A unique identifier for the user.
- Email: The user's email address.
- Traits (optional): Additional user attributes, such as name or preferences, to enrich the user profile.
Configure the Identify User action in the Flow Editor to track user details and enhance personalization.
Alias
The Alias action links a previous user identifier to a new one in Segment. It requires:
- Previous ID: The original identifier for the user.
- User ID: The new identifier to associate with the user.
Use the Alias action to merge user identities for consistent tracking across sessions.
Track Event
The Track Event action records specific user actions or events in Segment. It requires:
- Event Name: A descriptive name for the event (e.g., "Clicked Button").
- User ID: The unique identifier of the user performing the action.
- Properties (optional): Additional details about the event, such as item purchased or page visited.
Track user interactions with the Track Event action to gain insights into user behavior.
Page View
The Page View action logs page view events in Segment, useful for tracking navigation within your chatbot. It requires:
- Name: The name of the chatbot or page.
- Category (optional): A category for the page view (e.g., "Home" or "Settings").
- Properties (optional): Additional metadata about the page view, such as load time or referrer.
Use the Page View action to monitor chatbot navigation and optimize user experience.