Lead Posting Responses
When posting leads into the boberdoo system using the standard GET/POST method, your system returns a response for every post attempt. Whether you have vendors posting leads into your system or are using internal landing pages, this immediate response gives you the details of each posting attempt.

Short vs. Full Responses
The standard responses boberdoo provides can be split into two categories: short responses and full responses.

Response Types
Short Responses
Most boberdoo clients utilize the standard short response. The default short response is returned in XML format and can include 3 possible values: status, lead_id and error. The status tells you whether the lead posted correctly and found a buyer. The lead_id returns the unique ID assigned to each successful lead. The error field specifies the issue upon a failed submission.
Success/Error Short Responses
In cases where clients don't want vendors to know whether a buyer was found, we can enable the success/error response which simply indicates whether the lead was posted correctly. This setting can be enabled at the source level by enabling Success/Error Response.
Short Response Use Case: Conditional Redirect
When a lead fails to match any buyer, you can dynamically adjust the confirmation page. Send matched leads to your standard thank you page, and unmatched leads to a page informing them that no partner was found. The unmatched page could include useful links or affiliate feeds to assist the lead.
Full Responses
The full response provides the same information as the short response plus a partners field with detailed information about the matching partner. You can also enable a lead_admin_link field that provides a link to the matching partner's boberdoo system login (open a support ticket to enable).
Full Response Use Case: Display Matching Partner
Because the full response includes matching partner information, you can display who the lead can expect to be contacted by on your confirmation page. Note: if you are purchasing and re-selling leads, avoid this option as it will reveal your buyer information to your vendor.
Full Response Use Case: Live Transfers with Data Matching
boberdoo's live transfer with data matching allows call center reps to ping or post lead information into the system to determine the best buyers for each live call. This method requires the full response to return information of one or more potential partners.
Configure Your Response Settings
Response settings are configured at the source level and can be edited on a source by source basis, giving you flexibility to make changes whenever needed.
Frequently Asked Questions
The default XML response that includes status, lead_id, and error fields. Most boberdoo clients use this format.
A response that includes all short response data plus detailed information about the matching partner. Used for displaying partner info or live transfers with data matching.
Response settings are configured at the source level and can be edited on a source by source basis.
Ready To Get Started?
Fill out the form below to schedule a demo with one of our lead distribution experts.