System Fields

In addition to the campaign fields (defined in the Campaign Set-up section), we also provide a few System Fields that may be received.

The following System Fields are available:

• Lead ID
• Lead Status
• Lead Status Detail
• Lead Capture Date
• Lead Capture Date & Time
• Source Node ID
• Source Lead ID

System fields are automatically generated by LeadConduit. These fields are used for tracking within the application.

Field: Lead ID (leadId)

The lead identifier is a permanent identifier that uniquely identifies the lead. It is up to a 9 character hexadecimal (alpha numeric) string (i.e. “1a2b3c”).

It is important to capture the lead identifier when receiving data from LeadConduit. The lead identifier is used for updating the final disposition of the leads (See “Closing the Loop: Final Lead Dispositions” for more information about the final lead disposition.).

The lead identifier is available with all delivery mechanisms (manual, email, HTTP/HTTPS) as well as via a data export. The table below shows the name used for the lead identifier depending on the mechanism,

Field: Lead Status (leadStatus)

The lead status indicates the current state of the lead. The lead status is available via a data export. The lead status value is passed using “leadStatus”.

See Life Cycle of a Lead (Lead Status) for the list of possible Lead Status values and their meaning.

Field: Lead Status Detail (leadStatusDetail)

Contains further information describing the status of the lead. For example, if the lead is INVALID, the "leadStatusDetail" might contain the text "duplicate" indicating that a lead with the same primary key(s) has already been provided in the campaign.

Field: Lead Capture Date (leadCaptureDate)

The lead capture date indicates the date that the lead was submitted to LeadConduit. The capture date is available via a data export. The capture date is passed using “captureDate.”

Field: Lead Capture Date & Time (leadCaptureDateAndTime)

The lead capture date indicates the date and time that the lead was submitted to LeadConduit. The capture date and time is available via a data export. The capture date is passed using “captureDateAndTime.”

Field: Source Node ID (sourceNodeId)

The source node identifier is a permanent identifier that uniquely identifies the lead publisher within a particular campaign. It is up to a 9 character hexadecimal (alpha numeric) string (i.e. “1a2b3c”). Each lead is posted into LeadConduit with the xxNodeId parameter. Source Node ID contains the value provided as xxNodeId when the lead was submitted.

The source node identifier is unique per publisher (affiliate) and campaign. The same affiliate will have a different source node identifier in different campaigns.

The source node identifier is available with all delivery mechanisms (manual, email, HTTP/HTTPS) as well as via a data export. The table below shows the name used for the publisher identifier depending on the mechanism,

Field: Source Lead ID (sourceLeadId)

The source lead ID permanently and uniquely identifies another lead in LeadConduit. This field is automatically populated if you have been set up to route leads from a source campaign to a destination campaign. In this scenario, the source lead ID identifies the lead in the source campaign when you're looking at the lead in the destination campaign. This field can be used to manually reconcile the status of leads routed one campaign to the next. Leads posted to a campaign that is not a routing destination will not contain a value for source lead ID.