Overview
The Ping Post Response Settings Tab in LeadExec defines how the system processes and interprets responses from clients after sending ping requests. These settings determine whether a ping is accepted, what price buyers are offering, and how to handle specialized response formats. Additionally, handling dynamic values in responses often requires the use of regular expressions to correctly capture variable data.
Key Functionality
Result Search: Identifies successful ping acceptance.
Regular Expression: Enables pattern matching for complex response formats.
Price Search: Extracts bid prices from responses.
Ping During Sort: Required for Ping/Post delivery methods.
Ping Reference Search: Captures ping authentication tokens.
Redirect URL Search: Extracts redirect URLs for form processing.
To handle dynamic values in these fields, a regex (regular expression) needs to be created to correctly capture the variable data. For example:
Result Search:
"Success":true– Checks for a successful response in the returned data.Price:
"Price":"([0-9.]+)"– Captures the dynamic Price value, which can be any number with optional decimals.PING Reference Search:
"PingReference":"([a-zA-Z0-9!&\\.$%@#_-]+)"– Captures the dynamic Ping Reference ID, which can include letters, numbers, and special characters.
Using these regex patterns ensures that the system reliably extracts the correct values even when they change dynamically in each POST.
Please note that these settings are based on the posting instructions for your client’s endpoint and must follow their format. The format may differ depending on whether the endpoint uses JSON or XML:
JSON Example:
Result Search:
"Success":truePrice:
"Price":"([0-9.]+)"PING Reference Search:
"PingReference":"([a-zA-Z0-9!&\\.$%@#_-]+)"
XML Example:
Result Search:
<status>Success</status>Price:
<price>([0-9.]+)</price>PING Reference Search:
<PingReference>([a-zA-Z0-9!&\\.$%@#_-]+)</PingReference>
How to Use This Feature
Navigate to the Response Settings Tab
In your LeadExec account, go to the Ping/Post Delivery Method section and select the Response Settings tab.Configure Result Search
Input the exact success response from your client's API documentation.
Example:"status": "accepted"Enable Regular Expression if Needed
Check the box if the client uses pattern-based responses.
Example:"status\":"accepted"Set Price Search Parameter
Specify the JSON/XML field containing bid price.
Example:"offerPrice":"offerPrice":"([0-9.]+)"Enable Ping During Sort
Check this box for all Ping/Post delivery methods.Configure Ping Reference Search
Specify the field containing the ping reference token.
Example:"PingReference":"([a-zA-Z0-9!&\\.$%@#_-]+)"Set Redirect URL Search (if applicable)
Specify the field containing redirect URLs.
Example:"nextUrl":
Best Practices
Documentation Alignment: Match settings exactly with your client's API documentation.
Request sample responses for accurate configuration.Testing Protocol: Test with sample responses before going live.
Validate price extraction calculations.Regex Considerations: Use simple string matching when possible.
Reserve regex for complex pattern requirements.
Troubleshooting
Pings Not Accepted:
Verify the Result Search matches the client's success response.
Prices Not Captured:
Check that the Price Search parameter matches the response field.
Redirect Failures:
Confirm the accuracy of the Redirect URL Search field.
Next article: Retry Settings Tab>