Skip to main content
Terminus Hub is where teams agree on the rules for their marketing campaign data and then put those rules to work. You design a governance model that says exactly what a campaign should look like: the fields to capture, the dropdown lists that constrain them, and the taxonomies that group fields into a form. People then fill in that form, you approve their entries into clean records, and Terminus turns each record into a short branded link and QR code whose clicks it tracks for you. The result is campaign metadata that is consistent by construction. Instead of policing UTM tags and naming conventions after the fact, you encode them once in the model. Every submission is validated against the published rules before it can become a record, so the data your reports and integrations read is already correct.
New here? Read key concepts for the vocabulary, then follow the quickstart to go from a blank account to your first short URL.

​
The core flow

Terminus Hub follows one path from rules to results. Five steps:
1

Define a governance model

Create a model and add the fields you need (a campaign name, a source, a destination URL, and so on). Back your dropdowns with picklists, then group the fields into one or more taxonomies, the forms people fill in. Key concepts defines each of these.
2

Publish a revision

Publish a revision to lock the model into an immutable snapshot. Forms and validation always run against the latest published revision, so you can keep editing the model without affecting anyone until you publish again.
3

Submit campaign data

In a workspace with a taxonomy attached, people click Build URL (or New record, when the taxonomy produces no links) and enter campaign data in the submission builder, one record at a time or many rows at once. Computed fields like tagged URLs fill themselves in as they type.
4

Approve into records

Clicking Create URL (or Create record) approves the submission straight away, or, if the workspace requires review, a reviewer approves it. Approved rows become records: structured, validated, read-only, and queryable.
5

Get short URLs, QR codes, and analytics

Each approved record can carry a short branded link (for example ter.link/aB3xZ) and a matching QR code. Terminus records every click and scan, then reports them in analytics broken down by your taxonomy’s UTM and campaign fields.

​
What you can build

Governance models

The container for your fields, picklists, and taxonomies. Author it once, publish revisions, export or import it as JSON.

Fields and field types

Thirteen field types, from free text and validated URLs to computed concatenations, tagged URLs, short URLs, and QR codes.

Picklists

Static lists, parent-to-child cascading lists, or lists sourced live from another taxonomy’s approved records (automated picklists, on the Business plan or higher).

Submissions and records

A governed form (in quick, form, or grid mode) for collecting data, and the approved records it produces.

Short URLs and QR codes

Branded short links and QR codes generated from a record’s destination URL, with every click and scan counted.

Analytics

Click and scan dashboards that group and filter by any field in your taxonomy, so the data you governed is the data you measure.

​
Templates and the API

You do not have to build a model from scratch. The templates gallery ships ready-made governance models for common cases (a simple UTM starter, B2B demand-gen, ecommerce, agency multi-client, and more). Preview one, then create a model from it in a click and customize from there. For programmatic access, Terminus exposes a versioned REST API. Authenticate with an API key, then read governance models, workspaces, submissions, and records. The API is read-only; submissions are created in the app. See the API reference to get started.

​
Where to go next

Key concepts

A short glossary of the core nouns and how they fit together.

Quickstart

The fastest path from sign-up to your first short URL.

Campaign URL Builder tutorial

Build a working governance model end to end, with picklists and computed fields.