Skip to main content

Custom contact fields

Custom fields store data that does not fit name, phone, email and tags: birthday, city, plan, loyalty tier, whatever your business tracks.

Who can do this

  • Owner
  • Admin

Agents see the values on a contact but cannot define fields.

Add a field

SettingsContact fieldsAdd field.

Each field has:

  • Label: what people see, for example "Birthday".
  • Key: the storage key and the CSV column header. Generated from the label (lowercase, underscores) and worth keeping stable.
  • Type: one of these.
TypeStoresShown as
TextFree textText box
NumberNumbersNumber box
DateA dateDate picker
SelectOne of a fixed list you defineDropdown
Yes / NoTrue or falseSwitch

Reorder and edit

Use the up and down arrows on each row to change the order. The order here is the order the fields appear on the contact form, so put what your team fills in most at the top.

Edit changes the label, type or options. Delete removes the field and its stored values.

Import fields from Shopify

If a Shopify store is connected, an Import from Shopify button appears. It creates field definitions mapped to Shopify customer data, so those values fill themselves in when customers sync.

Shopify-sourced fields show a Shopify badge and are read-only on the contact form, with "Synced from Shopify" underneath. Editing them by hand would be overwritten on the next sync, so the app does not allow it.

See Shopify customer sync.

Custom fields in CSV import and export

The field key is the CSV column header. Once a field exists, that column is recognised on import and included on export.

The built-in import columns are name, phone (required), email and tags (semicolon-separated). See import and export contacts.

Working with contacts
The contact list, filters, bulk actions and the contact form.
Shopify customer sync
Bring Shopify customers into Contacts.