FastLinkIt

Custom contact fields

Contacts & Mailingcontacts3 min read

Available on Professional and Unlimited plans

Define your own fields beyond the built-in ones (email, name, company, phone, etc.) and target them in segment rules and mailing personalization.

Field types

Type Editor control Use for
Text single-line input one-off labels (job code, role)
Number numeric input revenue, score, account size
Date date picker renewal date, anniversary
Yes/No dropdown (true/false/empty) flags
URL URL input with validation LinkedIn, GitHub, blog
Email email input with validation secondary email
Select-from-list dropdown with CSV options tier (Gold/Silver/Bronze), event source

Defining fields

Go to Contacts → Custom fields (/contacts/custom-fields).

  1. Click Add field.
  2. Fill in:
    • Name — must be unique within your account / org
    • Type — picks the editor control above
    • Options (only for Select) — comma-separated list of dropdown values
    • Required — when on, contact-edit blocks save until the field is filled
    • Sort order — positions the field among others on the contact editor
  3. Save. The field appears immediately on every contact's edit page under a Custom fields card.

Editing values

Open any contact (/contacts/{id}/edit). The Custom fields card auto-renders the right control for each definition:

  • Empty value = unset (the row in ContactCustomFieldValue is deleted, not stored as empty string).
  • This matters for segments: customField:Tier isSet matches only contacts with a value; isNotSet matches the rest.

Using in segments

In the segment rule builder, the Field dropdown lists every custom field under a Custom fields group. Operators per type:

  • Text / URL / Email / Select / Number / Date — equals, contains, isSet, isNotSet
  • Yes/No — equals true, equals false

Worked example — track which trade show every lead came from

Goal: measure which event delivered the best leads.

  1. /contacts/custom-fieldsAdd field.
  2. Type: Select-from-list. Name: Source Event. Options: 2026-Berlin, 2026-Paris, 2026-Lisbon.
  3. After each show, CSV-import the badge scans (the field auto-renders as a dropdown on every contact).
  4. Six months later, build a segment: Source Event equals 2026-BerlinRun preview → 87 contacts.
  5. Send a follow-up to that segment, compare open / click rates with the Paris and Lisbon segments.
  6. Concrete data for next year's event budget.

Worked example — partial sync from a CRM

Goal: keep one custom field (Tier) in sync with an external CRM.

  1. Define the Tier select field with options Gold / Silver / Bronze.
  2. From the CRM, push updates via POST /api/contacts/bulk with the field set per contact.
  3. Use Tier equals Gold as a segment rule for VIP-only campaigns.
  4. Null fields on update mean "leave existing alone", so partial syncs don't accidentally clear tiers.

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.
Please retry or reload the page.

The session has been paused by the server.

Failed to resume the session.
Please retry or reload the page.