Segment Review

Overview

Segment is a customer data platform (CDP) that collects event data from websites, apps, and servers, then routes it to 400+ downstream tools. You instrument Segment once, and it fans your data out to your analytics platform, your CRM, your email tool, your ad platforms, and your data warehouse simultaneously. For companies with complex multi-tool stacks, Segment eliminates the need to build individual integrations for every tool.

The product sits in the data infrastructure layer, not the analytics layer. Segment doesn't generate dashboards or reports. It collects, cleans, routes, and resolves identity across touchpoints. When a prospect visits your website, opens an email, and signs up for a trial, Segment stitches those events into a single user profile. That unified profile then flows to every downstream tool with consistent data.

Twilio acquired Segment in 2020 for $3.2B, which created both opportunities (deeper Twilio product integrations) and uncertainty (product roadmap shifts, organizational restructuring). The core product remains strong, but the CDP market has evolved. Newer alternatives like RudderStack (open-source Segment) and composable CDPs (Hightouch, Census) challenge Segment's position by offering warehouse-native approaches that skip the middleman.

GTM Engineer Use Cases

• Unified event tracking across marketing and product. Instrument Segment's analytics.js on your website and app. Every pageview, button click, form submission, and product action gets captured once and sent to all your tools. No more maintaining separate tracking code for Google Analytics, Mixpanel, and HubSpot.
• Identity resolution for prospect-to-customer journeys. Segment's Profiles feature merges anonymous visitor data with known user data after they identify themselves. Track the full journey from first ad click through demo request to closed deal with a single identity graph.
• Real-time event routing to outbound tools. When a prospect hits your pricing page for the third time, Segment can push that event to Slack, HubSpot, or your sales engagement tool in real-time. GTM Engineers build intent-based triggers off Segment events.
• Data quality enforcement with Protocols. Segment Protocols lets you define a tracking plan (which events, which properties, which types) and validates incoming data against it. Malformed events get blocked or flagged. This prevents the "garbage in, garbage out" problem that plagues analytics stacks.
• Warehouse integration for custom analysis. Segment's Warehouses destination pushes raw event data to Snowflake, BigQuery, or Redshift. GTM Engineers who write SQL can build custom attribution models, cohort analyses, and pipeline analytics on the raw event stream.

Pricing Breakdown

Plan	Price	MTUs	Key Features
Free	$0	1,000	2 sources, 300+ integrations, basic analytics
Team	$120/mo	10,000	Unlimited sources, Protocols, custom functions
Business	Custom	Custom	Identity resolution, data governance, SLA, SSO

Segment's pricing is based on Monthly Tracked Users (MTUs), which counts unique users sending events through Segment. The free tier's 1,000 MTUs work for early-stage products. The jump to $120/month for 10,000 MTUs is steep for what remains a data routing tool, not an analytics product.

The real cost escalation happens at scale. Companies with 50,000-500,000 MTUs pay thousands per month. Segment's Business tier pricing is custom-quoted and starts at $12,000+/year. For companies spending that much on data routing, the ROI calculation needs to account for the engineering time Segment saves versus maintaining direct integrations. At smaller scale, the question is whether you need a CDP at all.

Honest Criticism

Most GTM Engineers don't need a CDP. Segment solves a problem that emerges at scale: managing event data across many downstream tools. If your stack is Clay + Apollo + HubSpot + Instantly, you don't have a data routing problem. Direct integrations between these tools work fine. Segment adds value when you have 10+ downstream destinations consuming the same event stream. Below that threshold, it's engineering overhead without proportional benefit.

Pricing escalates quickly with MTUs. A SaaS company with 50,000 monthly active users can face $500-$1,500/month in Segment costs just for data routing. This is money that buys no dashboards, no reports, no insights. It buys the infrastructure to send data to tools that generate those insights. For budget-conscious teams, maintaining direct integrations (more engineering time, lower tool cost) is often the better trade.

The Twilio acquisition created roadmap uncertainty. Segment's original vision was "API for customer data." Under Twilio, the product has shifted toward Twilio Engage (campaign orchestration) and tighter Twilio product integrations. Some long-time users report that innovation on the core CDP features has slowed while the company pursues Twilio-centric use cases. Whether this matters depends on whether you use Twilio's other products.

Verdict

Segment is excellent infrastructure for companies with complex, multi-tool data stacks. If you're routing event data to 10+ downstream tools and need identity resolution across web, mobile, and server-side touchpoints, Segment saves significant engineering time and ensures data consistency.

Most GTM Engineers won't need Segment directly. It's a platform engineering decision, not a practitioner purchase. If your company already uses Segment, learn to work with it: understand the tracking plan, use the Protocols to enforce data quality, and build workflows off Segment events. If your company doesn't use Segment, don't buy it just for GTM purposes. HubSpot, Apollo, and Clay handle the data routing GTM Engineers need without a CDP layer.

Frequently Asked Questions

Do GTM Engineers need Segment?

Most don't. Segment solves data routing at scale (10+ downstream tools). GTM Engineers typically work with 4-6 tools that have direct integrations. Segment becomes relevant when you're building complex event-driven workflows or when your company already has Segment deployed and you can build on top of it.

How does Segment compare to PostHog?

Different products for different problems. Segment routes data to other tools. PostHog analyzes data directly. Segment has no dashboards. PostHog is primarily dashboards. Some companies use both: Segment for data collection/routing, PostHog as one of the analytics destinations. For GTM Engineers who want analytics, PostHog is the more useful tool.

Is RudderStack a better alternative to Segment?

RudderStack is open-source Segment with warehouse-first architecture. If your team is comfortable self-hosting and wants to avoid MTU-based pricing, RudderStack is a strong alternative. Data quality and integration coverage are comparable for most use cases. The tradeoff: you manage the infrastructure. For cloud-hosted, RudderStack's pricing is competitive with Segment.

What's the difference between Segment and a data warehouse?

Segment collects and routes data in real-time. A data warehouse (Snowflake, BigQuery) stores data for batch analysis. Segment can send data to your warehouse, making them complementary. Think of Segment as the pipeline and the warehouse as the destination. You can skip Segment and send data directly to your warehouse, but you lose real-time routing to other tools.