Relevant to: Demand Acceleration Platform | Content Syndication | Event Lead Management | Social Integrations | Webinar Integrations
This article explains the field types, groupings and validation settings that are available to use in the Fields tab. For more information about configuring your Campaign/Source fields, see Fields tab.
| The options here will differ according to which Campaign/Source type and channel you are using. For more detailed information, reference the specific channel section. |
In this article:
Field Types
The table below describes the types of fields available in the Custom option in the Field Creator sidebar and the corresponding validations that can be applied to set up the Campaign/Source Fields tab.
| Field type | Description | Available validation | Validation description |
| Number |
Input value consists of numeric characters. |
Digits - Minimum and/or Maximum |
Checks that the value consists of a specified number of digits. |
| Value - Minimum and/or Maximum | Checks that the value is within a specified range. | ||
List |
Input must match allowed value(s) from the assigned General List or System Locked List. |
Set Lead Cap |
Limits the number of leads that can be accepted per list value. Any leads submitted over the limit will be rejected. This can be used with a General List. |
|
Single-Select |
Input value must match one item on the associated list's Allowed Values. | ||
|
Multi-Select - |
Any - Multiple input values permitted, must match associated list's Allowed Values. All - All associated list's Allowed Values are required. |
||
| Email |
Input value is an email address. |
Email Format |
Checks that the value is structured with email syntax (eg. name@domain.com). |
|
Email Format & Mail-Server Lookup |
Checks that the value is a valid email address that messages can be sent to.
|
||
|
Use Domain List |
Allows or blocks (exclude) leads with email addresses using a domain on the associated Domain List. |
||
|
Suppression List |
Blocks leads with email addresses on the associated Suppression List. | ||
|
Set Domain Lead Cap |
Limits the number of leads that can be accepted from any domain. Any leads submitted over the limit will be rejected. This can be used with or without a Domain List. | ||
| Phone |
Input value is a phone number. |
None |
Value not validated, can be submitted with any characters (eg. (+1) 234-567-8910). |
|
United States |
Checks that the value is a valid phone number within the US or Canada.
|
||
|
International |
Checks that the value is a valid phone number within the corresponding country, including the US and Canada.
|
||
| Text |
Input value consists of alphanumeric characters. |
Character Range |
Value must have a minimum and/or maximum number of characters. |
|
Text Value |
Allow Values - Value must contain one of the values on the assigned General List. Disallow Values - Value must not contain any of the values on the assigned General List.
|
||
| Date |
Input value is a date. |
Date Format |
Value will be required to be formatted as either:
|
|
Date Validation |
Rejects leads that are older than a specified number of days.
|
Field Groups
The table below describes the field groupings available in the Groups option in the Field Creator sidebar that can be used to add validations and set up the Campaign/Source Fields tab.
| Field Group | Description |
| Address Block |
A field grouping, which contains the fields Street 1, Street 2, City, State, Zip, Country.
Enable Address Validation checks that the value is a valid address within the corresponding country. See Address Validation for more details. |
| Or [This feature is coming soon] |
Checks that lead data uploaded into the fields within the Or field grouping pass through the applied Or Logic acceptance criteria. Or Logic is a field grouping validation that can be used to set conditional lead acceptance criteria based on values uploaded into two individual fields.
|
| All |
Currently this feature is not functional. |
Standard Fields
Standard Fields enable the Demand Acceleration Platform to streamline reporting and provide more robust data within the Insights Dashboard. Using Standard Fields can also help keep Field Names consistent for your most frequently used fields, resulting in more efficient Campaign/Source builds and reporting.
Standard Fields are listed and available to add to your Fields tab from the Field Creator sidebar. You can identify a standard field in use by the blue shield icon.
Existing custom fields can be assigned or reassigned to Standard Fields from the My Campaigns page and/or Sources pages. Click the options menu on the individual Campaign/ Source and select Map Standard Fields.
This will display the Map Standard Fields modal, where you can map or remap your existing fields to the corresponding Standard Fields. Each Standard Field may only be mapped once and any other fields can be mapped to the Custom Field option.
If you open a Campaign/Source that was created prior to the implementation of Standard Fields (June 2020), the Map Standard Fields will appear automatically to prompt you to assign those existing fields.
The table below describes the Standard Fields available, the intended use and default field type.
| Standard Field | Description | Default field type |
| First Name |
Input value is a first name. |
Text * |
| Last Name | Input value is a last name/surname. | Text * |
| Email Address | Input value is an email address. | Email * |
| Phone Number | Input value is a phone number. | Phone * |
| Asset Title | Primarily used for Content Syndication, the input value is the title of a content asset downloaded by the lead. | Text |
| Company Name | Input value is a company name. | Text |
| Industry | Input value is a company's industry. | Text |
| Job Title | Input value is a job title (eg. Director of Marketing Operations). | Text |
| Employee Size | Input value describes the size of a company. | Text |
| Opt In | Input value indicates whether a lead has consented to opt-in to follow-up or marketing activity. | Text |
| Street 1 | Input value is the first line of an address. | Text * |
| Street 2 | Input value is the second line of an address. | Text * |
| City | Input value is a town or city. | Text |
| State |
Input value is a US State or region.
|
List |
| Zip | Input value is a zip code or postcode. | Text |
| Country |
Input value is a country.
|
List |
| Company Revenue | Input value indicates the annual revenue of a company. | Text |
| Job Level | Input value indicates a level of seniority (eg. Mid-senior management). | Text |
| Job Role | Input value broadly describes a job role (eg. Marketing Operations). | Text |
| Address Block |
A field grouping, which contains the fields Street 1, Street 2, City, State, Zip, Country.
|
Group * |
|
* The field types of these Standard Fields are locked and may not be updated. |
||
Validations
Within the Fields tab, certain field types (Email, Phone and Address Block) have additional levels of validation that may be added. When applied, lead processing will occur and the data within these fields will be sent to our validation provider to be evaluated.
|
Validation does not guarantee that the email address, phone number, or address in question belongs to the lead it is associated with - it verifies that the contact detail itself is real and functional. |
Email Validation
Validation can be applied to an Email field type by checking the box for Email Format & Mail-Server Lookup under the Validations section of the field settings sidebar. See Fields tab for instructions.
The email validation service provider checks the following information about each email and determines a deliverability score. During this validation, no email is sent to or from the email address in question.
- Syntax check - Confirms valid email format contains an '@' symbol, a recognizable domain and doesn't contain characters that are not acceptable in email addresses.
- Domain Name System (DNS) check - Verifies the domain exists and has a valid mail exchange (MX) record in order to relay mail.
- Simple Mail Transfer Protocol (SMTP) check - Confirms ability to communicate with the email server, if it will accept mail from any address and if it will accept email from a specific address.
- Mail servers linked to spam and email-mining tools may respond in defensive ways (eg. responding very slowly, providing unhelpful or missing data).
- As such, our validation service provider was designed with this in mind.
After collecting all relevant information, the email is assigned a deliverability score that determines whether the email in question is considered valid or invalid.
An invalid email result will cause the lead to be rejected within the Demand Acceleration Platform and display the Disposition Code REJECT_LEAD_INVALID_EMAIL. See Conversions for more details on Disposition Codes.
| General email validation information |
Bounced emailsMany corporate IT departments have defensive mechanisms in place for their email servers because there is an increased risk that opening spam email may cause network wide issues. As such, there are scenarios where email validation providers might consider an email valid but when an actual email is sent from your Marketing Automation or CRM system it might bounce or be rejected. Reasons for bounced emails may include:
Catchall domainsThis is a setting corporate IT departments can enable so that no email using their domain is rejected, even if that exact email address doesn’t exist. These domains are more likely to return a false positive validation but does not mean that email validation providers are not effective. If you attempt to email a catchall domain, you may find that your emails are bounced and return a 550 error. In this instance it is advised to first speak with your Integrate Customer Success Manger. It may be determined that the catchall domains need to be removed from your target account list - your support contact for your Marketing Automation or Email Service Provider should be able to provide instructions on how to make these adjustments. Additional reading about catchall domains: |
Phone Validation
Validation can be applied to a Phone field type by selecting the radio button option for United States or International under the Validations section of the field settings sidebar. See Fields tab for instructions.
The phone validation service provider checks the following information about each phone number, depending on the option selected.
United States - includes both the United States and Canada.
- Checks for a complete phone number and valid phone format.
- Most typical phone formats are acceptable (eg. 555-123-4567 or 5551234567).
- A country code is not required, just an area code.
- Identifies the phone carrier that owns the number and confirms it is valid and active.
International - works for all countries, including the United States and Canada.
- Checks for a complete phone number and valid phone format.
- Most typical phone formats will work (eg. +44 1234 567890 or +32 012-34-56-789)
- A country code is required.
- Identifies the corresponding Country field value, confirms the phone number uses a valid number sequence within the associated region, and checks the number is valid and active.
- Requires the use of our Standard Country field or Address Block.
- Most country value formats are acceptable (eg. full country names or ISO Alpha-2 or Alpha-3 character country codes).
After completing all checks for the selected option, the phone number in question will be considered valid or invalid. Valid phone numbers will be passed through the Demand Acceleration Platform in the same format they were received.
An invalid phone result will cause the lead to be rejected within the Demand Acceleration Platform and display the Disposition Code REJECT_LEAD_INVALID_PHONE. See Conversions for more details on Disposition Codes.
Address Validation
Validation can be applied to an Address Block field grouping by checking the box Enable Address Validation under the Validations section of the field settings sidebar. See Fields tab for instructions.
The address validation service provider checks the following information about each address to determine if it is a real mailable address. It is typically recommend to apply this validation if you intend to send mail to leads received.
- Confirms valid address format is used including a Country field value.
- Standard Country field must be set as required to ensure a value is present.
- Most country value formats are acceptable (eg. full country names or ISO Alpha-2 or Alpha-3 character country codes).
- Checks the USPS database (United States) or the local postal service database equivalent within the associated region (if available) to confirm a valid address within that region.
- Address data can be uploaded in English or the localized language.
- Validation results are proportional to the match between the address data uploaded and the address record within the local database (which varies). To receive the most accurate results, we recommend setting these fields within the Address Block to required: Street 1, City, State, Zip.
An invalid address result will cause the lead to be rejected within the Demand Acceleration Platform and display the Disposition Code REJECT_LEAD_INVALID_ADDRESS. See Conversions for more details on Disposition Codes.
Recommended Reading