Skip to main content
A record is one approved campaign row in a taxonomy. Records are read-only: you browse, filter, group, and export them, but you never create or edit one directly. Every change to a record happens through a submission.

​
What it is

A record is a single approved campaign-metadata row that lives in a taxonomy inside a workspace. Records are the canonical, approved data the rest of the product reads from. Each record has:
  • A Terminus ID: a stable, permanent identifier in the form trm0 followed by lowercase letters and digits (for example trm0abc123def456ghi7). It never changes, and it is how other parts of the product (short URLs, analytics, update submissions) refer to the row.
  • A status: active or archived (a third state, deleted, is treated as gone and is hidden everywhere).
  • The value of every field in the taxonomy for that row, including computed fields.
Records appear only when a submission is approved. There is no way to create, edit, or delete a record on its own, in the app or over the API.

​
Record statuses

Archived records stay visible in the grid. Deleted records are hidden from both the grid and the API, so a request for a deleted record is not found.

​
The records grid

Records open one taxonomy at a time on a workspace’s records page, with the taxonomy picker in the breadcrumb. For browsing, filtering, saved views, export, and building or changing records, see Work with records. The reference points:
  • Columns follow the taxonomy’s field order in the last published version of its governance model, one column per field. The taxonomy name in the breadcrumb and the column names also come from that version, so a rename or a new field shows here only after you publish it. A field that a later publish removed stays as a column, after the current ones, while existing records were approved under a version that had it. The breadcrumb shows the total record count, or “shown of total” when a filter or search reduces the rows.
  • Load limit: the grid loads up to the first 1,000 records of a taxonomy. CSV export pages through the full dataset.
  • Dropdown labels are frozen at approval. A dropdown column shows the label the option had when the record was approved. Relabeling or removing the option later does not change it. The API and outbound webhooks read the same stored label.
Some field types behave differently in the grid:

​
Saved views

A saved view stores a taxonomy’s column state (order, visibility, pinning, sort, grouping) and active filters under a name. Column widths are restored when you apply a view but do not count as a change. The last view you used in a taxonomy is re-applied when you return.
Saved views are stored in your browser only. They do not sync across browsers, devices, or teammates, and clearing your site data or signing out removes them.

​
CSV export format

Download CSV exports every record in the taxonomy, not just the rows loaded in the grid.
  • Columns: only the currently visible columns, in their current order.
  • Rows: the active filters and sort apply.
  • Empty cells become blank values.
  • Filename: the taxonomy name, the active saved view’s name if one is applied, and the date, for example email-campaigns-q4-launch-2026-06-23.csv.

​
Changing records

Records are read-only. Edit, Clone (Clone URL for a taxonomy that builds links), and Delete on the records page, and the Build URL or New record button, all start a submission. Nothing changes until that submission is approved. See Work with records.

​
Gotchas

  • Records are read-only. You can’t create, edit, or delete one directly, in the app or the API. Every change flows through a submission. The buttons on the records page just start one.
  • Saved views are browser-local. They live in this browser only, don’t sync across devices or teammates, and are lost if you clear site data or sign out.
  • The Terminus ID never changes. It is assigned when the record is created and stays fixed for life. Short URLs, analytics, and update submissions all rely on it.
  • Archived stays visible; deleted disappears. Archived records remain in the grid and the API. Deleted records are hidden everywhere and return not-found.
  • The grid shows up to 1,000 rows. For a larger taxonomy, the grid is a window onto the first 1,000 records. CSV export is the path that loads everything.
  • CSV reflects the screen, not the raw schema. It exports only the visible columns and the active filters and sort, so hiding a column or filtering changes the output.
  • Some columns can’t be grouped. Constant and QR-code columns can’t be sorted, filtered, or grouped; multi-select dropdowns and unique fields can’t be grouped.
  • Labels don’t follow picklist edits. A record keeps the dropdown label it was approved with.
  • Work with records: build, clone, edit, and delete records, and use saved views and export.
  • Submissions: the flow that creates and updates records.
  • Analytics: click reporting for the short URLs on your records.
  • Terminus ID: the stable identifier on every record.
  • Workspaces: records are partitioned per workspace.