If you submit a lead into LeadConduit via HTTP you will receive an XML response from our server. This document describes that response and how to interpret it.
Response Versions
LeadConduit provides two different response versions. The first response version (v1) is being phased out as we transition to the second response version (v2). The posting documents, available for each campaign by logging in to LeadConduit, reflect the v2 response format as of 4:00pm CST 7/13/2007. Campaigns setup before this time will continue to get the v1 response, until they start using the latest posting URL.
The server sends a different response version depending on the posting URL used. Because the v1 and v2 responses are available at different posting URLs, you may continue to use the v1 response even after the transition to v2 is complete.
| Version | URL |
| 1 | http://production.leadconduit.com/ap/PostLeadAction |
| 1 | http://production.leadconduit.com/ap/v1/PostLeadAction |
| 2 | http://production.leadconduit.com/ap/v2/PostLeadAction |
This document is a reference for the v2 response only. More information about our v1 response is available upon request.
What can you infer from our server response?
The response indicates all of the possible outcomes of submitting a lead into LeadConduit. A response does NOT indiciate the final disposition of the posted lead (whether or not you will be paid). That is determined by the final recipient of the lead.
What information is available in our server response?
There are several parts to our server response: the result, reason, leadId, and url. The result will be included in every response, while all other parts may be omitted from the response as appropriate. For a technical description of our response format, please refer to the Document Type Definition (DTD) included in the DOCTYPE declaration of the response (http://production.leadconduit.com/ap/dtd/response-v2-basic.dtd).
The result tag
A result is shown with every server response. The code word shown inside the result tag indicates the outcome of your lead post:
| result | meaning | how to interpret |
| success | lead was submitted successfully | We received the lead. Do not resubmit. |
| queued | lead was submitted successfully, but no further processing occurred | We received the lead. Do not resubmit. |
| failure | lead was invalid | There is a problem with the lead. Do not resubmit without first correcting the problem(s) described in the reason tag(s). Some issues, like a duplicate lead, cannot be corrected. |
| error | the request was malformed (i.e. missing a parameter) | There is a problem with your HTTP request. Do not resubmit the same request again without first correcting the problem(s) described in the reason tag(s). |
The reason tag(s)
One or more reason tags may be returned in each server response. If there are a several problems with the lead you've posted, each problem will be shown inside its own reason tag. Reason tags are only provided in the event that some problem has occurred (on failure and error responses). Generally speaking, if you submit the same lead again without first correcting these problems, you will receive the same response from our server. For this reason, we require that you do not repost the same lead that generates a failure or error response without first correcting the problems shown in the reason tags.
The leadId tag
The leadId tag contains our record identifier for the lead you have submitted into LeadConduit. All leads that are posted to our system, regardless of whether the post generates a success or failure response, get a leadId. Generally speaking, if you have a question about a lead you will need to refer to it using the value contained in the leadId tag.
If no leadId tag is provided in the response, you must assume that the lead could not be created in our system. Sometimes this happens because an error occurs on our end or because the lead-handling component of our system was offline for maintenance. When this happens, you will receive a queued response and no further action is necessary on your part. When our system comes back online, your post will be automatically handled and a new lead will be created in our system. Other times, the problem may be related to the way you posted the lead. You can recognize that this has occurred because an error response is given. Take a look at the specified reason tags to figure out why the lead could not be created in our system.
The url tag
The url tag contains a hyperlink to the lead submitted into LeadConduit. You can copy and paste this link into your web browser in order to view the details of the lead (you will be required to log into LeadConduit first). The "<![CDATA[...]]>" information that wraps the hyperlink is included in the url tag for the benefit of software that parses the XML in our response. This is not part of the hyperlink itself.
Some real world examples
A good lead is posted.
<?xml version="1.0"?>
<!DOCTYPE response SYSTEM "http://production.leadconduit.com/ap/dtd/response-v2-basic.dtd">
<response>
<result>success</result>
<leadId>000drxhsn</leadId>
<url><![CDATA[https://production.leadconduit.com/ap/lead?id=000drxhsn]]></url>
</response>
A lead is posted, but is invalid because it doesn't meet the requirements, as explained in the posting documents, of this campaign. The reason tags show why the lead post was a failure: the email is invalid and the required phone field is missing. Do not resubmit this lead without first correcting the email address and providing the lead's phone number.
<?xml version="1.0"?>
<!DOCTYPE response SYSTEM "http://production.leadconduit.com/ap/dtd/response-v2-basic.dtd">
<response>
<result>failure</result>
<reason>invalid email</reason>
<reason>missing phone</reason>
<leadId>000drxhsn</leadId>
<url><![CDATA[https://production.leadconduit.com/ap/lead?id=000drxhsn]]></url>
</response>
A lead is posted but the lead cannot be processed at the current time because the system is offline. Notice that there is no leadId contained in the response. The reason tag shows why the lead was queued. The lead will be processed when the system is back online.
<?xml version="1.0"?>
<!DOCTYPE response SYSTEM "http://production.leadconduit.com/ap/dtd/response-v2-basic.dtd">
<response>
<result>queued</result>
<reason>system is offline</reason>
</response>
A lead is posted but the lead cannot be processed at the current time because an internal server error occurred. Notice that there is no leadId contained in the response. The reason tag shows why the lead was queued. The lead will be processed once the internal server error is corrected.
<?xml version="1.0"?>
<!DOCTYPE response SYSTEM "http://production.leadconduit.com/ap/dtd/response-v2-basic.dtd">
<response>
<result>queued</result>
<reason>internal server error</reason>
</response>
The request is missing the required xxNodeId parameter. The lead cannot be handled without this parameter, so no leadId is contained in the response.
<?xml version="1.0"?>
<!DOCTYPE response SYSTEM "http://production.leadconduit.com/ap/dtd/response-v2-basic.dtd">
<response>
<result>error</result>
<reason>missing parameter xxNodeId</reason>
</response>