Using Field.aspx

TSL Ping Tree > Page Usage

Using Field.aspx

A Field is an internal variable for holding visitor lead data that originates from a visible or hidden input on a web form or a parameter posted directly from you or one of your affiliates.

The web does not really support the concept of a data type - every input value is a character string - but our system does.  We support Checkbox, DateTime, Decimal, Integer, IP Address, String, and String Enumeration (all of which are defined below).  We recommend that you use the best internal data type for your fields such that filtering values and mapping to many differing interfaces and lead buyers is easiest.

For example, many online lead generation web forms ask "How Long" type questions such as "How Long Have You Been Living at This Address?"  Most implementations are drop down lists with values such as "0 - 6 months", "6 - 12 months", "12 - 24 months" etc.  There are several problems with this approach especially when you are selling leads to multiple lead buyers or when you attempt to use or sell leads that do not sell in real-time at some time in the future.  How do you map to a lead buyer who wants to break things down as "0 - 18 months" and "18+ months" when your visitor answered "12 - 24 months"?  If you sell unsold leads in a bargain bin or list management type of arrangement then how long has this lead lived at his current address after two more months have passed?  A much better way to implement a question like this is to either ask "Approximately when did you start living at this address?" and have the answer be a Date, or provide smaller time intervals such as months in a drop down list, e.g. "1 month", "2 months",... "1 year", "1 year 1 month"..., or ask "How many months..." and before posting the value to our Submit service converting those answers to a Date.  A Date will be useful for all kinds of filters and mapping needs now and at any time in the future.

There are many other examples where using a data type other than String for a Field can make things better.  However, if you wish it is perfectly valid to use nothing but String and String Enumeration types for a particular Form.

Configuration Item Description
Name A unique field name up to 255 characters, e.g. "First Name".
Default HTTP Parameter Name A form or posting specification input name, e.g. "firstname".
Data Type

CheckBox - Use this for HTML checkboxes or Boolean (True/False) parameters.

DateTime - This can be a date and/or a time.  String inputs are converted into dates according to the rules of the Culture specified for the Form where this Field is used.

Decimal - Use this for money amounts, e.g., even if you plan to round off fractional amounts.

Integer - Use this for counts where fractional amounts make no sense such as "Number of Bedrooms".

IP Address (v4) - An IP Address such as (Google's main public DNS server).

String - A character based value that is not limited to a finite set of valid values.

String Enumeration - A character based value that is limited to a finite set of valid values.

Modifier Modifiers are used to modify the as-submitted string value for a Field before casting it into its specified data type and before any Field Validations or Filters occur.  For example using "DigitsOnly" on a phone number string would change input value "(678) 325-1582" into "6783251582".  The main use of Modifiers for a Field is to run modifiers like "DigitsOnly" and "NumericOnly" but any modifiers can be used provided that after running them it will be possible to cast the modified value into the specified data type.
Hidden You can't delete a Field once you create it but you can change its definition and you can also hide it so that it does not appear in drop down lists, e.g.

A Field may have one or more Field Validations attached to it (except for String Enumeration type Fields which only have a list of valid Value/Description pairs of characters strings up to 255 characters each).

There are several built in Field Validations to choose from depending on the data type of the Field.  You may also define your own Field Validations.