Segment Pricing 2026: Plans, MTU Overage and Real Cost

Segment pricing looks simple on the plan cards and gets harder once you read how monthly tracked users are counted and what happens above the allowance. Twilio Segment is a customer data pipeline: it collects events from your site and apps and sends them on to other tools. This guide records what Twilio publishes about the price on 16 October 2026, how the bill grows, and whether an online store needs a data pipeline at all.

The short answer: Segment starts at $120 a month, and Arktis is the clear winner for store attribution

Twilio Segment sells its pipeline, called Connections, on three plans. Free costs $0 and covers 1,000 monthly tracked users (MTUs). Team starts at $120 a month and includes 10,000 MTUs, with each extra 1,000 costing $12 up to 25,000, $11 up to 100,000 and $10 above that. Business is custom priced through sales. The full customer data platform, which adds Unify and Engage on top of Connections, is sold only through sales. These are the prices shown on 16 October 2026, in US dollars when viewed from Sweden, on a page that says pricing is current as of August 2026.

Arktis is not a customer data platform and does not route events to other tools. But if the real question behind a Segment search is which ads and campaigns brought your orders, Arktis is the clear winner for an online store. It captures ad click identifiers and UTM tags on landing, matches orders back to the visit, and counts conversions per campaign and per ad platform, without a pipeline and a second tool to do the attribution. Growth, at $149 a month for up to 250,000 monthly tracked visitors, is the plan that lists conversion tracking and session recordings, and it has a 7-day free trial; Starter is $49 for up to 50,000 and Scale is $349 with unlimited visitors.

Key takeaways

Connections plans are priced on people rather than events: an MTU is each unique user ID plus each anonymous ID not tied to a user ID in a billing month, so every browser that visits a store counts. Team includes 10,000 MTUs for $120 a month, and Twilio's own example puts 50,000 MTUs at $575 a month on the monthly Team plan. Paid workspaces keep collecting above the allowance and pay overage, while a Free workspace that goes over twice in six months stops receiving data. Team has a 14-day free trial, annual billing saves up to 20 percent according to the pricing page, and the prepaid part of an annual plan is not refunded after the trial. Segment moves data; it does not tell you which campaign earned an order.

What Segment sells: Connections and the CDP

Twilio's customer data pricing page splits the product in two. Connections is described as a customer data pipeline for collecting first-party data and sending it to other tools, with more than 700 integrations listed. The Customer Data Platform is Connections plus Unify and Engage, which add identity-resolved profiles, audiences and journeys, and it has a contact sales button and no published price.

The Connections pricing page's FAQ says many teams start with Connections and add the CDP later. Everything with a published price in this guide is a Connections plan.

The plans in detail

The Free plan includes 1,000 visitors a month, which the page also calls MTUs, two sources, more than 700 integrations, one data warehouse destination and 500,000 Reverse ETL records a month. Its warehouse syncs once a day.

Team includes 10,000 MTUs, unlimited sources, one warehouse with two syncs a day, 1,000,000 Reverse ETL records, public API access and 10 seats. It is paid by credit card, on monthly or annual terms.

Business has custom volume and unlimited seats and warehouses, and adds data governance, advanced roles and permissions, HIPAA eligibility with a business associate agreement (marked as an add-on in the comparison table), and a choice of EU or US regional infrastructure. Segment's documentation marks Protocols, Engage and Replay as Business tier features, and the pricing page lists Protocols as an optional add-on.

What counts as an MTU

Segment's documentation defines it precisely. Segment counts the unique user IDs, then adds the unique anonymous IDs that were not associated with a user ID during the billing period, across all sources in the workspace. Each user counts once a month, however many events they send.

For a store, the consequence is that most visitors are anonymous and each one is an MTU. The same documentation lists what pushes the count up: a visitor on a second browser gets a new anonymous ID, private browsing creates a new ID each session, clearing cookies starts over, and tracking two separate domains creates a new ID per domain. A traffic spike from a sale or a press mention raises the bill in the same month.

Overage: what Team costs as traffic grows

Twilio's support article on the monthly Team plan gives the overage rates in tiers: $12 per 1,000 MTUs from 10,001 to 25,000, $11 per 1,000 from 25,001 to 100,000, and $10 per 1,000 above 100,000. The comparison table on the pricing page shows the same three rates. One line on the same page is looser: its FAQ says Team adds $10 per 1,000 visitors beyond 10,000. The table and the support article agree on the tiers, so budget with those.

The 50,000 row is Twilio's own worked example. The other rows are our arithmetic using the same rates, on monthly billing, before tax.

Exceeding the allowance does not stop a paid workspace. Twilio's support article says data keeps flowing to your destinations on monthly Team plans and the overage is charged, while Business overage is set by your contract.

The Free plan works differently. Segment's billing FAQ says that if you exceed 1,000 MTUs once in a six-month period the account is locked but data still flows, and if you exceed it twice in six months Segment locks the account and stops sending and receiving data until you move to Team.

Billing, trial and cancellation

Team comes with a 14-day free trial. Segment's billing FAQ says you need to add payment details if you upgrade from Free, but not if you sign up for a new Team plan, and that a subscription with payment details on file continues at the regular rate when the trial ends. Cancelling during the trial costs nothing.

On monthly Team, the billing cycle starts the day after the trial ends. Cancelling mid-month produces a final prorated bill for the $120 base plus any MTU overage.

On annual Team, you are billed at the end of the trial for a full year including a set number of MTUs, and overage is billed at the end of each monthly cycle. The pricing page says annual billing saves up to 20 percent. Segment does not refund the prepaid part of an annual plan after the trial, and the FAQ warns that data still sent after you ask to cancel can generate overage, so delete the workspace or rotate the write keys.

Throughput and other limits

MTUs are not the only meter. Segment's documentation says plans can carry a throughput limit, a number of API calls and objects allowed per MTU each month across the workspace. Its example is a limit of 250 on a 10,000 MTU plan, which allows 2.5 million calls and objects a month. The pricing page lists the throughput limit as standard on Free and Team and custom on Business.

Functions, Segment's custom code feature, is listed with 50 hours on Free and Team.

What a store gets from Segment, and what it does not

Segment's job is collection and delivery. Its tracking library records a campaign object with the standard UTM fields, name, source, medium, term and content, and passes it to the destinations you connect. That makes Segment useful when a store already runs several tools that all need the same events: an email platform, a warehouse, an ad platform's server-side feed and a product analytics tool.

What it does not do is the attribution itself. Segment's own guide to its role in attribution, written about mobile install attribution, says Segment loads the attribution provider's code but that attribution happens outside Segment. A store that buys Segment to find out which campaigns drive revenue still needs a destination that matches orders to visits and reports on them, and pays for that tool on top.

Segment against Arktis for the attribution question

Take a store with 50,000 monthly visitors, all anonymous until checkout. On monthly Team billing that is about $575 a month in MTUs before any destination is paid for. On Arktis, the plan for that question is Growth at $149 a month for up to 250,000 monthly tracked visitors, because it is the plan that lists conversion tracking and goals; Starter, at $49 for up to 50,000, lists 7 days of data retention and does not list conversion tracking. At 100,000 visitors it is still Arktis Growth at $149 against $1,125 for Segment Team. The meters are not identical, since Segment counts unique IDs and Arktis counts tracked visitors, but the gap is wide enough that the difference in counting does not change the comparison.

Arktis is the product we build, so weigh this accordingly. Its tracker captures gclid, gbraid and wbraid from Google, fbclid from Meta, msclkid from Microsoft, ttclid from TikTok and other click identifiers, plus UTM parameters, and holds them against the visitor across sessions, server side. Shopify orders arrive by webhook and are matched to a visit on email where the store has identified the visitor, otherwise on the UTM source of a session from the previous 24 hours, which can be another visitor's session. Stripe customers are matched through a four-pass waterfall. Unmatched orders are kept, unattributed. An order counts for an ad platform when the visit it was matched to arrived with that platform's click identifier.

From those matched orders and the conversion events its tracker records, Arktis counts conversions per UTM campaign and per ad platform, next to the Meta spend it syncs per campaign once a day. Google, TikTok and other spend is entered by hand per platform and period, which gives a cost per conversion per platform, labelled CAC in the dashboard, and one blended return on ad spend. A Models view compares five rule-based models per ad platform: first-touch, last-touch, linear, time-decay and position-based.

Where Arktis does not fit

If you need a data pipeline, Segment or a tool like it is the right purchase and Arktis is not a substitute. Arktis does not route events to other tools, send conversions to Meta's Conversions API or Google enhanced conversions, sync audiences to ad platforms, or load data into your warehouse. It identifies visitors per browser and does not join one person across devices, which Segment's identity resolution on the CDP plans is built to do. And it has no free plan, while Segment Free covers 1,000 MTUs at no cost.

The two can also run side by side, Segment feeding your other tools and Arktis answering which campaigns brought the orders.

Check it on your own store

To see conversions per campaign from your own orders, start the 7-day Growth trial, or compare the tiers on the pricing page. For the wider picture, read the modern e-commerce analytics stack and server-side tracking for e-commerce, or model tool costs on your own traffic with the analytics cost calculator.

Sources

Twilio Segment: Connections pricing, plans, allowances, overage table, billing terms and FAQ, accessed 16 October 2026 from Sweden, shown in US dollars

Twilio: customer data pricing, Connections versus the Customer Data Platform and its contact sales route, accessed 16 October 2026

Twilio Help Center: how MTU overages are billed on the monthly Team plan, tiered rates and the 50,000 MTU example, accessed 16 October 2026

Twilio Help Center: what happens if you exceed MTU or API limits, data flow and overage by plan, accessed 16 October 2026

Segment docs: MTUs, throughput and billing, MTU definition, causes of MTU spikes, throughput and Business tier features, accessed 16 October 2026

Segment docs: billing and account FAQs, trial, billing cycle, cancellation, refunds and Free plan lock rules, accessed 16 October 2026

Segment docs: common fields, the campaign object and UTM fields, accessed 16 October 2026

Segment docs: Segment's role in attribution, attribution happening outside Segment, accessed 16 October 2026