Follow

Lead Delivery Overview

What is it?

LeadConduit Classic provides a variety of methods to deliver leads from LeadConduit to an external system. You must have a paid LeadConduit Classic account and be the owner of a campaign in order to configure the delivery for that campaign. Lead Delivery is designed to work in real-time (one-by-one as leads arrive) but other scenarios can be configured. Lead delivery is configured by adding delivery destinations in the "Outbound Lead Delivery" section of the "Campaign" screen.

 

Manual Delivery

By default, if no delivery destinations are set up for a campaign, leads must be delivered using manual lead delivery. Manual Lead Delivery is essentially a batch export process that only exports leads that are currently in a Pending status. Once the leads have been downloaded, their status is updated from "Pending" to "Delivered". You can access the Manual Lead Delivery screen under the Delivery tab in LeadConduit

 

Pending Leads

A lead that is in a Pending status is a lead that has not yet been delivered. A lead can be in a Pending status for a variety of reasons. Examples include: No delivery destinations have been added to the campaign, the delivery destinations have been disabled for the campaign, the lead is receiving an error response from one of the destinations, the lead has not yet finished going through all of its delivery destinations, etc.

 

Delivery Destinations

Each campaign can be configured with zero or more delivery destinations. To automatically deliver a lead when it arrives in LeadConduit Classic you must add at least one delivery destination.

When a lead is delivered to a destination, there are three possible outcomes: success, failure, or error. A lead is considered delivered if it reaches a configurable number successful destinations.

Delivery Destination Types

  • HTTP — This is used for the majority of lead deliveries. It is a form post using HTTP POST or GET to send leads to another server in real-time.
  • Custom HTTP Post — This is used for SOAP or XML formatted deliveries.
  • Email — This is for delivering leads in real-time via email where there is one lead delivered per email. Learn more.
  • QuickBaseQuickBase is a web-based application provided by Intuit. This type of delivery destination allows you to map campaign fields, certain system fields, and hard-coded values into a specified QuickBase table.
  • Campaign — This option is for delivering leads to another LeadConduit Classic campaign. Learn more.
  • TrustedForm — This option is for claiming a TrustedForm certificate. Learn more.
  • BatchRobot — This option is deprecated.

Trouble Monitoring

In the global delivery settings you have the option to configure email notifications about your campaign delivery for:

  • Error Alerts — An error is when delivery must be retried for any destination (for example, if a recipient server is temporarily offline). You can specify the number of errors before receiving an email.
  • Reject Alerts — A reject is when the minimum number of successful deliveries cannot be made (for example, if a lead is a duplicate in the system being delivered to). You can specify the number of rejects before receiving an email.

Setting up these notifications is an important step in ensuring that your campaigns are running smoothly. If this isn't set up to at least notify someone when excessive numbers of errors or rejects occur, then your campaign may run for days or weeks before someone discovers a problem.

The "Delivery" tab in LeadConduit Classic provides a real-time view of the status of your campaigns' lead delivery from LeadConduit to third-party systems. Clicking on the tab will take you to the "Lead Delivery Status" page. This page lists the campaigns with leads awaiting delivery, along with information to help determine the problem, if any. Depending on their configuration, a campaign being listed here may or may not indicate a problem. Campaigns with no pending leads are not shown.

 

Lead Distribution

This is only applicable if you have multiple delivery destinations. In the Global Delivery Settings section you can select from 2 types of lead distribution:

  • Standard — Always start at top of the list with the first destination and work through the destinations in the priority listed.
  • Round Robin — Rotate the starting destination for more even lead distribution across all destinations. Note that this rotation is based on random selection of which destination to use first, and may result in the uneven distribution, especially for small numbers of leads. Round robin does not attempt to even out the actual delivery of leads, it merely changes who gets the first shot at attempting a delivery. So if you get the first shot at a lead which is not accepted by your campaign (for whatever reason) that still counts as an "at-bat" for you.

In this section you can specify the maximum times a lead should be delivered. This is useful if you are selling leads to multiple buyers and need to specify the maximum number of times a lead should be sold.

While entering a number greater than the total number of deliveries is moot, it guarantees that the lead will attempt delivery at each location. It also adds additional flexibility should you add more destinations in the future and forget to increase the total. For example, you may have 3 delivery destinations, but indicate that each lead should be delivered a maximum of 10 times. That way, you could still add an additional 7 destinations and the lead will get delivered to each. 

Make sure to keep in mind that a lead can only be delivered once per destination.   

 

Lead Status Determination

When you are sending a lead to multiple destinations, you must define what is considered a good lead based on the outcome of all of those destinations. On the Global Delivery Settings page, you specify which of the destinations must successfully receive leads for them to be marked as 'good'.

For example, assume you have a campaign that sells exclusive leads to one of 4 buyers. The campaign would have 4 delivery destinations (one for each buyer). In the Global Delivery Settings, you would indicate "Mark leads accepted when delivery to at least 1 of the following selected destinations succeeds". A lead to this campaign would only be considered good if one of the buyers accepted it.

If a lead is not accepted by the required number of destinations as defined in this section, it will have a reject reason of "accepted by too few delivery destinations". In the example above, if none of the buyers accepted the lead it would have this reject reason.

If the lead was marked bad because it only failed one of the delivery destinations, LeadConduit Classic will use the reject reason from that destination. For example, assume you have a campaign that is using a 3rd party lead verification service. The campaign uses two delivery destinations - one for verification and one to deliver to your CRM. The verification destination would be configured to stop on failure. In this case, the reject reason would be captured from this destination since that is the only destination that failed.

 

Synchronous Lead Posting

This is configured on the Global Delivery Settings page. Learn more.

 

Filtering

You can filter out leads that you do not want to deliver to a particular destination, using the feature described in the lead filtering article

 

Delivery Summary

After a lead is delivered, you may want to check to see the details of that delivery. This can be done be looking at the Delivery Summary of an individual lead. You can get to an individual lead via the Leads tab or by drilling into the numbers on the Statistics screen.

Within 100 days of delivery, the Delivery Summary will provide the outcome of each delivery destination along with the request and response body, and the time the lead was delivered. After 100 days, the request and response bodies are removed from the system, but the lead status and delivery time for the lead will remain. You will still have access to the lead data via the system fields and campaign fields, which remain available.

//--//

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

Comments

You must be logged in to comment.