Segment has three tiers: Free (1,000 MTU, 2 sources), Team ($120/month for 10,000 MTUs, with tiered overage rates of $10-12 per additional 1,000 MTU), and Business (custom-quoted, typically starting around 100,000 MTU, bundling identity resolution and Reverse ETL). Enterprise-scale Business deployments commonly run $25,000-500,000+/year depending on volume and features.
- MTU (Monthly Tracked User) counts every unique userId and every unique anonymousId seen in a billing month — including visitors who never convert
- A person browsing on a phone and a laptop without logging in can generate two separate anonymousIds and count as two MTUs
- Overage pricing is tiered and marginal — reaching 50,000 MTUs doesn't price every user at the top-tier rate
- CDP features (Unify, Engage, AI predictions) require the custom-quoted Business tier with no public pricing
Segment's Team plan looks simple at $120/month for 10,000 MTUs, until you understand exactly what an MTU counts. It's not 10,000 customers — it's 10,000 unique tracked identities, and that includes every anonymous visitor your website ever logs an event for, whether or not they ever become a real customer.
This guide breaks down what actually counts toward your MTU total, how overage pricing works once you exceed your plan's allowance, and what moves a company into custom Business-tier territory.
1. How much does Twilio Segment cost?
Source: segment.com/pricing (verified) + Vendr transaction data, verified Sep 19, 2026.
Annual contracts on Team can save up to 20% versus month-to-month. Overage beyond Team's included 10,000 MTU is tiered and marginal: $12 per additional 1,000 MTU from 10,000-25,000, $11 per 1,000 from 25,000-100,000, and $10 per 1,000 above 100,000 — meaning your effective blended rate decreases as volume grows, rather than every user being priced at the highest tier. Business pricing is entirely custom, typically structured around declining per-MTU rates across volume bands.
2. What each plan includes
| Feature | Free | Team | Business |
|---|---|---|---|
| Core event collection & 700+ destinations | ✓ | ✓ | ✓ |
| Reverse ETL | ✕ | ✓ | ✓ |
| Unify (identity resolution) | ✕ | ✕ | ✓ |
| Engage (audiences & journeys) | ✕ | ✕ | ✓ |
| Advanced data governance & Protocols | ✕ | ✕ | ✓ |
3. Cost calculator
4. Hidden costs to budget for
| Scenario | Annual cost | Change |
|---|---|---|
| Free, under 1,000 MTU | $0/yr | Base |
| Team, 10,000 MTU included | $1,440/yr | Base |
| Team, 50,000 MTU (with overage) | ~$5,700/yr | Marginal tiered overage applies |
Beyond MTU counting, API throughput has its own separate limit that can constrain high-volume implementations independent of your MTU allowance. The CDP features most buyers actually associate with Segment's brand — Unify for identity resolution and Engage for audience building — require moving to the custom-quoted Business tier; the self-serve Team plan's Connections product doesn't include them at any price point.
5. How Twilio Segment pricing has changed
6. Which plan should you choose?
- For evaluating Segment on a small, early-stage implementation, Free's 1,000 MTU and 2 sources cover initial testing.
- Most growing companies land on Team, but should model actual anonymous-plus-known traffic realistically before assuming 10,000 MTU covers their needs.
- Organizations needing identity resolution, audience orchestration, or advanced governance should expect a Business-tier quote, typically starting around 100,000 MTU volume.
7. Is it worth the price?
For companies that genuinely need a unified data collection layer feeding many downstream analytics and marketing tools, Segment's 700+ destination catalog remains a strong reason to choose it over building custom integrations. The MTU-based pricing model rewards clean identity implementation — a well-architected setup that resolves anonymous visitors to known users efficiently keeps the MTU count closer to your actual audience size, which is a genuine, addressable cost lever rather than something to simply accept.
8. How to pay less
- Audit your identity resolution setup for double-counting before assuming your MTU total reflects real audience size — a weak implementation inflates the bill without adding any real value.
- Understand the tiered overage structure before panicking about crossing 10,000 MTU — the marginal rate decreases at higher bands, so overage isn't as punishing as a flat-rate assumption would suggest.
- Scope your Business tier negotiation around actual MTU volume and specific CDP features needed rather than accepting a generic enterprise quote.
- Consider annual billing for the up-to-20% savings if your MTU volume is reasonably stable and predictable.
For teams sizing a Business tier evaluation, third-party estimates suggest mid-market deployments commonly run $25,000-100,000/year, with larger enterprise deployments reaching $100,000-500,000+ depending on MTU volume and feature scope.
9. Alternatives and what they cost
| Tool | Entry price | Cheaper when |
|---|---|---|
| RudderStack | Free (self-hosted) / usage-based | Open-source, self-hosted control over the data pipeline is preferred |
| mParticle | Custom | Comparable CDP capability is needed with different pricing structure |
| Snowplow | Free (open source) / custom | Full data ownership and warehouse-native architecture matter most |
10. The bigger picture: why Twilio Segment bills drift
A usage metric that can inflate without any change in real customer behavior — purely from technical implementation details — is exactly the kind of cost driver that rewards deliberate, ongoing tracking rather than a one-time setup review. Zapro AI is built to flag this kind of usage-based cost pattern across your vendor list, not just the sticker price.
11. The bottom line
Segment's MTU-based pricing is reasonable in principle, but understanding precisely what counts as an MTU — including anonymous visitors and potential double-counting from weak identity resolution — is essential before assuming your bill reflects your real audience. Audit your identity implementation as a genuine cost lever, and scope any Business-tier negotiation around the specific CDP features you actually need.
FAQs
It's every unique userId and every unique anonymousId that generates at least one event during a billing month — including anonymous website visitors who never convert into identified customers.
Yes, in practice. A visitor who browses on multiple devices without logging in, or who clears cookies and returns, can generate multiple anonymousIds — each counted as a separate MTU even though it's one real person.
Team includes 10,000 MTU for $120/month, with tiered overage of $12/1,000 MTU from 10,000-25,000, $11/1,000 from 25,000-100,000, and $10/1,000 above 100,000 — the marginal rate decreases at higher volume.
No. Those CDP features (identity resolution and audience/journey orchestration) require the custom-quoted Business tier — they're not available on the self-serve Team plan at any price.
The most common way is an MTU count inflated by weak identity resolution, effectively paying for the same person multiple times. A vendor spend platform combined with an identity implementation review is the most reliable way to catch this.