Ping Post Definitions
This page outlines several ping post definitions and explains the terms that are used within a boberdoo.com lead distribution system. If you are looking for more information regarding ping post, please visit our ping post/ping tree page.
Ping Post Definitions and Descriptions In Your boberdoo.com System
Listed below are a set of ping post definitions and descriptions for the terms that appear within your boberdoo system. These definitions cover the key elements of ping and post requests, response fields and matching logic used throughout the platform.
Request Fields
Data
The Data element contains the appropriate lead data tags for the ping or post request. The specific fields and format vary depending on the lead type being submitted. Each lead vertical has its own set of required and optional data fields that must be included in the request.
Matches
The Matches element is used when a lead has already been sold by the vendor and the vendor wants to indicate existing matches. This is an optional element that allows vendors to communicate prior sales to prevent duplicate distribution.
Match
The Match element contains information about a specific match, including hashed or unhashed values for identifying data such as phone number, email address, company name, promotion code and partner group. Each Match entry represents one prior sale of the lead.
Match_With_Partner_Hashes
This element is used to request that the lead be matched with specific partners using the partner hashes returned in the ping response. By including partner hashes from the ping step, the vendor can direct the post to specific buyers who expressed interest during the ping.
Match Properties
ValueType
ValueType is a property of the Match tag that describes the type of data being provided for matching purposes. Allowed values include email, phone, company, promotionCode and partnerGroup. This tells the system how to interpret and compare the match data.
HashType
HashType is a property of the Match tag that indicates the hash algorithm used to encrypt the match value. The allowed values are sha1 and md5. When match data is hashed for privacy, the HashType tells the system which algorithm to use for comparison.
Selected_Partner_Hash
The Selected_Partner_Hash is the unique hash identifier of a specific partner that the lead is being requested to match with. This value is obtained from the ping response and used in the post request to direct the lead to a chosen buyer.
Response Fields
Status
The Status field indicates the result of the ping or post action. Possible values are Matched (the lead was successfully matched to a buyer), Unmatched (no buyer match was found) or Error (the request encountered a processing issue). Always check the Status field to confirm successful lead submission.
Lead_id
The Lead_id is the unique ID number assigned to a successfully submitted lead. This value is returned upon a successful post and serves as the primary reference for tracking, reporting and any future actions related to that specific lead in the system.
Price
The Price field returns the best price at which a lead can be accepted. This value is returned on a successful ping response when price information is requested. It represents the highest bid from matched buyers and helps vendors decide whether to proceed with the post.
Redirect URL
The Redirect URL is returned when the matched buyer requires the consumer to be redirected to a specific landing page or thank-you page after lead submission. Include this URL in your post-submission flow to ensure a seamless consumer experience.
Learn More About Ping Post
Visit our [ping post page](/ping-post) for a complete overview, or schedule a demo with one of our lead distribution experts.