Segment (Tracking & Profiles)
Turn orders and customer changes into the right Segment (Tracking & Profiles) audiences and campaigns, with a person approving what goes out.
7 ways to read, 7 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Segment (Tracking & Profiles), an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Alias identitiesApproval by rule
- Send batchApproval by rule
- List account linksRead
Example flow
- Shopify · Read ordersDone
- Segment (Tracking & Profiles) · Track eventNeeds approval
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Segment (Tracking & Profiles).
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Segment (Tracking & Profiles)
- Segment (Tracking & Profiles)'s reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.
For developers
Technical detail
Send Segment identify, track, page, screen, group, alias and batch calls from a source write key, and read Unify profile traits, events, external IDs and links.
Twilio API docs- Source actions
- 7
- Destination actions
- 7
- Data types
- 14
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Account links1
- List account linksSource
User profiles linked to a Unify account profile, looked up by group ID.
Account traits1
- List account traitsSource
Traits on a Unify account profile, looked up by group ID.
Alias1
- Alias identitiesDestinationProvider duplicate protectionApproval before production
Sends an alias call merging a previous identity into the user. Segment forwards every accepted call to all destinations connected to the source, which can update marketing tools and trigger downstream messages or journeys.
Batch1
- Send batchDestinationProvider duplicate protectionApproval before production
Sends up to 500 identify, track, page, screen, group and alias calls in one request. Segment forwards every accepted call to all destinations connected to the source, which can update marketing tools and trigger downstream messages or journeys.
Group1
- Associate user with groupDestinationProvider duplicate protectionApproval before production
Sends a group call linking a user to an account or organisation. Segment forwards every accepted call to all destinations connected to the source, which can update marketing tools and trigger downstream messages or journeys.
Identify1
- Identify userDestinationProvider duplicate protectionApproval before production
Sends an identify call that ties a user to their traits. Segment forwards every accepted call to all destinations connected to the source, which can update marketing tools and trigger downstream messages or journeys.
Page1
- Record page viewDestinationProvider duplicate protectionApproval before production
Sends a page call for a website page view. Segment forwards every accepted call to all destinations connected to the source, which can update marketing tools and trigger downstream messages or journeys.
Profile events1
- List profile eventsSourceIncremental
Events recorded on a Unify user profile in the last 14 days, newest first by default.
Profile external IDs1
- List profile external IDsSource
Identifiers merged into a Unify user profile (user IDs, anonymous IDs, emails, device IDs).
Profile links1
- List profile linksSource
Account profiles linked to a Unify user profile.
Profile metadata1
- Get profile metadataSource
When a Unify user profile was created and updated, and its first and last messages.
Profile traits1
- List profile traitsSource
Traits, computed traits and audiences on a Unify user profile, with the source and time each was last set.
Screen1
- Record screen viewDestinationProvider duplicate protectionApproval before production
Sends a screen call for a mobile app screen view. Segment forwards every accepted call to all destinations connected to the source, which can update marketing tools and trigger downstream messages or journeys.
Track1
- Track eventDestinationProvider duplicate protectionApproval before production
Sends a track call recording an action the user performed. Segment forwards every accepted call to all destinations connected to the source, which can update marketing tools and trigger downstream messages or journeys.
Access and limits
- Authentication
- Source write key (Basic) and optional Profile API access token (Basic)
- Plans and access
- The Tracking API is available on every Segment plan through an HTTP API source. The Profile API needs Unify (Business tier). A write key belongs to one source and only sends data into it. Profile API access tokens are created per Unify space by workspace owners and can read every profile in the space.
- Test environment
- Use a free workspace with a dedicated HTTP API source that has no destinations connected, and watch the source debugger.
- Rate limits
- Tracking API: 1,000 requests per second; above 1,000 events per second per workspace Segment may queue events; HTTP 429 with Retry-After and X-RateLimit-Reset. Profile API: 100 requests per second per space by default; HTTP 429.
- Pagination
- Tracking API calls are single requests. Profile API lists return cursor.next and cursor.has_more; Nexra sends the cursor back as the next query parameter.
- Provider events
- Segment delivers events onward to destinations and Functions; there is no subscription API for Nexra triggers. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- Fan-out: Segment forwards every accepted call to all destinations connected to the source, which can update marketing tools and trigger downstream messages or journeys. Every send operation is a write that must be enabled per connection and is approval-gated like other sends.
- Segment returns HTTP 200 { success: true } for most payloads, including some invalid ones and unknown write keys; Nexra validates identity, field types, timestamps and size before sending, and a 200 does not prove the source accepted the data.
- The connection test validates credential format only. Segment documents no side-effect-free endpoint to verify a write key, and Nexra never sends a test event.
- Duplicate protection: the call carries a messageId (supplied, or derived from the Nexra delivery so a retry reuses it); Segment de-duplicates repeated messageIds within about 24 hours.
- Batches are limited to 500 events in Nexra (Segment allows 2,500), 500 KB per request and 32 KB per event; Nexra checks sizes before sending.
- Profile lookups accept user_id and anonymous_id identifiers only. Email and phone lookups, which Segment puts in the URL path, are not offered; user IDs that look like email addresses or phone numbers are refused.
- Profile events cover the last 14 days, as documented by Segment. Profile responses do not include consent preferences.
- Profile API page-size maximums are documented only for traits (200); other lists use up to 100 per page.
- Account profiles are limited to the documented account traits and links endpoints.
- OAuth for the Tracking API, Segment Public API workspace configuration (see the Segment connector), deletion and suppression requests, and Reverse ETL are not part of this connector.
Developer reference
- Create the Twilio credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Segment (Tracking & Profiles), enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/segment-tracking and the Connections API.