Using LeadPoint.aspx

TSL Ping Tree > Page Usage

Using LeadPoint.aspx

A Lead Point is a destination in a Ping Tree. It is based on an Interface for a particular Lead Buyer along with pricing, e.g.

 
Configuration Item Description
Name Provide a name for this Lead Point up to 255 characters.  It need only be unique within the same Lead Buyer, so for example "Tier 1" is a perfectly valid name to use across multiple Lead Buyers.
Lead Point UID This is a display only field that shows the Lead Point's internal Unique identification number.
Lead Buyer Interface Select a Lead Buyer Interface.
Lead Buyer Accounting Code Up to 36 characters that identifies the lead from the Lead Buyer's accounting perspective.
Post Url Production The URL that will be posted to when this Lead Point is not in Test Mode. It can be any valid HTTP or HTTPS URL using any valid token substitution strings. See Token Substitution for information on substitution strings.
Production SSL Certificate Acceptance This allows you to set what SSL certificate issues you will ignore when posting to the Production URL. The options are:

Must Be Valid - Requires the SSL to be valid.  It must be signed by a recognized certificate authority and can not be expired. It is highly recommended that you use this setting for production posts.   With this setting posts to hosts with self-signed certificates will fail.

Host Name Must Match - Requires the host name you are connecting to to be contained in the Subject section of the SSL certificate.  The Subject section includes the CN (common name) section which should be the DNS name you are using to connect to the host.

Any - This setting will allow a successful post to host with any SSL certificate even if the host name is not set properly in the certificate.  This setting should only be used as a last resort to make a production post work.

Post Url Test The URL that will be posted to when this Lead Point is in Test Mode. It can be any valid HTTP or HTTPS URL using any valid token substitution strings. See Token Substitution for information on substitution strings.
Test SSL Certificate Acceptance This allows you to set what SSL certificate issues you will ignore when posting to the Test URL. The options are:

Must Be Valid - Requires the SSL to be valid. It must be signed by a recognized certificate authority and can not be expired. With this setting, posts to hosts with self-signed certificates will fail.

Host Name Must Match - Requires the host name you are connecting to to be contained in the Subject section of the SSL certificate. The Subject section includes the CN (common name) section which should be the DNS name you are using to connect to the host.

Any - This setting will allow a successful post to host with any SSL certificate even if the host name is not set properly in the certificate.

Disable Old Certificate Types This disables old certificate types that are now considered insecure (SSL and TLS 1.0). The preferred setting for this is checked to enhance security. The currently supported versions when you check this setting are TLS 1.1 and TLS 1.2.
Receivable Event This determines if and when a receivable will be generated:

Never - No receivable event will be generated.

On Accept - A receivable event will only be generated on an Accept.

On Any Response - A receivable event will be generated on any response. If a filter blocks the lead from being posted or if a timeout occurs no receivable event will be generated.

On Post - A receivable event will be generated on any post. If a filter blocks the lead from being posted no receivable event will be generated.

Receivable Amount is Dynamic If checked this indicates that the receivable amount is dynamic and will be the value from the reported receivable amount from the response of the post to the Lead Buyer.
Minimum Receivable Amount This is only applicable for dynamic lead points that book receivables. This value is used to determine if a lead is sold below your expected minimum sale price for this Lead Point.  If this occurs a warning is logged, the sale is allowed, and the Lead Point is disabled.  This feature is intended to automatically prevent you from distributing leads to an interface that breaks its contract with respect to what should be returned in an Accept response.  If you do not wish to automatically disable based on the amount found in the response then set this to zero.
Maximum Receivable Amount This is only applicable for dynamic lead points that book receivables.  This value is used to determine if a lead is above below your expected maximum sale price for this Lead Point.  If this occurs a warning is logged, the sale is allowed, and the Lead Point is NOT disabled.
Receivable Amount This is only applicable for fixed price lead points. This is the amount of the receivable that will be generated when a Receivable Event occurs.
Redirect URL Required in Response If this is checked then all responses for Accepted leads must contain a redirect URL.  If an Accept response is received without a redirect URL then an internal error is logged and the Lead Point is automatically disabled.  This feature is intended to automatically prevent you from distributing leads to an interface that breaks its contract with respect to what should be returned in an Accept response.  Only check this checkbox when you are certain that valid accepts will always return a redirect URL and you want to automatically disable the lead point whenever this isn't the case.
Static Accept Redirect URL If this redirect URL is specified, then it is used on any Accept regardless of the reported redirect URL.
Daily Limit Timezone This determines what timezone is used to determine the start and end times for a day with respect to daily limits.
Daily Submit Limit This sets the maximum number of submits that can be made to a Lead Point in one day. If it is left blank, then there is no limit.
Daily Accept Limit This sets the maximum number of Accepts that can be received on a Lead Point in one day. If it is left blank, then there is no limit. Once this limit is reached, no more submits happen on the current day. Note that because of the multithreaded nature of TSL PingTree it is possible for two simultaneous posts to receive Accepts and thus cause a slight overrun of this limit. For that reason if you have a hard limit that can not be exceeded you should set this value slightly lower than the hard limit.
Test Mode If this is checked then the Lead Point is considered to be in Test Mode.  This causes the following to happen:
  • Where specified, test expressions are used in field mappings.
  • Leads are posted to the Test URL instead of the Production URL.
  • The disposition of Accepted is changed to "Accept Treated As Decline Due To Test Mode".
  • No receivable event is generated and an internal message is logged.

Note that the auto-disable features for Accept responses for both redirect URLs and minimum receivable amounts works the same regardless of whether the Test Mode checkbox is checked.

Enabled Determines if this Lead Point is enabled.
Notes This is used for you to add any descriptions about the interface that you want.
Lead Point Variables

Lead Point Variables (LPV) are used to provide values that change for each Lead Point. A common use for this is when you are posting to one lead buyer with the same format post but at different price levels.

Let's say that the lead buyer has a parameter called "LVL" which is set to either "A" or "B" depending on the price level.  You could define a LPV called "Level" and reference it in the mapping for the Interface parameter LVL.

Name - Select the name of the Lead Point Variable

Value - The value of the Lead Point Variable

Filters

You can attach filters specific to the Lead Point here.

Filter - Select the Lead Point Filter to attach to this Lead Point

Duplicate Rules

You can attach duplicate rules specific to the Lead Point here.

Duplicate Rule - Select the Duplicate Rule to attach to this Lead Point

See also: