Skip to main content
A field is one piece of campaign metadata in a governance model, such as Campaign Name, Source, or Short URL. Think of fields as the columns of your taxonomy: you define each field once, then place it into one or more taxonomies, where it becomes a column people fill in. Every field has a type, chosen when you create the field. The type decides how the value is captured, which settings you can configure, and whether the field is entered by a person or computed by Terminus Hub. The type cannot be changed after the field is created, so pick it deliberately.
Fields split into two groups. Entered fields are filled in by whoever makes a submission. Computed fields are generated by Terminus Hub from other fields or from system rules, so submitters never type their value directly.

​
Field type matrix

There are 13 field types. Four are entered, nine are computed. Short URL is listed as both because its slug can be auto generated (computed) or typed by a submitter (entered), depending on its slug mode. See the Short URL page.

​
Browse the field types

Text

Free text with optional length, character, and case rules.

URL

A web address; the base for Tagged URL and Short URL.

Date

A calendar date rendered in a format you control.

Dropdown

A choice from a picklist, with optional cascading.

Concatenation

Joins other fields together with a separator.

Auto-fill

Derives a value from other fields, with transforms and conditions.

Tagged URL

A base URL with query parameters appended.

Short URL

A short redirect link over a destination URL.

QR code

A QR code generated from another field.

Auto number

Sequential numbers, padded to a fixed width.

Random

A random string of a length you set.

Constant

A fixed value, identical on every record.

Terminus ID

A unique identifier generated per record.

​
Settings shared by every field

Beyond the type-specific settings, each field carries a small set of shared attributes:
  • Name. The display name. Required, and unique within the governance model.
  • Description. Help text shown to submitters under the field.
  • Required. A submission with this field blank cannot be approved. Computed fields are always required, and the toggle is locked.
  • Hidden. Only computed fields can be hidden. A hidden computed field still generates its value, but does not appear in the submission form.
  • Prefix and suffix. Literal text wrapped around the value. Not available on URL, Tagged URL, Short URL, QR code, or Terminus ID fields.

​
Reusing a field across taxonomies

A field is defined once and then referenced into a taxonomy, where it gets a position (its column order). A taxonomy can override a field’s required and hidden flags, but only in the stricter direction: it can promote a field to required or hidden, never relax a field that the definition already marks required or hidden. For dropdown fields, a taxonomy can also filter which picklist options are offered. See field reference overrides for the override rules and option filtering.

​
Cross-field references stay in one model

When a field references another field (Concatenation, Tagged URL, Short URL, QR code, or a cascading Dropdown), the referenced field must live in the same governance model. A reference to a field in another model is rejected. A field that is referenced by a taxonomy cannot be deleted until you remove it from those taxonomies.