PING / POST delivery allows you to send a smaller request to a client's system and receive a response about whether they will accept that record before you submit the full lead or not.
To setup the PING / POST first select Clients from the top menu:
From there, select the client you wish to update, or create a new client.
Once you are in the client settings, select Delivery Method from the left navigation
You will either be prompted to create a new delivery method, or you can select Create from the toolbar.
You will create two delivery methods. One for the PING and one for the POST (you will need documentation from your client on what to send for each, also if you need to capture any reference codes from the PING to forward in the POST).
First we will create the PING delivery. For this example the following expected response will be received:
Using that response example above (this will change per client, on what they will respond with). We can tell that we need to check the WillAccept and grab the Reference item so we can forward that value in the POST with the lead.
First thing is to create the PING delivery method.
On the General Settings you will select the type of delivery for the PING, this is usually HTTP POST or HTTP GET.
On the Delivery URL tab will include the delivery address and any custom headers.
Next on the Field Mappings tab you will want to map out the values located in the post docs. For the PING delivery, there is usually very few fields to be sent.
Now click on the Response Settings tab, this will be where you specify what to look for in the response as well as the reference number.
From the example above, you can see that in the Response Information, we are looking for true in the
<WillAccept> node. Also we have the Use Regular Expressions checked.
Also, in the PING Reference Search, we are searching the <Reference> node and capturing any value located in that node.
At this point, the PING delivery method is complete, we can move on to the POST delivery.
When creating the POST delivery, you want to select the PING/POST delivery method instead of HTTP POST. This will tell LeadExec that you will want to use another delivery method for the PING.
From there, you would fill in the Delivery URL tab just like you did on the PING delivery using the POST delivery address located in your client's documentation.
Next you will want to build out your field mappings for the POST. This should include all fields and not just the fields you sent in the PING.
You will want to add the PING reference that you captured from the PING delivery method. (this may not always be required, please refer to the client's documentation).
To return the PING reference, you can use the
[ping reference] placeholder, this will grab that value from the PING response. In the example below, we are sending the PING reference value to the client under the field PINGReference.
Once that is complete, you need to fill in your response settings with the expected response you will get from the POST.
You have setup both the PING and POST delivery. Now you will want to setup a delivery account that will reference these methods.
Go to Delivery Accounts located on the left hand side of the screen.
You will be prompted to create a delivery account, or you can click Create from the toolbar.
From there, you will want to go through the steps required to setup the delivery account (1 through 4).
On step 3, you will want to select the POST delivery you setup from the delivery method drop down. Once you do that, the PING Delivery drop down will provide a list of delivery methods, you will want to select the PING delivery you setup earlier.
Once you have completed all 4 steps, press Save at the bottom.
This PING / POST delivery is now complete