Typically, after a prospect submits their information (lead) on a website, they expect to see a thank you page. We provide mechanisms that allow lead sources to redirect the prospect to the page of their choice using various field parameters.
If leads are being submitted directly to LeadConduit from consumers' browsers, then we suggest re-directing them to a "thank-you", or landing, page on your site (rather then 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:
| Parameter | Description | Restrictions |
|---|---|---|
| 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 in case a lead post gets a failure 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. |
| xxRedirVerbose | Causes the server to append xxLeadId, and all campaign field values to the URLs specified by "xxRedir" and "xxRedirFailure". | Set to either '1' or 'true' to cause a verbose redirection. |
If you want a simple redirect to a thank-you page (or some other page) on your site, then use the 'xxRedir' or 'xxRedirFailure' parameters.
Use 'xxRedirVerbose' for a verbose redirect, which adds the LeadConduit leadId and all the lead's data, in the redirect.
More information about these parameter are included in the posting info for your campaign. For information about how to submit leads into LeadConduit, go to Inbound Delivery Mechanisms