Custom fields

4 min read77
Copy for AI:

Custom fields store what the standard contact record does not cover β€” and your account creates them, with the name and type that make sense for your business. They serve two purposes: writing each person's value inside the email and splitting the audience in segments. They live in Audience β€Ί Contacts, under the Custom fields button.

Before creating one, check whether the standard record already has what you need: name, company, job title, website, phone numbers, address (with country, state and city) and social profiles already exist. Do not create a custom field to repeat one of them β€” the information would live in two places, and the import would link the column to only one.

Create a field

Click New field and fill in:

  • Field name β€” the label shown on the contact form and on the contact page. It can be changed later.
  • Key β€” the name used inside the email. Only lowercase letters, numbers and underscore, starting with a letter. It cannot be changed later.
  • Type β€” defines how the value is entered and validated.

At Casa Moura CafΓ©s, Renata created the Favorite coffee field with the key cafe_preferido, type Text, and the Last purchase field with the key ultima_compra, type Date.

The types

  • Text β€” a free single line.
  • Long text β€” a multi-line box, for notes.
  • Number β€” accepts numbers only.
  • Date β€” picked from a calendar.
  • Yes/No β€” a checkbox.
  • Option list β€” you define the Options (type in New option and click Add), and the contact can only have one of them. A value outside the list is refused, imports included.

The right type matters more in segments than on the form: it decides which conditions show up. Number allows "is greater than" and "is between"; Date allows "is before" and "in the last N days"; Text allows "contains" and "starts with"; Long text, being a paragraph, gets "contains", "does not contain", "is empty" and "is filled". Storing a date as Text keeps you from segmenting, say, who bought in the last 90 days.

Filling in the values

The fields show up in the Custom fields block of the contact form and as target columns in the import. There, a spreadsheet column whose header equals the field's key (or its name) arrives linked on its own: a cafe_preferido or Favorite coffee column lands straight in Renata's field. On the contact page, the values sit in their own card, with the names your account created.

Using it in the email

Write the key between double curly braces in the campaign's subject or body: {{cafe_preferido}}. Each recipient gets their own value β€” the customer who prefers Yellow Bourbon reads "A new lot of Yellow Bourbon is in". In the editor, your account's fields appear under See available variables, ready to copy.

A contact without the field filled in gets the snippet blank. To avoid a "A new lot of is in" use a fallback value after a bar: {{cafe_preferido|specialty coffee}}.

A word of caution about Yes/No: in the email, a ticked value comes out as "1", and an unticked one comes out empty. It is meant for segmenting, not for being written in the message.

Editing and deleting

  • The key never changes. Renaming it would make every campaign using {{cafe_preferido}} go out with the field blank, silently. Got the wording wrong? Adjust the Field name, which is free.
  • The type locks once there are values. The Usage column shows Has values or No values. Changing the type of a filled-in field would erase whatever did not fit the new type β€” so the screen does not allow it.
  • Deleting erases the field and its values across all contacts, with no undo. Campaigns still using the key start going out with the snippet blank.

Creating, editing and deleting fields is for Author, Manager, Administrator and the Owner; Viewer only looks.

Where to go next

  • Import contacts from a spreadsheet β€” fill in the fields of many contacts at once.
  • Segments β€” use the fields as conditions.
  • Campaigns β€” personalize the subject and body with variables.

In short: create the field with a key meant to last and the type your segments will need, fill it in through the form or the import, use {{key|fallback}} in the email, and remember that the key never changes, the type locks once filled and deleting erases everything.

Was this article helpful?