If leads are being submitted directly to LeadConduit Classic from consumers' browsers, then we suggest re-directing them to a "thank-you", or landing, page on your site (rather than displaying the XML that LeadConduit returns).
If you are not using a thank-you page (i.e., you are doing a server-to-server transfer) then you do not need to use these parameters at all.
Include the following parameters in your lead posts to use redirects:
|xxRedir||Causes the server to redirect the user to the given URL, rather than returning an xml response. Must be a valid URL, starting with http:// or https://. Must be url-encoded if you are submitting leads via HTTP GET. Cannot be longer than 255 characters.|
|xxRedirFailure||An alternate URL to redirect to when a lead post gets a failure response from LeadConduit. A failure response from LeadConduit could be the result of an invalid or rejected lead when synchronous delivery is enabled. Must be a valid URL, starting with http:// or https://. Must be url-encoded if you are submitting leads via HTTP GET. Cannot be longer than 255 characters.|
|xxRedirVerbose||Causes the server to append xxLeadId, and all campaign field values (listed in the Campaign Parameters section) to the URLs specified by xxRedir and xxRedirFailure. Set to either '1' or 'true' to cause a verbose redirection.|
For example, if you want to redirect successful submissions to
http://yoursite.com/thankyou.html and failed submissions to
http://yoursite.com/sorry.html, then you would pass the following:
Notice that the values of the redirection parameters are URL encoded — failure to encode the URL could lead to unexpected lead submission results.
Tracking pixels are often placed on thank you pages to track the number of leads submitted. However, advertisers only want to pay for good or accepted leads. A way to accomplish this is to place the tracking pixels on the thank you page used for successful submissions and don't place any tracking pixels on the page used for failed submissions.