Testing Lead Submissions
Are you looking to test leads being posted from one of your vendors or a custom form into your boberdoo system? If so, you’ve come to the right place. The following outline will help you test all of your inbound leads to make sure everything is set up properly.
What’s Required For the Post
Before you or your vendor start sending test leads through the system, let’s make sure we have everything you need to build the integration.
Regular Lead Type
- Lead type posting specifications
- Source (SRC) value
Ping Post Lead Type
- pingPostLead API specifications
- Source (SRC) value
- Vendor API key
Getting Leads Into The System
Once you have collected the appropriate information above, you or your vendor can build a post into the system. When a lead is correctly sent into your system via your posting specs and there are no errors in the setup, the lead is inserted into your Leads page and the system returns back an XML response to let you or your vendor know what happened with the lead. A successful response will either be Matched (lead entered the system and sold to a buyer) or Unmatched (lead entered the system but did not sell to a buyer). However, if the response returns an error, that means the lead was not inserted into your leads page due to an issue with the posting setup.
Adding a Test Buyer
When you or a vendor are sending through test leads, you will most likely want to get back a valid and successful response. Especially with any ping/post vertical, a “Matched” response is required to get back on the ping, so that a post can even be attempted. When using the Test_Lead=1 parameter mentioned above, even though the lead is not submitted and stored into the system, the Lead Filter Sets for all your buyers are still being checked to consider whether the response should be Matched, or Unmatched.
So, in order to receive a successful “Matched” response, you will want to create a test buyer account in your system. This test account will act like any other partner account, so be sure to follow these instructions to prevent your test account from purchasing any real leads. First, create your test partner account. Feel free to fill in false information and be sure to label the Company Name as “Test” so it can be easily identified.
Next, go to your test partner’s Invoicing/Billing subtab and give the account some funds so it will be eligible to “Match” with the test leads. We would recommend setting their credit limit to something small such as $50. As long as you are testing with Test_Lead=1, the money is not actually deducted from their account (since the leads are not actually being stored in the system). However, this is a good safeguard in case you forget to remove or accidentally activate this account and it attempts to purchase real leads.
Lastly, create a Lead Filter Set for this account. If your system has multiple lead types, you will need to create a new filter for each lead type. In this lead filter set, set the lead price to something modest such as $10. For the Accepted Lead Sources section, make sure you check whichever source you are using to test. Finally, at the bottom of your filter set, specify exactly what you want your vendor to submit with their test lead in order to force a match with this filter set. We recommend setting up your test filter to ONLY accept:
This way, you can tell any vendors who are testing to submit the test with State=AK and Zip=99999 in order to force a match. The idea is that a real lead would never have this information, so no real-time leads would ever be eligible to match to this test Filter Set. Finally, activate your filter set and you are all set to test. Once you have finished testing, be sure to either Deactivate your test partner account, or delete it altogether.
If you have any additional questions about testing, please open a support ticket and we would be happy to respond as soon as we can.