Meet Terminus Hub
The next generation of Terminus, designed from the ground up for the most advanced campaign governance.
Already use Terminus
You are on Classic. It is here to stay.
New to Terminus
Start on Hub. This page is what you get.
What Terminus Hub does
Governance models
The heart of the system, fully versioned: fields, picklists, taxonomies, dependencies, and validations. Define the rules once and they apply everywhere.
How governance models workScoped workspaces
Give each team, agency, or region exactly what it can build: a slice of the governance model, scoped by region, source, and medium.
Building tools
Flexible, fully customizable builders for every way teams work: Quick, Form, and Grid modes, with bulk building.
Submission pipeline
Every submission, whether through the builders, API, or bulk import, runs through validation and approval (if enabled), so all data is rigorously checked before it becomes a record.
How validation runsOne clean dataset
Every workspace rolls up into one governed dataset: a single, consistent source of truth.
Analytics
Short-URL analytics: clicks, QR scans, and your own custom dimensions like Product and Goal, broken down however your business reports.
See the analyticsClassic and Hub, side by side
Classic is the UTM builder and link manager you know. Hub adds governance for whole teams. Here is how they line up.
| Classic | Hub | |
|---|---|---|
| Best for | Marketers and teams of any size standardizing UTMs | The same people, with governance highly optimized for medium to large teams |
| Rules live in | Projects you share with your team | A versioned governance model, with per-workspace control over which values each team can use |
| Enforcement | Naming conventions and enforced rules | Typed fields, picklists, and taxonomies grouped into forms |
| Field types | Four | Thirteen, including concatenation, auto-number, and computed URLs |
| UTM strings | Auto-generated in the URL builder | Computed from governed, validated inputs as a tagged URL |
| Building | URL builder, short links, QR codes, extensions | A visual designer for the model itself, then Quick, Form, and Grid modes for daily entry, with live validation |
| Spreadsheets | Limited compatibility | Paste straight into the grid, or round-trip a CSV through Excel or Google Sheets |
| Workflow | Rules enforced as you build | Draft, review, and approve, with comments and immutable records |
| Where records live | Inside the project that made them, searchable but never consolidated | One account-level table across every workspace, filterable by any field |
| Reporting | Basic reporting | Clicks, QR scans, UTM breakdowns, geo and device, per-link stats, plus your own custom dimensions like Product, Goal, and more |
Both products are live today. Sign in to Classic or sign in to Hub.
Where Hub goes further
Hub keeps Classic's enforcement model and makes the rules, field types, building tools, and analytics behind it dramatically richer.
Thirteen field types, not four. Concatenated campaign IDs, auto-numbering, and dropdowns that depend on several other fields rather than one parent. Text fields get real validation: patterns, casing, and uniqueness across every record.
One picklist, not a dropdown per parent. A hierarchy such as region and country lives in a single picklist you edit like a spreadsheet. Classic needed a separate dependent dropdown for every parent value, which is most of what made a convention tiring to maintain.
Workspaces in place of projects. Assign taxonomies to a workspace and control which dropdown values that team or agency is allowed to use, without duplicating the model. Light enough to run one per region, brand, or client.
A designer, and three ways to enter. Build the model in a visual designer. Then, for daily work, a guided form, a quick mode, and a full spreadsheet grid. Validation runs as you type in all three.
A grid that behaves like a spreadsheet. Copy and paste straight in, or download a CSV, edit it in Excel or Google Sheets, and upload it back. Classic's architecture only ever allowed limited spreadsheet compatibility.
Analytics that reach your own fields. Clicks on a short link break down by the fields the link was built from, not just device and referrer. The architecture connects a click back to the field it came from, even when that field is only one part of a UTM value.
Every link in one table. Records from every workspace sit in a single account-level view you can group, filter, sort, and export whole. In Classic they stay inside the project that created them: global search finds one, but nothing brings them together.
Records pushed to your systems. Point a webhook at your CRM or data warehouse and every approved record lands there, signed and delivered once, then again whenever it changes. Instead of you polling our API, we call you. Webhooks are the first connector, and the architecture was built to take more.
Built-in workflow and audit. A draft, review, and approve pipeline with comments, notifications, and immutable approved records makes governance easy to run and audit.
Built to extend
Because Hub treats everything as a structured, versioned governance model, new field types, analytics dimensions, and integrations can be added on top of the same foundation, the kind of thing that wasn't easy to do in Classic.
And there's far more under the hood: extensive data processing pipelines and a robust architecture built to support evolving interfaces, APIs, and AI/LLM compatibility. Hub is designed to be the backbone of every campaign, from launch to precise analytics reporting.
Why we built something new
Classic began as a UTM builder and grew, over the years, into a mature convention-management system that teams large and small have trusted for over a decade. So why build something new instead of evolving it?
Because at its heart, Classic is a URL builder, and the best ideas we've gathered over the years bend awkwardly around that.
So we asked ourselves a different question: if we built Terminus today, knowing everything we now know, what would it look like? Hub is the answer, with a foundation built for richer rules, deeper analytics and integrations, and the flexibility to handle nearly every requirement we've come across.
There was a second reason to build something new rather than reshape Classic: we weren't willing to break the workflows people rely on. Many customers have built years of history and daily habits on Classic. Reshaping it underneath them would be like turning a dining chair into a recliner while someone is still sitting in it. Nobody would enjoy the process, and the result wouldn't be what anyone wanted.
The responsible path was to build the next generation alongside Classic, not on top of it.
Hub is the product of more than a decade in campaign tracking, years of gathering requirements from real teams, and a long, deliberate build. We understand this problem deeply, and we've put our heart into making it best-in-class. We can't wait to show you what's inside.
For existing Classic customers
What happens to Classic?
Nothing changes for you. We'll keep maintaining, supporting, and improving Classic. Stay as long as you like, and when you're ready to explore Hub, moving your projects and conventions over is supported, and we'll help you do it.
And if you ever asked us for a feature Classic couldn't support, there's a good chance Hub has it now. Check with us.
Two products, two sets of addresses
| Terminus Classic | Terminus Hub | |
|---|---|---|
| Sign in | app.terminusapp.com | hub.terminus.app |
| Documentation | docs.terminusapp.com | docs.terminus.app |
| API reference | terminusapp.com/apidocs | docs.terminus.app/api-reference |
| Support | support@terminusapp.com for both products | |
Ready to see Hub?
Start from a production-ready template, or bring your own conventions. And if you have questions first, we read every email.