Source connector

Segment connector

Segment integration for databases, warehouses and BI tools

Customer data platform routing events to warehouses. Datrise captures Segment entities such as sources, destinations, track events, identify calls, and schema catalog, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Segment Public API + Warehouse Syncs / Data Lakes authenticates with personal access token, incremental runs key on loaded_at, and Segment caps calls at No published default per-workspace limit; documented endpoint overrides include the Spaces API at 60 requests/minute and some Destinations endpoints as low as 5 requests/minute.

Of the 5 objects, 3 sync as upserts keyed on the primary key and 2 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `segment_sources`) with a schema derived from the Segment API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Segment pipeline page, and join the waitlist to get the Segment connector (Product analytics) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Segment data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
sources	segment_sources	Upsert by primary key, incremental on updated-at
destinations	segment_destinations	Upsert by primary key, incremental on updated-at
track events	segment_track_events	Append-only, incremental by timestamp
identify calls	segment_identify_calls	Append-only, incremental by timestamp
schema catalog	segment_schema_catalog	Upsert by primary key, incremental on updated-at

Segment API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Segment Public API + Warehouse Syncs / Data Lakes
Authentication	personal access token — The Public API (workspace/source/destination management) authenticates with a workspace-scoped "Public API token" sent as `Authorization: Bearer $TOKEN`; there is no OAuth2 flow for it.
Pagination	cursor — List endpoints take `pagination.count` (default 200, max 1,000) and an opaque `pagination.cursor`, returning `current`/`next`/`previous` cursors rather than offsets.
Rate limit	No published default per-workspace limit; documented endpoint overrides include the Spaces API at 60 requests/minute and some Destinations endpoints as low as 5 requests/minute
Incremental cursor	loaded_at — Actual event/object data is not pulled through the Public API but lands via scheduled Warehouse Syncs, where a `loaded_at` staging timestamp column is only added for BigQuery warehouses.
Webhooks	Yes — Webhooks destination (real-time HTTP POST per event, configured like any other Segment destination)
Bulk export	Yes — Warehouse Syncs / Data Lakes (batch load into a customer warehouse, S3 + Glue Catalog, or lake)
Deletes detectable	No

Official API reference

What bites when replicating Segment

Segment explicitly does not delete historical rows from a connected warehouse when a collection or property is disabled, so a pipeline cannot infer source-side deletes from what is missing in a later sync.
Warehouse sync frequency is plan-gated: Free syncs once every 86,400 seconds (daily), Team twice daily, and only Business unlocks up to 24 syncs/day and a full historical backfill (lower tiers backfill roughly two months of history on connect).
Selective Sync cannot go past 5,000 collections per source or 5,000 properties per collection in the UI (an 80% warning fires first); more requires a support request.
There is no single documented rate limit for the Public API; individual resources like the Spaces API (60 req/min) and several Destinations endpoints (as low as 5 req/min) enforce their own, tighter caps returned via `X-RateLimit-*` headers.

Compare this against every other documented API

Popular destinations for Segment

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Segment connector FAQ

What Segment data does the connector extract?: 5 objects: sources, destinations, track events, identify calls and schema catalog. Each lands in its own table with types preserved; history-style objects (2: track events and identify calls) load as append-only streams.
Is the Segment integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Segment data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Segment → destination pair has its own page with the object-to-table mapping.

Related Product analytics sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Segment pipeline with guided onboarding

Join the waitlist to get priority access for Segment integrations with guided setup, schema-aware mapping, and production-grade incremental sync.