Field Types: Click on field type for more information.
- Date of Birth
- Debt Amount
- First Name
- Last Name
- IP Address
- Phone Number
- Street Address
- Text - List
- Zip Code
- About min & max field lengths
The Age field type is used to collect age values. It accepts a single number, and can be restricted by minimum and maximum age limits. The default minimum age is zero. Leaving the maximum age blank allows any age above the minimum. For example, to accept leads with an age of 18 or older, set the minimum to 18 and leave the maximum blank. To help prevent bad data, however, you may want to set a maximum age. (Note that the highest recorded human age is 122 years.)
The City field type is used for city names, and can ensure that data submitted is a valid city name. When city validation is turned on, LeadConduit Classic looks up lead data from a database of valid US city names. Leads with an invalid city name will be marked with "invalid City". Don't use this lookup if leads are expected from cities outside the U.S.
City fields can also be cross-validated with a Zip Code field in your campaign. When this is selected, city values that don't match the ZIP value (for example, a city of "Los Angeles" with a San Francisco ZIP code) will be invalidated.
The Date field type should be used to collect dates. This field type may also be used to ensure that data is in a specific date format (e.g., "mm/dd/yyyy"). Leads with invalid Dates are marked with "invalid Date". The available formats are listed below. If the date field is set to accept "any format", LeadConduit Classic will try to match the incoming data against these formats in the order they are listed here.
The "Date of Birth" field type allows you to collect birth date information in several formats. You may also select a minimum and/or maximum age allowable for your campaign.
Age is evaluated as of the day of the month, not by the entire calendar month. That is, if the date of birth is May 15, that person will be considered 0 months old until June 14th, then 1 month old until July 14, etc.
The age range will even accept negative values. This is useful in the event you are collecting a baby's due date and only want to accept leads from expecting mothers. Please note that in LeadConduit Classic, the prenatal age of an unborn child is considered 0 months for the month leading up to its birth. Therefore, when the prenatal age is 12 months or more, the number of months must be off-set by 1. In otherwords, to account for a prenatal age of 9 months, -8 must be used.
Leads with an invalid Date of Birth will be marked with "invalid Date of Birth". For valid formats, see the Date type.
The Debt Amount field was designed to accept both a single numeric value (ie $5000) and a range ($5,000 - $10,000) representing the amount of financial debt held by a prospect.
The Debt Amount field is able to handle leading dollar signs, commas used as thousands separators, and decimal points. That is, valid values can be formatted like: "5000", "5,000", "$5,000" or "$5,000.00". In addition to accepting single numbers, the Debt Amount field can also accept two numbers in the form of a range, such as: "$10,000 - $20,000". Valid range separators are nearly anything with spaces around them: dashes (" - "), colons (" : ") and more (e.g., " to ").
You may use the Debt Amount field to specify the range of debt values you will accept in your campaign. For example, you may specify that you only allow debt values between $5,000 and $15,000 and values outside of that range will be marked invalid.
You can set a minimum value (zero is used if you don't enter anything) and a maximum value. Leave the maximum blank to accept any value greater than the minimum (e.g., "$10,000 and up").
To determine whether an incoming range value is valid, LeadConduit Classic must treat it as a single value: the low, average or high value of the range. If, for example, a lead comes in with Debt Amount of "$10,000 - $20,000", the low value would be 10,000, the average value would be 15,000, and the high value would be 20,000. You specify how you want it to be interpreted. Range values will still be captured and stored as they are received in LeadConduit Classic.
The Email field type ensures that data is passed in a valid email format. Leads with incorrect address formats will be marked with "invalid emailAddress".
You may optionally select to only receive email addresses from valid U.S. domains (such as .com, .net, .org, .gov, .us, .edu etc.). We use a list of U.S. only domains for this validation. The list is subject to change as new domains are added. If a lead is submitted with an email addresses belonging to any other domain it will be marked invalid with lead status detail of "invalid preferredEmail".
You may also specify domains for exclusion (Example: xyz.com, spam.com). A lead with an email address belonging to an excluded domain will be marked invalid.
If you would like your field to accept email addresses but you do not want to validate the format of those addresses, you should use a Text data type.
The IP Address type ensures that a valid IP address is submitted. Leads with an invalid IP Address are marked with "invalid IP Address".
You may also choose to validate the IP Address against an accepted or excluded list of IP Addresses. Enter the IP addresses as comma separated values in the text box provided. Leads with IP addresses in (or not in) the list will be invalidated with "Not an accepted IP Address".
Both LeadConduit and LeadConduit Classic platforms properly validate IPv4 and IPv6 addresses.
First Name should be used when collecting a first name. There is no validation on this field type, but specifying the usage makes campaign integration easier.
"Last Name" should be used when collecting a last name. There is no validation on this field type, but specifying the usage makes campaign integration easier.
Use this field type to collect numerical data. Positive and negative whole numbers and decimals are accepted. You may restrict the accepted values by specifying a minimum and maximum.
The Phone Number field type is used to collect phone numbers. Phone Number requires that incoming values are in a known North American phone number format.
Phone Number also allows you to specify a format (dashes, no dashes, parenthesis, no parenthesis, etc). If you specify a format, leads with phone number that do not conform will be marked with "invalid Phone Number". The available formats, and those that are accepted when this is set to "any U.S. format", are:
512 555 1212
(512) 555 1212
1 512 555 1212
1 512 555-1212
1 (512) 555 1212
1 (512) 555-1212
Additional phone number validation is available. You may choose to validate that the area code is valid or that the exchange (the second three digits) is valid within the area code. If you use this phone validation, it's best to validate both the area code and exchange, as this gives you the more detail about invalid numbers. Note that this validation cannot be applied to toll-free phone numbers (those that start with 800, 866, 877, 888, 855, 844, 833 or 822).
Because any combination of digits is possible for the line number (the last four digits), LeadConduit cannot validate it. Our phone number validation recognizes all active North American phone numbers including the United States, Canada and most of the Caribbean.
You may also choose to validate the incoming phone number against an accepted/excluded list of area codes (Eg. 512) or area codes + exchanges (Eg. 512-275). Enter the codes as comma separated values in the text box provided. Lead are marked with "Not an accepted phone number" if their phone numbers do not pass these acceptance criteria.
You can pass a phone number extension space separated after any valid formatted phone number format, like: 512-555-1212 999
The State/Province field type is used to collect and validate U.S. states, territories, military bases, and Canadian provinces. You may also use this field to limit acceptable leads to certain states. Leads with an invalid State/Province are marked with as "invalid State/Province".
State fields can also be cross-validated with Zip Code fields in your campaign. When this is selected, state values that don't match the ZIP value (for example, a state of "NY" with a Texas ZIP code) will be invalidated.
Use this field type to collect street address information. There is no validation on this field type, but specifying the usage makes campaign integration easier.
Text is the default data type for new campaign fields. Text will accept all characters. If you do not know which data type to select, use this one.
By default, the text field type will accept any value. However, the text field type provides a great deal of flexibility for customization. If you are familiar with regular expressions, you may validate a text field using a custom pattern. Should you require field validation that is not handled by one of LeadConduit Classic's built in types (text-list, email, phone, etc.) then this feature provides the solution.
A Text - List will only accept values from a pre-defined list.
For example, imagine that you have a campaign field named "siteName" and you want to use this field to track which website generated the lead. You know you only accept leads from two affiliate sites, "lotsofleads.com" and "moreleadsplease.com". These are the only two authorized sites, and leads coming from sites other than these should be marked invalid.
Other applications for this data type:
- yes/no (or true/false) fields
- month names (January, February, March...)
- gender (male/female)
- any field that uses a drop down control in the web form
Text-list field types have an option for a Multi-value field. Multi-value fields are text-lists that allow more than one value to be submitted for a single field. For example, imagine a form that asks the respondent to select up to 3 hobbies, from a list of 20 possible choices. The field, "hobby", would be a multi-value field, with a maximum of 3 values. The "hobby" text-list field would accept any of 20 possible values up to a maximum of 3. Each value would be passed separately such as hobby=fishing&hobby=golf&hobby=hunting.
Use this type to collect timestamps in one of these formats:
|mm/dd/yyyy hh:mm:ss tz
mm-dd-yyyy hh:mm:ss tz
dd/mm/yyyy hh:mm:ss tz
dd-mm-yyyy hh:mm:ss tz
yyyy/mm/dd hh:mm:ss tz
yyyy-mm-dd hh:mm:ss tz
|yyyymmdd hh:mm:ss tz
mmddyyyy hh:mm:ss tz
mm/dd/yy hh:mm:ss tz
mm-dd-yy hh:mm:ss tz
dd/mm/yy hh:mm:ss tz
|dd-mm-yy hh:mm:ss tz
yy/mm/dd hh:mm:ss tz
yy-mm-dd hh:mm:ss tz
yymmdd hh:mm:ss tz
mmddyy hh:mm:ss tz
The "tz" on the end is for Timezone, and is optional. Allowed values are EST, EDT, MST, MDT, CST, CDT, PST, PDT and UTC+/- hours (such as "+0500"). Leads with an invalid timestamp will be marked with "invalid time_stamp".
Use this field type to collect ZIP code data. You may also validate the ZIP against a national database. Leads with an invalid Zip Code will be marked with "invalid Zip Code".
You can also specify that ZIP codes will only be accepted if they are within a certain distance of a single ZIP. For example, you could allow only ZIP codes that are within 50 miles of 78703. Note that this distance calculation is based on latitude and longitude coordinates that represent the "center" of a ZIP code area.
Lastly, you can validate the ZIP against a list of accepted (or excluded) list of zip codes. Enter the ZIP codes as comma separated values in the text box provided. The lead will be marked "Not an accepted zipcode" if the ZIP does not meet these criteria.
Supported zipcode formats: US, Canadian, UK
A number of the text fields ("City", "Email", "First Name", "Last Name", "Text" and "Street Address") can also have minimum and maximum lengths specified. The maximum length of any of these is 255 characters. If no maximum is entered, the maximum of 255 is used by default. Also, if no maximum is specified on one of these fields, leads will not be rejected if a value is longer than 255 characters. Rather, the lead will be processed with that value cut off to that length.