Nexra
All connectors
Implemented
Marketing & advertising

Segment (Tracking & Profiles)

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.

Feed customer events and traits from operational systems into Segment so every connected marketing and analytics destination stays current, and use Unify profiles to personalise flows.

Build a flow with Segment (Tracking & Profiles)Provider API documentation

Source actions

7

Destination actions

7

Data types

14

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

account links
  • List account links
    Source

    User profiles linked to a Unify account profile, looked up by group ID.

    account_links.list
account traits
  • List account traits
    Source

    Traits on a Unify account profile, looked up by group ID.

    account_traits.list
alias
  • Alias identities
    Destination
    Provider duplicate protection
    Approval 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.

    alias.send
batch
  • Send batch
    Destination
    Provider duplicate protection
    Approval 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.

    batch.send
group
  • Associate user with group
    Destination
    Provider duplicate protection
    Approval 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.

    group.send
identify
  • Identify user
    Destination
    Provider duplicate protection
    Approval 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.

    identify.send
page
  • Record page view
    Destination
    Provider duplicate protection
    Approval 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.

    page.send
profile events
  • List profile events
    Source

    Events recorded on a Unify user profile in the last 14 days, newest first by default.

    profile_events.list
profile external ids
  • List profile external IDs
    Source

    Identifiers merged into a Unify user profile (user IDs, anonymous IDs, emails, device IDs).

    profile_external_ids.list
profile links
  • List profile links
    Source

    Account profiles linked to a Unify user profile.

    profile_links.list
profile metadata
  • Get profile metadata
    Source

    When a Unify user profile was created and updated, and its first and last messages.

    profile_metadata.get
profile traits
  • List profile traits
    Source

    Traits, computed traits and audiences on a Unify user profile, with the source and time each was last set.

    profile_traits.list
screen
  • Record screen view
    Destination
    Provider duplicate protection
    Approval 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.

    screen.send
track
  • Track event
    Destination
    Provider duplicate protection
    Approval 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.

    track.send

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. Nexra event triggers are not yet available; flows run on demand or on a schedule.

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

  1. Create the Twilio credentials described above with the narrowest permissions your flows need.
  2. 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
  3. Test the connection, then use its actions as flow sources and destinations. Flow guide
Twilio docsAPI referenceTwilio docsAuthenticationTwilio docsRate limits

Machine-readable detail: GET /api/public/connect/connectors/segment-tracking and the Connections API.