A small team evaluating a customer data platform usually starts from the same place: signups are coming in from a social campaign or two, a spreadsheet or an email tool’s built in segmentation has stopped being enough, and someone has to figure out what a real CDP costs before anyone agrees to a sales call. Most CDP marketing pages are not written for that reader. They are written for a buyer with a data team and a champion inside a large org. Segment, the product Twilio sells under the name Twilio Segment, publishes a self serve tier specifically for the smaller evaluation, the one that starts with a credit card and a pricing page, not a discovery call.
The buyer this piece is for
If your team is still deciding whether a CDP is the right category of tool, not which enterprise vendor to negotiate with, you are the reader this piece is written for. Segment’s Free and Team tiers exist precisely so that a small team can sign up, connect a source or two, and see what the tool does before anyone talks to a salesperson. That self serve path is not a stripped down demo of the real product. It is Segment’s own on ramp, and understanding what it actually meters is the difference between a plan that fits and a bill that surprises you in month two.
What Segment actually calls the metered unit
Segment’s pricing page runs on a single meter across both self serve tiers: the monthly tracked user, or MTU. The page’s own FAQ answers the question directly. Asked how to estimate MTUs, Segment’s guidance is to add your monthly active users to the number of anonymous visitors you get per month, fetched from the pricing page’s “How can I estimate my MTUs?” accordion on September 9, 2026.
The pricing cards on the same page label this same figure “visitors/mo,” while the tier comparison table further down calls it “Monthly Tracked Users.” Both terms describe one meter, not two. A reader comparing the hero numbers on the cards against the line items in the comparison table should read them as the same count, not as separate limits.
The plain consequence: MTU is not seats, and it is not the people who log into your Segment workspace. It counts end users and site visitors that your sources track, whether or not they ever create an account. A five person team can run a workspace with an MTU count in the tens of thousands, and a fifty person team can run one with an MTU count in the hundreds, because the number tracks your audience, not your headcount.
The three published tiers
| Tier | Price | Monthly tracked users | Sources | Seats | Notes |
|---|---|---|---|---|---|
| Free | $0/month | Up to 1,000 | 2 | [EVIDENCE NEEDED: seat count for Free was not shown in the comparison table’s Seats row on this fetch] | Create a free account, no trial needed |
| Team | Starting at $120/month | Base includes 10,000 | Unlimited (per the page’s plan comparison table) | 10 | 14 day free trial noted on the page |
| Business | Contact sales, no published self serve price | Custom volume | Unlimited | Unlimited | Custom quote only |
The source and seat figures for Team and Business above come directly from the plan comparison table on the same pricing page fetch as the rest of this piece, checked September 9, 2026. Everything else in this section is read the same way: no figure here is carried over from an older post or estimated.
What happens past 10,000
Team tier pricing does not stop at the 10,000 MTU included in the $120 base. The pricing page’s comparison table breaks additional usage into three bands, each priced per additional 1,000 monthly tracked users: 10,000 to 25,000, 25,000 to 100,000, and 100,000 and above.
The rate is not flat across those bands, which is worth stating plainly because it is easy to assume otherwise. At the entry point of the Team tier, the 10,000 to 25,000 band, the page prices additional MTU at $12 per 1,000. The 25,000 to 100,000 band drops to $11 per 1,000, and the 100,000 plus band drops again to $10 per 1,000. So the marginal rate falls as usage grows, rather than holding at a single number across the whole range.
The page also discloses that annual billing works differently: choosing an annual plan lets a team purchase MTU at a lower rate than the month to month price, according to the page’s own FAQ. The same FAQ notes that exceeding the allotted MTU count on an annual plan can incur additional charges. The page does not publish what that lower annual rate actually is, so this piece states only what the FAQ says, not a computed discount.
Why a social driven signup spike changes the estimate
Because MTU counts anonymous visitors in addition to active users, a landing page that catches a traffic spike from a social post can push a workspace into a higher tier even when the campaign converts almost nobody. A post that sends ten thousand curious clicks to a page Segment is tracking adds roughly ten thousand to that month’s MTU count, regardless of how many of those visitors ever sign up.
This is a mechanical consequence of the definition Segment publishes, monthly active users plus anonymous visitors, not a flaw in the product or a criticism of how it is priced. It does mean a small team should look at its actual traffic volume, not just its active user count, before picking a tier. A team whose product has a small user base but a page that regularly gets shared can carry a much larger MTU number than the size of its user base would suggest.
What the self serve tiers do not tell you
- Business tier pricing is not published anywhere on the page. Contact sales is the only path once a team’s needs exceed what Team tier offers, and the page does not describe what those needs typically are.
- The page does not publish a fixed per source limit for Team; the comparison table marks Team’s sources as unlimited on this fetch, and Business the same way.
- [EVIDENCE NEEDED: the Free tier’s row in the Seats column of the comparison table was not populated with a visible number on this fetch, so no seat count for Free can be stated]
- The exact dollar figure behind an annual plan’s “lower rate” for MTU is not published. The page states the benefit exists without stating the rate.
A rough way to size it before signing up
Segment’s own guidance for estimating your MTU count is to add your monthly active users to your monthly anonymous visitors. That is the entire formula the page publishes, and a small team can run it before signing up for anything.
Picture a hypothetical example, not a real company: a small team’s app has 1,400 monthly active users, and its marketing site draws roughly 6,000 unique visitors a month between organic search and social. Added together, that is about 7,400 MTU, comfortably under the Team tier’s included 10,000 and nowhere near where a self serve tier for Business would need to enter the picture. Now picture the same team running a social campaign that briefly triples site traffic to 20,000 visitors in one month. Even with active users unchanged, the MTU count for that month would be roughly 21,400, which is past the Team tier’s included 10,000 and into the second billing band. Both numbers here are illustrative only, built from round figures to show how the arithmetic works, not a measurement of any real workspace.
FAQ
Does Segment’s self serve plan charge by team seats?
No. The metered unit is the monthly tracked user, defined on Segment’s pricing page as monthly active users plus anonymous visitors. It has nothing to do with the number of people who have logins to the workspace. Team tier does list 10 seats and Business lists unlimited seats in the page’s comparison table, but those are features of the plan, not the basis for the bill.
What is included in Segment’s free tier?
As published on the pricing page on September 9, 2026, the Free tier is $0 per month, includes up to 1,000 monthly tracked users, and includes 2 sources.
Sources
- Twilio Segment, Connections pricing, fetched September 9, 2026. Free, Team, and Business tier pricing, the MTU estimation FAQ, the annual billing FAQ, and the incremental MTU pricing bands were all read directly from this page on this date. Prices verified this date; this is not Watchdog data and is not on followedapp’s re-verification schedule.
Back to Blog