Segment Team starts at $120 a month. Your traffic and identity setup decide how long it stays there.
Segment bills monthly tracked users, including anonymous visitors who never convert. A weak identity implementation can count one person more than once. API throughput has its own limit, and the CDP features most buyers associate with Segment can require custom pricing.
All figures below were checked against Twilio Segment Connections pricing and Segment's usage documentation in August 2026. Pricing and contract terms change, so verify them before signing.
Segment pricing plans in 2026
| Plan | Monthly price | Included MTUs | Buying model |
|---|---|---|---|
| Free | $0 | 1,000 | Self-service |
| Team | From $120 | 10,000 | Monthly or annual |
| Business | Custom | Custom | Sales contract |
The Free plan includes two sources, unlimited destinations, one warehouse destination, and up to 10 workspace seats. It can test a real implementation. Load-test expected production traffic before treating it as a production budget.
Team removes the two-source limit, adds Public API access, and keeps the base allowance at 10,000 MTUs. Twilio advertises a 14-day Team trial. Annual contracts can save up to 20 percent, while usage beyond the purchased allowance can still create extra charges.
Business adds custom volume, regional infrastructure, advanced permissions, data governance, and CDP options. There is no public Business price.
What Segment counts as an MTU
MTU means monthly tracked user. Segment counts:
- Every unique
userIdseen during the billing month. - Every unique
anonymousIdthat was not associated with auserIdduring that month.
Events from one known user across several sources can resolve to one MTU when they carry the same userId. Anonymous activity is less tidy.
A visitor who browses on a phone and laptop without logging in can count twice. A person who clears cookies and returns gets a new anonymousId. Incognito sessions create fresh identifiers. If your login flow never joins the anonymous history to a known user, the identifiers remain separate for billing.
Your identity implementation changes the bill. The same audience can produce different MTU counts in two Segment workspaces when only one resolves identity correctly.
For a marketing team, the practical budgeting input is closer to monthly unique visitors than monthly active customers. A campaign that brings 40,000 anonymous visitors and 800 conversions is not an 800-MTU campaign.
Team overage rates
The monthly Team plan uses graduated overage pricing:
| Monthly tracked users | Charge |
|---|---|
| First 10,000 | Included in $120 base fee |
| 10,001 to 25,000 | $12 per additional 1,000 MTUs |
| 25,001 to 100,000 | $11 per additional 1,000 MTUs |
| Above 100,000 | $10 per additional 1,000 MTUs |
These are marginal tiers. Reaching 50,000 MTUs does not price every user at the final rate.
Twilio's own example calculates 50,000 MTUs like this:
| Charge | Amount |
|---|---|
| Base plan, first 10,000 MTUs | $120 |
| Next 15,000 MTUs at $12 per 1,000 | $180 |
| Next 25,000 MTUs at $11 per 1,000 | $275 |
| Total | $575 |
Paid workspaces continue processing data when they exceed the included MTUs. Monthly Team applies the published overage charges, while Business overage follows the contract. Repeated limit breaches on Free can stop ingestion and delivery until the workspace is upgraded or otherwise resolved.
What Segment costs at real volumes
The published Team rates, applied across a range of workspace sizes:
| Monthly tracked users | Monthly cost | Effective rate per 1,000 MTUs |
|---|---|---|
| 10,000 | $120 | $12.00 |
| 25,000 | $300 | $12.00 |
| 50,000 | $575 | $11.50 |
| 100,000 | $1,125 | $11.25 |
| 250,000 | $2,625 | $10.50 |
| 500,000 | $5,125 | $10.25 |
| 1,000,000 | $10,125 | $10.13 |
The 50,000 row is Twilio's own worked example. Every other row applies the same graduated rates: $120 for the first 10,000, then $12, $11, and $10 per additional 1,000.
Annual contracts are advertised at up to 20 percent off, which puts the 100,000 row nearer $900 a month. Workspaces of this size are also normally moved onto Business, which is quoted rather than published, so read the higher-volume rows as the published-rate ceiling rather than a quote you would receive.
MTUs are also not the only meter. Throughput and Functions execution time are counted separately and do not appear in this table.
What anonymous traffic does to the bill
A consumer site with 200,000 monthly visitors who never identify themselves and 5,000 known customers is a 205,000-MTU workspace.
| Line | Amount |
|---|---|
| First 10,000 MTUs | $120 |
| Next 15,000 at $12 per 1,000 | $180 |
| Next 75,000 at $11 per 1,000 | $825 |
| Remaining 105,000 at $10 per 1,000 | $1,050 |
| Monthly total | $2,175 |
Those 5,000 customers account for $50 of the $2,175 at the marginal rate. Remove them and the bill barely moves. Remove the anonymous traffic instead and a 5,000-MTU workspace fits inside the $120 base plan.
Size the plan from a monthly unique visitors report rather than a CRM count, then check how much of the gap identity resolution can collapse back into known users.
Throughput and Functions add two more meters
Segment documents three core billing measurements: API calls, MTUs, and throughput.
Free and Team include up to 250 API calls and cloud-source objects per MTU. A Team workspace with 10,000 paid MTUs therefore has a standard aggregate allowance of 2.5 million API calls and objects for the month.
Batching does not reduce that count. Segment unpacks the batch and counts the objects and calls inside it.
Cloud sources can also move the number in ways a website traffic report will not show. Event sources can introduce new MTUs when their records contain user or anonymous identifiers. Object sources can raise throughput because every retrieved record counts as an object, including records fetched again before deduplication in some integrations.
Functions have another meter. Segment measures their total execution time each month, and requests to external APIs can extend that execution time. The public plan table lists 50 hours for Free and Team and custom limits for Business.
A high-event product, frequent cloud sync, or slow custom Function can expose the second meter quickly.
The $120 plan covers Connections
Connections collects data from web, mobile, servers, and cloud apps, then routes it to destinations and warehouses. That is the product covered by the public Free and Team prices.
Protocols, Unify, and Engage are separate capabilities:
Protocols governs schemas and tracking plans. It is listed as a Business add-on.
Unify resolves identity and builds customer profiles. Twilio lists identity resolution only with CDP plans.
Engage builds audiences and journeys on those profiles. It is also sold through the CDP offer.
Requirements for identity resolution, computed traits, audiences, and journey orchestration push the purchase beyond the $120 Connections plan. Ask for the complete CDP package and its usage units.
Costs outside the Segment invoice
Segment does not pay the vendors at the other end of its connections. Twilio's pricing FAQ says customers remain responsible for their source, destination, and warehouse accounts.
A working marketing data stack can include:
- Segment Connections
- A warehouse and its compute or storage bill
- Product or web analytics
- Email, CRM, and advertising platforms
- Consent management
- Implementation and ongoing schema ownership
- Premium Segment support or professional services
The Connections subscription is one line in this budget because every connected vendor keeps its own bill.
When Segment is the right call
Use Segment when a shared customer data model serves several teams and products. Engineering can instrument once, data teams can govern the schema, lifecycle teams can build audiences, and product teams can choose their own destinations.
Segment fits best when Unify profiles and Engage journeys are required.
The tradeoff is ownership. Someone must define identities, event contracts, source boundaries, destination behavior, and warehouse syncs. A large integration catalog reduces connection work. It does not make those decisions for you.
How Hardal compares
Hardal bills events and includes marketer-facing measurement that Segment expects downstream.
Hardal gives marketers one governed first-party event stream for advertising APIs, analytics tools, warehouses, CRM systems, and custom endpoints. Web and mobile analytics, attribution, server-side delivery, managed sGTM and gateway options sit in the same product. Enterprise customers can self-host.
Plans start at $249 per month for 5 million events. Segment Team starts at $120 for 10,000 MTUs. Events and users measure different things, so converting between them requires your real traffic data.
Segment is the broader product for identity-resolved profiles, journey orchestration, and a CDP shared by engineering, data, and lifecycle teams. Hardal is more direct for reliable campaign measurement and conversion delivery without a separate collector, reporting layer, and destination manager.
Full product comparison: Hardal vs Twilio Segment. Current Hardal plans: usehardal.com/pricing.
For adjacent enterprise data platforms, compare the Tealium pricing guide and Piwik PRO pricing guide.
The short version
The $120 headline is real, and Connections is a good pipe.
Count anonymous visitors, not customers. The MTU number tracks unique visitors far more closely than it tracks active customers, and a weak identity implementation widens that gap every month.
Then check whether you are buying Connections or a CDP. Protocols, Unify, and Engage are where most Segment evaluations end up, and none of them sit inside the published price.
Need reliable marketing measurement and destination delivery without a full CDP rollout? Compare Hardal and Segment →