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:| Part | What it is | Can it change? |
|---|---|---|
| Label | The name people read, UTM source | Yes, at any time |
| Key | The name the data is stored under, utm_source | No, fixed at creation |
| Type | Text, number, date or yes/no | No, fixed at creation |
The key
- Lowercase letters, digits and
_, starting with a letter, 40 characters at most:utm_sourceis valid,UTM-Sourceand2nd_sourceare 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
| Type | What it accepts |
|---|---|
| Text | Up to 1,000 characters. Spaces at both ends are removed. |
| Number | Any finite number, decimals included. |
| Date | A 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/no | Yes or no. |
0.