What a custom field does

A custom field is one piece of data you keep on every contact — utm_source, plan_tier, signup_date — beyond the email, the name and the other standard details. It is defined once for the whole organization: every contact in every list can carry a value for it, or none.

Where you create one

In Settings → Custom fields. The owner and the admins of the organization create, rename and delete fields; the other members see the list but cannot change it. A field has three parts:
PartWhat it isCan it change?
LabelThe name people read, UTM sourceYes, at any time
KeyThe name the data is stored under, utm_sourceNo, fixed at creation
TypeText, number, date or yes/noNo, fixed at creation
The key and the type never change because values are stored under them: renaming a key or switching a type would silently orphan or break every value already recorded. To change either, create a new field.

The key

  • Lowercase letters, digits and _, starting with a letter, 40 characters at most: utm_source is valid, UTM-Source and 2nd_source are not.
  • Unique within the organization.
  • Some keys are taken by the details every contact already has, and are refused: email, first_name, last_name, phone, birth_date, locale, country, status, notes, tags, id, list_id, organization_id, source, source_label, created_at, updated_at, optin_at, optin_ip, confirmed_at, confirmed_ip, unsubscribed_at, unsubscribe_token, custom.

The four types

TypeWhat it accepts
TextUp to 1,000 characters. Spaces at both ends are removed.
NumberAny finite number, decimals included.
DateA date, 2026-03-14, or a date and time with its time zone, 2026-03-14T09:30:00+01:00. Dates are kept in UTC; a date and time without a time zone is refused rather than guessed.
Yes/noYes or no.
An empty value means "no value": an empty text is never stored as a blank, and an empty number never becomes 0.

Limits

An organization has at most 50 custom fields. The counter next to the list shows how many you use. The label is required and holds up to 100 characters; two fields may share a label, never a key.

Deleting a field

Deleting a field erases its value on every contact, in every list, at once. It is final: there is no undo, and creating a field with the same key afterwards starts empty.