How are Custom Fields formatted in Outreach?

Created by Aye Myat, Modified on Mon, 9 Feb at 11:01 PM by Alsabana Sahubarali

Applies To

Outreach Admins
Outreach Users
Custom Fields
Prospects
Accounts
Users
CRM Plugin

Answer

Prospect, Accounts and Opportunities objects

The custom fields of these 3 objects support various formatting:

Plain text
Numerical
Percentage
Currency
Date
Date/Time
URL
Phone Number
Single-Value pick-list and Boolean (3-value pick-list)

When a custom field will be configured with a specific type, the data they contain, let’s say it is a date or a numerical, will be referenced with filters such as "Before", "After", "Greater Than", or "Less Than." Each data type has its own filters and operators in the List View pages.

When a custom field on a Prospect, Account, or User contains a URL that you want to reference with a variable in your outbound messaging, simply inserting the variable for that custom field will insert the text of the link, it will not be a clickable link. To insert a variable as a clickable link, simply use the "Insert Link" function and, define your Link Text and add the appropriate variable in the "URL" field, as shown below.

When a custom field will be configured with a specific type, the data they contain, let’s say it is a date or a numerical, will be referenced with filters such as "before", "after", "greater than", or "less than." Each data type has its own filters and operators in the List View pages. More on this below.

Custom Field Filter Options

Boolean	Is true Is false
Currency	Is Is not Between Greater than or equal to Less than or equal to Is empty Is not empty
Date	At Between Is empty Is not empty Last 7 days Last 30 days Last 90 days Last month This month Today Until today Year to date
Date/Time	At Between Is empty Is not empty Last 7 days Last 30 days Last 90 days Last month This month Today Until today Year to date
Numerical	Is Is not Between Greater than or equal to Less than or equal to Is empty Is not empty
Percentage	Is Is not Between Greater than or equal to Less than or equal to Is empty Is not empty
Phone Number	Is Is not Starts with Is empty Is not empty Contains Does not contain
Picklist (Single select)	Is Is not Is empty Is not empty
Picklist (Multi Select)	Is Is not Is empty Is not empty
Text Field	Is Is not Starts with Is empty Is not empty Contains Does not contain
URL	Is Is not Starts with Is empty Is not empty Contains Does not contain

Data Type Definitions

Type	Display value	*Stored value	Additional Information
Boolean	"True False (NULL) empty"	"true (but we also accept 1 via the API) false (but we also accept 0 via the API) (NULL) empty"
Currency	"Formatted number with thousand separator. (NULL) empty"	"Integer (-2,147,483,647 to 2,147,483,647) (NULL) empty"	The currency sign is stored separately, not as part of the value, but in the definition field of the CustomField.
Date	YYYY-MM-DD	Format: YYYY-MM-DD.	Time part will be stripped-of if present.
Date/Time	YYYY-MM-DDTHH:MM:SS (1985-04-12T23:20:50.52Z)	Format standardized by RFC3339	No conversion to UTC done.
Numerical	"Number (NULL) empty"	"Float (NULL) empty"
Percentage	"Same as numerical: Number"	"Float (NULL) empty"	The % sign is not stored as part of the value.
Phone Number	"Phone Number. (NULL) empty Example: Valid: Open image-20241105-102622.png Invalid: Open image-20241105-102645.png"	"We first validate the number and we do the following: We try to separate the main phone number from any extension by looking for parts separated by the letter 'x' (e.g., ""123-456-7890x3""). We check if the phone number starts with a plus sign ('+'), indicating an international format. If the phone number does not start with a plus, it uses the PhonyRails library to normalize the number based on the given or default country code. The sanitized phone number is parsed using to create a standardized format. If at the end, the phone number is valid, the final output will include: number: The phone number in a standardized format (e164 format). country_code: The international dialing code associated with the number, if available. extension: Any phone number extension found after an 'x'."
Picklists (single select / multi select)	"Field configuration level: The list of values for the picklists. (NULL) empty - if the configured field as a picklist does not have values. Record level: Single select: Single value from a list of values. (NULL) empty Multi select: Single or multiple values from a list of values. (NULL) empty"	More or less the same as the “display value” section.

Note 1: When you alter the definition of a custom field from one data type to another, it only alters the validation applied; it will not automatically warn you when there are existing field values that will subsequently fail validation. If you are planning on changing the data type definition, you must also plan to update the existing values to ensure the stored data will pass the new validation.

Note 2: If you remove a custom field definition, this does not automatically delete any stored content in the field. You will need to remove the values as a separate action.