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 to post leads in, this immediate response gives you the details of the posting attempt and allows you or vendor to know whether each lead made it successfully into your boberdoo system.

Short vs. Full Responses

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

Short Responses

Most boberdoo clients utilize the standard short response. The default short response is returned in an XML format and can include 3 possible values: status, lead_id and error.

short response

The response’s status field tells you whether the lead posted into the system correctly and whether it was able to find a buyer. The lead_id field returns the unique Lead ID that is assigned to each lead upon a successful post into the system. Finally, the error field specifies the issue with the posting upon a failed submission. This field will not display if the lead successfully posts into the system.

short response

Success/Error Short Responses

In certain cases, such as when our clients don’t want their vendors to know whether a buyer was found, we can enable the success/error response which simply tells you whether or not the lead was posted into the system correctly. This setting can be enabled at the source level by enabling Success/Error Response.

Short Response Use Cases

Although the short response returns the most basic information upon a lead submission, there are still a few interesting ways to use this information.

Conditional Redirect Upon Unmatched Response

In the event that one of your leads fails to match to any of your lead buyers, you can dynamically adjust the confirmation page that the lead is redirected to. In this scenario, you can continue sending all matched leads to your standard thank you page, but send all unmatched leads to a page that informs the lead that you found no matching partners. Alternatively, your unmatched confirmation page could even include useful links or affiliate feeds to try to assist the lead even though you were unable to find a matching partner.

Full Responses

While most of our clients utilize the short response, there are certain scenarios where a full response needs to be used. The full response provides the same information as the short response along with a partners field, which returns the detailed information of partner that the lead matched to.

full response

Note: You will also see a lead_admin_link field option in the full response example. This provides a link to the matching partner’s boberdoo system login. To utilize this option, please open a support ticket.

Full Response Use Cases

If you are purchasing and re-selling leads, you would not want to use this option because this will reveal your buyer information to your vendor. However, there are a few unique opportunities that the full response provides that you can easily take advantage of.

Display The Matching Partner To The Lead

Because the full response includes the matching partner information, you can use this information to display the information of the matching partner (or partners) on your confirmation page. This will inform the lead exactly who they can expect to be contacted by.

Live Transfers With Data Matching

boberdoo’s live transfer with data matching options allows call center reps to ping or post lead information into the system in order to determine the best possible buyers to transfer each live call to. When using this live transfer method, you must utilize the full response in order to return the information of one or more potential partners for each lead.

Configure Your Response Settings

Response settings are configured at the source level and can be edited on a source by source basis, giving you the flexibility to make changes whenever needed.