How do I return leads?


If you are a lead recipient, you should return bad leads to their respective sources. Your sources can use the return reasons you provide to optimize lead generation for your campaign. If you choose not to return leads then your lead sources may assume that you are happy with the leads they are providing, and consequently will not make adjustments which could lead to higher conversion rates for you.

A word about return reasons

You should carefully select the return reasons you use. It is important for the lead source to be able to see how many leads were returned for each reason you provide. If you provide three different variations of the same reason, then this sort of categorization will be more difficult. For example, for all leads that had a disconnected phone, always use the phrase "disconnected phone." Avoid submitting multiple reasons that have the same meaning which are phrased in different ways: "phone was disconnected," "disconnected phone," and "home phone number was disconnected" are all the same thing, and should all be returned with the same return reason phrase.

Leads are categorized by return reason in the Bad Lead Summary.

How does it work?

Returning leads is easy. There are three different methods you can use.

Return a single lead

Simply navigate to the lead in question by searching for the lead ID (leads > search), or by drilling into the statistics. On the lead details page, just click the "return lead" link in the yellow tool bar at the top of the page.

Provide the return reason, such as "disconnected phone" or "never signed up." The source that provided the lead will be able to see your return reason.

Return leads in bulk with a CSV file

Your file should be a CSV file with a header line and one lead per line. Each line should contain either the LeadConduit lead ID or the primary key value (usually email address or phone number), and should also contain the return reason.

Navigate to the leads > returns page.

Select your CSV file. Be sure to choose the appropriate selection based on whether your file contains lead IDs or primary keys. Your file will be verified prior to performing the returns. You may be asked to select the column which contains the return reason.

Once you begin your return, you may continue to use LeadConduit. You can cancel your return while it is still processing, but any returns that have already been performed will not be automatically rolled back.

Once every line in your file has been processed, you will see a summary of what happened. If there were some "failures", this indicates that some of the leads could not be returned. This happens when the leads were already marked bad prior to your return, or possibly that the leads in question were deleted.

If you see some "errors," then this indicates that some returns could not be processed. If all lines resulted in error, then there is probably something wrong with your file. Make sure you have the lead ID or primary key and the return reason, and that the file you are using is a valid CSV file. If some of your leads were successful and some were errors, you can try processing your file again. This should not be necessary under normal operating conditions.

Return a lead via the API

If you want to integrate lead returns into your CRM solution, you should use the LeadConduit API. This can be accomplished by making a simple HTTP call to the LeadConduit API.

PUT{lead_id}/return or


Lead returns are protected by Basic Authentication. For more information about authentication, and the API in general visit the API Overview.

Use an HTTP PUT or POST to the above URL to return a lead to the lead source that provided it. Use the reason parameter to specify why the lead is being returned. The reason parameter has a 75 character maximum length and will be truncated if it exceeds that length. If the lead is successfully returned, the API returns HTTP 200. Any other code indicates that the lead was not returned. Only the final recipient or owner of the lead’s campaign may return the lead and calls to this resource by someone else will generate an HTTP 401 Unauthorized. Your lead sources, when logged into their LeadConduit accounts, will be able to see a summary of how many leads were returned by reason.

This information is also available in the associated API documentation.

What happens if I make a mistake?

Don't beat yourself up over your mistake. You can easily undo a bulk return using the same process. But this time, just select the "undo" checkbox when you upload your file. You can also perform this operation from the lead detail screen and via the API.

Instead of rejecting your leads, LeadConduit will "rollback" the rejection for each lead. If you attempt to rollback the rejection for a lead that isn't rejected, then nothing will happen to that lead. Leads that are rejected, however, will be returned to whatever state they were in prior to the rejection. If they were awaiting delivery, for example, they will be placed back into the delivery queue. If they were already delivered and marked as accepted, then they will be marked as accepted again.

If you wish to rollback returns through the API, use one of the two the following calls:

PUT{lead_id}/rollback_return or


If you attempt to rollback the return for a lead that was not returned, the API will return a HTTP 409 Conflict with "lead has not yet been returned" in the response body.

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request


You must be logged in to comment.