For each campaign there is an option to use either Synchronous or Asynchronous Lead Delivery. This is only applicable to leads that are being delivered (both inbound and outbound) via HTTP POST/GET.
How does synchronous delivery work?
For synchronous delivery LeadConduit Classic holds the connection open with the lead source while we deliver the lead to the recipient(s). We wait to get a response from the recipient(s) before we give a response back to the source. The response given to a lead posted into that campaign will reflect the result of the delivery of that lead. If the lead is rejected at delivery, the lead post will return a failure response.
What if I am sending leads to multiple delivery destinations and synchronous delivery is enabled?
LeadConduit Classic will keep the connection with the lead source open while we deliver the lead to all of the delivery destinations for that campaign. We will then return the result of the deliveries to the lead source.
How does asynchronous delivery work?
For asynchronous delivery, LeadConduit Classic treats the inbound delivery separately from the outbound delivery. They are 2 separate transactions.
Inbound (how LeadConduit Classic responds to the data posted to it)
For the inbound post, LeadConduit Classic will provide a success response as long as the lead meets all of the acceptance criteria for that particular campaign. Once accepted, LeadConduit Classic will deliver the lead to the recipient(s). If the lead is rejected during that delivery, the originating source will not receive a reject response, since they have already received an accept response, and there is no longer a connection to the source.
Outbound (how LeadConduit Classic handles delivery to other systems)
Leads sent asynchronously are put into a delivery queue and processed in the order they're received. There is a separate delivery process (or "thread") for each campaign. That process delivers its campaign's queued leads sequentially, one after another, as quickly as possible. Asynchronous deliveries are usually processed within a few minutes of being queued, unless the campaign's queue is very full.
Aside from a small amount of overhead for LeadConduit Classic own processing, the main factor affecting delivery speed is how quickly the receiving server(s) handle each request. For example, if it takes the recipient server 3 seconds to respond to each lead post, then LeadConduit Classic will be able to deliver about 20 leads per minute.
Is there a disadvantage to using synchronous delivery?
Yes. If the recipient's server is slow, LeadConduit Classic will provide a slow response to your lead sources. Synchronous delivery can also overwhelm a less capable receiving server because leads will be posted just as fast as they come in. Asynchronous delivery only sends one lead at a time.
** Please note: ** in some cases, if lead volume is high and a recipient server is too slow (especially when LeadConduit times out waiting for a recipient server), the capacity of LeadConduit is threatened. In such a case, ActiveProspect may have to temporarily switch synchronous deliveries to asynchronous in order to relieve pressure on the system.