Segment

Segment

Segment collects event data from sources, transforms it, and routes to destinations (analytics, warehouses). Workspaces contain sources, destinations, and warehouses. Catalog endpoints list available integrations; instance endpoints manage your configured ones.

Data Model

• Sources — SDK, server, or SaaS ingest points; distinguish the integration marketplace from connectors already provisioned in your workspace.
• Destinations — downstream analytics tools and warehouses receiving forwarded events.
• Warehouses — supported lake/warehouse targets (BigQuery, Redshift, etc.) with catalog metadata vs live links.
• Transformations — serverless functions reshaping events mid-pipeline.
• Spaces — isolated sub-workspaces for multi-tenant or departmental boundaries.
• Labels — governance tags applied to connectors.
• Reverse ETL — models that push curated warehouse rows back into SaaS tools.
• Usage — daily API volume and Monthly Tracked User tallies for billing guardrails.

Gotchas

• Catalog vs workspace: Marketplace listings describe what can be installed; workspace endpoints describe what is installed—do not mix the two when planning changes.
• MTU (Monthly Tracked Users): Billing metric. Check usage before scaling sources.
• Transformations run in pipeline: Order matters; test with sample events.