Segment is hired to collect events once from your site and app and deliver them to the other tools and a warehouse. It is the hardest kind of tool to rate as easy, because everything downstream depends on it. Below: what the vendor publishes, what replacing the job takes, and how to move without losing data.
It sits in the middle. Each new marketing or analytics tool was connected through it rather than through new code, so years later it feeds more places than anyone remembers.
That is a fair reason to keep a pipeline. It is also why the first step is a map of what it feeds, not a quote for something cheaper.
Only alternatives we have checked. An open-source project is listed with the license its repository reports, on the date shown; one whose license could not be read as a single standard id is not offered as open source. Read the license guide before running any of them.
| Alternative | Kind | License | Read from |
|---|---|---|---|
| A small event forwarder for the few destinations the company actually sends to | Custom build | — | Written for the one job |
Each feature below is what the product's own page or README says, linked to where we read it on the date shown. Pros and cons are limited to what those pages state and to what the path itself changes. We do not rank products on quality.
A customer data pipeline sits between your product and the tools that want its events. The question is how many of those tools you actually use. A pipeline feeding two destinations is a different decision from one feeding twenty.
Cutting it is rarely the saving. The saving is usually in the plan size and in destinations that no longer need the data. Settle that first.
Samples are made up and are not Segment's prices. Type in the figures from your own invoice or order form.
Build a small tool or keep paying for one: the cost of each over your horizon and the month the build breaks even.
Paid seats against seats in use: what the idle ones cost a year, and what you save by right-sizing at renewal.
Arithmetic only, not tax, accounting or legal advice. Check the figures against your own order form.
In outline:
List every source, every destination and every transformation or filter, and who owns each one. Retire destinations nobody reads.
Pick the replacement path, whether direct sends to the few tools that remain or a small forwarder, and build one destination first.
Send to both paths for a month and compare event counts per destination. Explain any gap before trusting the new path.
Move the remaining destinations one at a time, remove the old tracking library, export your configuration, and end the plan inside the contract's notice window.
A replacement is written from scratch for the destinations a company actually sends to, with no copied code, interfaces or wording from Segment or from anyone else. It starts from the list of destinations and the tracking plan, not from the vendor's catalog.
It is a project, not a switch: every destination has its own format and its own failure modes, and a mistake silently drops data from ads or reporting. Run it beside the existing pipeline and compare counts before cutting over.
Run the vendor report for QuickBooks Online or Xero, then open the free audit.
General information, not legal advice. See cancelling without penalties. Last reviewed Oct 25, 2026. Product names belong to their owners and are used only to identify them.
Send us the export and see which lines are worth a second look. A connected version is planned. Segment is one of the lines worth a look.
Worked example. Type over it.
Result
| Year | Buy, cumulative | Build, cumulative |
|---|---|---|
| 1 | 9,000.00 | 8,040.00 |
| 2 | 18,000.00 | 10,080.00 |
| 3 | 27,000.00 | 12,120.00 |
Undiscounted, and it leaves out the vendor's price rises and your own overruns. A tool built for one job is not the whole product: list what you would lose before you count the saving.
Worked example. Type over it.
Result
“In use” is your call: last sign-in in the past 30 or 90 days from the vendor's admin report. A seat for someone on leave is not idle.