by Segment
Track an event
Records one action a user took, such as Signed Up, with its properties and routes it to the source's destinations.
Description
Send `event`, `userId` or `anonymousId`, and optional `properties`; a request can be up to 32 KB. Segment deduplicates on `messageId`, so give every event a unique one under 100 characters. `SEGMENT_API_KEY` holds the base64 of the source's write key followed by a colon.
track-event.md
Track an event
Records one action a user took, such as Signed Up, with its properties and routes it to the source's destinations.
Send event, userId or anonymousId, and optional properties; a request
can be up to 32 KB. Segment deduplicates on messageId, so give every event a
unique one under 100 characters. SEGMENT_API_KEY holds the base64 of the
source's write key followed by a colon.
Set up
Use the first option your agent supports.
API (official)
- Base URL: https://api.segment.io
- Endpoint:
POST /v1/track - Auth: send the header
Authorization: Basic $SEGMENT_API_KEY - Get a key: https://www.twilio.com/docs/segment/connections/find-writekey
- Docs: https://www.twilio.com/docs/segment/connections/sources/catalog/libraries/server/http-api
Before doing anything else, make one read-only call to confirm access.
Rules
- Ask the user before anything that sends messages, costs money, or changes data.
- Never print API keys.
Built from these files in the repository
The layout and the rules come from lib/catalog/render-markdown.ts, the set-up wording from lib/catalog/render-access.ts.
Ways in
| Route | Source | Call | Required | Docs |
|---|---|---|---|---|
| Official | POST /v1/track | API key in $SEGMENT_API_KEY | Docs |