Overview
Add Segment to any ModuleX agent or workflow. Customer data platform for collecting, cleaning, and controlling customer data via the Segment Tracking API (api.segment.io/v1).
Categories: Analytics & Data · Analytics · Customer Data Platform · Auth: Write Key · Actions: 6
Authentication
Write Key
Authenticate using your Segment source Write Key (used as HTTP Basic Auth)Step 1
Log in to your Segment workspace at https://app.segment.com
Required Credentials
| Field | Description | Required | Format |
|---|---|---|---|
| Write Key | Your Segment source Write Key from app.segment.com | Yes | xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx |
Available Actions
alias — Associate one user identity with another in Segment
alias — Associate one user identity with another in Segment
Parameters
Previous unique identifier for the user
Unique identifier for the user in your database
Dictionary of extra context about the message such as IP address or locale
Dictionary of destinations to either enable or disable
ISO 8601 timestamp of when the message occurred (e.g. 2022-04-08T17:32:11.318Z)
Response
group — Associate an identified user with a group in Segment
group — Associate an identified user with a group in Segment
Parameters
Unique identifier for the group in your database
Unique identifier for the user. Either user_id or anonymous_id is required.
Pseudo-unique substitute for a User ID when no absolute identifier is available
Free-form dictionary of traits of the group such as name or plan
Dictionary of extra context about the message such as IP address or locale
Dictionary of destinations to either enable or disable
ISO 8601 timestamp of when the message occurred (e.g. 2022-04-08T17:32:11.318Z)
Response
identify — Identify a user and record traits about them in Segment
identify — Identify a user and record traits about them in Segment
Parameters
Unique identifier for the user. Either user_id or anonymous_id is required.
Pseudo-unique substitute for a User ID when no absolute identifier is available
Free-form dictionary of traits of the user such as email or name
Dictionary of extra context about the message such as IP address or locale
Dictionary of destinations to either enable or disable
ISO 8601 timestamp of when the message occurred (e.g. 2022-04-08T17:32:11.318Z)
Response
page — Record a page view on your website in Segment
page — Record a page view on your website in Segment
Parameters
Unique identifier for the user. Either user_id or anonymous_id is required.
Pseudo-unique substitute for a User ID when no absolute identifier is available
Name of the page being viewed
Free-form dictionary of properties of the page such as url and referrer
Dictionary of extra context about the message such as IP address or locale
Dictionary of destinations to either enable or disable
ISO 8601 timestamp of when the message occurred (e.g. 2022-04-08T17:32:11.318Z)
Response
screen — Record a screen view in your mobile app in Segment
screen — Record a screen view in your mobile app in Segment
Parameters
Unique identifier for the user. Either user_id or anonymous_id is required.
Pseudo-unique substitute for a User ID when no absolute identifier is available
Name of the screen being viewed
Free-form dictionary of properties of the screen
Dictionary of extra context about the message such as IP address or locale
Dictionary of destinations to either enable or disable
ISO 8601 timestamp of when the message occurred (e.g. 2022-04-08T17:32:11.318Z)
Response
track — Track an event that a user has performed in Segment
track — Track an event that a user has performed in Segment
Parameters
Name of the action the user has performed
Unique identifier for the user. Either user_id or anonymous_id is required.
Pseudo-unique substitute for a User ID when no absolute identifier is available
Free-form dictionary of properties of the event such as revenue
Dictionary of extra context about the message such as IP address or locale
Dictionary of destinations to either enable or disable
ISO 8601 timestamp of when the message occurred (e.g. 2022-04-08T17:32:11.318Z)
Response
Limits & Quotas
- Rate limits: Segment does not publish hard per-source rate limits for the Tracking API but recommends keeping requests under 500/second per source for optimal throughput.
- Batch size: Individual calls (
/track,/identify, etc.) accept one event per request. Use the/batchendpoint for bulk sends (not exposed here). - Error model: Non-2xx responses are caught and returned as
success=False+errorrather than raising.