Comparing Contact Fields and Labels
When deciding whether to use a Custom Contact Field or a Label, use the table below to compare their functionality:
| Custom Contact Fields | Both | Contact Labels |
| Store unique, contact-specific information (e.g., student ID, advisor name, URL) | Can be used to create Audiences | Apply a shared tag to a group of contacts (e.g., “Fall 2025 Cohort,” “Alumni”) |
| Values must match the selected data type (text, number, date, email, etc.) | Can be added or removed manually on an individual's Contact Profile | Same value applied to all contacts with that label (text type format) |
| Can be used in Scripts and Personalized Responses | Cannot be used in scripts | |
| Cannot be used to search for Contacts on the Contact page | Searchable on Contact Page | |
| Can’t be accidentally deleted if used in Scripts, Audiences, or Personalized Responses | Can be renamed or deleted at any time. Managed through the Label Manager | |
| Include options like adding to Escalation Emails or including in AI features |
Added via import or on an individual's Contact Profile |
|
| Can be unset for individuals or in bulk via integration (SFTP, Salesforce, etc.) |
Cannot be cleared for specific Contacts or removed via integration |
For Custom Contact Fields, a contact can have many fields, but each field can only hold one value.
For Labels, there is just one "Labels" field, but it can contain many values.
You can think of it like this:
-
Custom Contact Fields are like a set of labeled jars on a shelf — each jar is for one specific type of information (like “Advisor Name” or “Student ID”), and you can only put one thing in each jar.
-
Labels are like a bulletin board of sticky notes — you can add as many notes as you want, each note representing a label (like “Fall 2025 Cohort,” “Honors Program,” or “Interested in Events”).
Comments
0 comments
Article is closed for comments.