The Client Delivery Method is one of the most important screens in LeadExec. From this part of the system, you have complete control over the technical way your leads are delivered to your buyers.

On this screen, you will give a description of the Delivery Method. Select your lead type as well.

Select the type of delivery method you want to use. Some we offer include:

  • HTTP Post - Delivers to Another Software solution

  • XML / JSON - Delivers to Another Software solution

  • SOAP POST - Delivers to Another Software solution

  • SMS Text Messaging

  • Email - Email Batch, Email with a Link to Client Portal, or Email with the lead details in the body of the email.

Once you select Create Delivery Method you will get a modal for entering the basic information about this Delivery.

Once you have entered the basic information, you will then get the Delivery Method Details with several options for your Lead Delivery Method.

From the General Tab, you can provide a name for this Delivery Method, the Lead Type, and if you want to run in a live Production Environment or Test Environment.

Next, you will want to select the URL Endpoint from the Details screen.

From this selection, you can pick the Method, which includes

Post, Get, Patch,

Delivery Day Schedule – Use this feature to set a schedule for your clients. For example, they only accept leads Monday through Friday.

Moving forward with our methods, we must now input our delivery URL settings.

In order for a POST or any lead to deliver out to a system, a delivery URL is required.

Note: Only use the test URL if you are given a staging environment. If the In Testing option is checked, our system will use the test URL provided to deliver leads.


  • Content Type – Set the content type of your delivery. By default most HTTP POSTs can use the default option shown. In case you need to change the type to XML/Text content, click the dropdown to change.

  • Timeout – You can set a timeout on your clients so you can ensure that if a client takes more than X seconds to respond the delivery will fail and move onto your next client.

  • Authentication Types – Basic, Digest, Bearer Token, and OAuth 2.0

  • Basic – Allows you to specify username and password for basic authentication types.

  • Digest – Allows you to specify username and password for digest authentication types.

  • Bearer Token – Allows you to specify a token as well as the authentication prefix.

  • OAuth 2 – Provides the ability to authenticate with an OAuth server using one of the following grant types: Client Credentials, Password Authorization, Code. Note: If the authorization server returns an instance_url property. Use [instance_url] placeholder in the delivery address. This will instruct LeadExec to parse and retrieve the instance_url property and inject it into the delivery address when sending the request. This placeholder should come before the rest of the URL. For example, If the authorization server returned “instance_url: ‘’” if you were to specify “[instance_url]/processor/insert/general” it would translate to “”.

  • Custom Header Attributes – These attributes are used to define custom fields. More often than not they are used for SOAP Actions.

Field Mappings

Field mappings tab.

Field mappings are where you begin assigning your lead values, to the values of your CRM provider. For example:

This is the LeadField as it applies to YOUR system

  • Field Name – Is how LeadExec will pass it into your CRM provider.

  • Mapped Values – These are fields. They are most commonly dropdown fields in your system that can be “mapped”, or have their value changed from what you contain to another, in order to pass the correct data.

  • Value – This Will show you any static value that is placed for a particular Field.

Field Map

Field mapping table.
  • Field Name – This will be the value passed into your client CRM.

  • Field Type – Selects the type of field your system will be referencing for the field name.

  • Static Value – Assigns a static value to the system to be passed every time.
    Note: requires the field type to be set to static field.

  • Lead Field – Assigns the field name the lead field it will be referencing when passing data. IE: first_Name (Field Name) = FirstName (Lead Field)
    Note: requires the field type to be set to lead field.

  • Special Field Properties – These values allow you to add special system fields, custom expressions, client fields and lead source fields. To assist in setting these up please contact your ClickPoint Software Account Manager.

  • Default Value – This will pass a default value if not data is found for this field mapping

  • Format – Allows you to format the field so that you can manipulate data. For example: (yyyy/MM/DD) (DD/MM/yyyy) (MM/DD/yyyy)

  • Test Value – This will be the value passed when the delivery method is designated as in testing.

  • Value Mappings – This is where you can take values from within a dropdown and match them to another value. For example:

Value mappings chart.

XML Schema

XML schema tab.

After field mappings, if you are doing an XML POST you will have to input your schema into the following XML Schema tab. Simply copy and paste the schema into this.

To connect data, select your field mapping, and place the field in between the nodes. For example, the first name field mapping will be placed in between the first name XML node.

Response Settings

Response settings tab.

Response settings tell LeadExec what to look for when searching the clients response on an accepted lead.

  • Revenue Search – This will be used to search for any prices returned in the client response.

  • Ping Reference – This will capture ping token when a Ping/Post method is enabled.

  • Will get a redirect URL from your clients response to send back to your form to process a redirect.

Delivery Settings

Delivery settings tab.

The Delivery Settings option portion of your delivery method allows you to send a notification email to your client that they have a lead. To set this up do the following:

  • Include a from address. This will be the address your client sees in their email when a lead is viewed.

  • Destination – This will pull from the email placed on the contact information OR you can put your own destination email to add multiple emails use the, to separate. (,

  • Destination copy and blind copy are used to set up CC and BCC options for delivery.

  • Sent Notification Email. This will send a notification email to the client who receives the lead. You do have the ability to edit this email via an HTML Editor.

  • Email Response To Lead. This customizes your Response to your lead via an HTML editor.

  • SMTP Server – This can be used if you want to use your own SMTP server for email delivery. It will require the SMTP server address.

  • If you require a username and password, you may enter them as well.

Portal Settings

Portal settings tab.

This contains portal settings you can allow the client portal to show.

  • IVR Call Information – Only works if sending IVR leads.

  • Show File Attachments – Allows users to attach files in the client portal.

  • Show Analytic Data – If using the analytics system you can display the referrer and search term.


Notifications tab.

On this page you have the ability to send specific users notifications when a delivery fails. By checking the Send Notification Failure box, you can select specific users in the system to receive either an

  • Email

  • SMS Notification

Note: SMS charges do apply

Delivery Accounts

Delivery accounts screen.

The last step when creating a client is to set up their delivery accounts. With delivery accounts you can:

  • Dictate Price

  • Set Criteria

  • Set cap limits

  • Set exclusivity

  • Set Automated Delivery

Click on the Create button to begin delivery account setup

General Information

Delivery account general information screen.

General Information is where you will supply the following information:

Name – Provides a name for this particular delivery accounts.

Status – Lets the system know whether this specific delivery account is open or any other option such as:

Close, On Hold, Paused, Lead Price – This is how much your client is paying for the lead.Delivery Priority – within a client you have the ability to specify the priority of your delivery accounts. This is useful in cases where 1 account should be receiving as many leads as possible.

Click Next to move to Quantity Limits.

Quantity Limits

Quantity limits screen.

Quantity limits allows you to place caps on your delivery account to control lead flow to your clients. For example, this delivery account is set to only receive 10 leads a day. Click Next to continue.

Note: you do not have to place caps. They are there only as a tool for you to use and can be left at 0 to continue.

Criteria Requirements

Criteria requirements are where you can put criteria for this delivery account to ensure that your clients only leads that they want. In this example. This specific delivery account will only take leads within a 10 mile radius of zip code 85303 and has to be in the state of AZ.

Click Save to finish your setup.

Did this answer your question?