Create and use custom fields
Store additional contact data for forms, segments, imports, and campaign personalization.
How custom fields work
A custom field defines a named piece of contact data and can be attached to one or more lists. Field types support simple text as well as controlled values and dates.
Required fields must contain an acceptable value when a contact is saved through a workflow that enforces the field.
Where custom fields are used
- Map imported file columns to custom fields.
- Add the selected fields to subscription web forms.
- Filter list-based segments by field value or date.
- Insert the corresponding shortcode into subjects, content, sender values, or custom headers.
Planning a custom field strategy
Before creating a long list of custom fields, decide what each one will actually be used for: personalization in subject lines and body copy, segmentation logic for targeted sends, or reporting. Fields that exist “just in case” tend to stay empty, which weakens both personalization and any segment built on top of them.
Keep naming consistent across lists so the same piece of contact data, such as a renewal date or plan tier, always lives in a field with the same name and type. This matters most once you start importing files from multiple sources, since mismatched field names lead to data landing in the wrong place or not mapping at all.
Custom fields across the platform
Custom fields are not limited to storage; they connect directly to personalization, segmentation, and forms. A date-type field can drive a segment for an upcoming renewal, the same field can trigger a reminder campaign through triggers, and its shortcode can appear directly inside the email copy so the message reads as individually written.
Required fields are worth using sparingly, since they can block a web form submission or import row if the value is missing or improperly formatted. Review your custom fields periodically and retire ones that are no longer referenced by any segment, form, or campaign, so the contact editing screen stays easy to work with.
Frequently asked questions
- Can one custom field be used across multiple lists?
- Yes, a custom field can be attached to more than one list and referenced consistently across them.
- What happens if a required field is left blank on import?
- A workflow that enforces the field will reject the row until an acceptable value is provided.
- Can custom fields drive both segments and personalization?
- Yes, the same field can filter a segment and also resolve as a shortcode inside campaign content.
Was this guide enough?
Contact support if your screen or result is different.