A variable is a key/value pair that is available to filters, rule sets and mappings and in templates at run time while processing a lead.

Every lead is born with a standard set of variables, and additional variables are added at run-time as leads are processed by each step in the flow. The full set of variables are stored on every event (in the vars property) generated during lead processing.

Variables are stored on events as nested objects and are referenced at runtime using dot-notation. There are several top-level variable prefixes that logically group variables.


Any of:

Variables prefixed with lead. are lead variables. Lead variables are created when a lead is submitted by a source to a flow. These variables typically contain data that was collected from the consumer on a web form.

Each variable name corresponds to a field ID. If the source submits a piece of data and the matching field ID has not been added to the flow, then a variable with that data will not be created. If the source needs to submit data using a parameter that does not have a matching field name, then a mapping must be added to map the source's parameter to the field name. For example, if a source submits fname=Joe then a mapping must be added in order to create the lead.first_name variable with the value "Joe".

For a list of all possible lead variables that are available "out of the box" in LeadConduit, simply prepend lead. to any of the standard field IDs.

property name*
additional property
{ }