Overview
The Ping Post Response Settings tab tells LeadExec how to interpret and process the buyer’s response after a PING request is sent. These settings determine whether the ping was accepted, what payout was returned, and which transaction or reference ID should be used during the POST step.
This section is especially important for Ping/Post delivery methods, since the values returned during the PING are often required later during the POST request.
LeadExec supports multiple response parsing formats:
JSON
XML
Custom
The selected format determines how LeadExec reads and searches the response data.
For standard JSON and XML responses, you can usually configure the fields using simple key/value matching without needing regular expressions.
The Custom format is intended for advanced or non-standard response structures where regex pattern matching may be required.
Important: Always obtain a sample response from the client’s API documentation before configuring the Response Settings. If the documentation does not include a successful response example, request one directly from the client. Knowing exactly what a successful response looks like is critical for properly configuring the Success Response, Bid Price, and PING Reference ID fields.
Response Formats
JSON
Use this option when the buyer returns a standard JSON response.
Example:
{
"Success": true,
"Payout": "50.00",
"TransactionId": "104316639974"
}
In most JSON configurations, you only need to provide:
Setting | Value |
Success Response Key |
|
Equal to the value |
|
PING Reference ID |
|
Bid Price |
|
XML
Use this option when the buyer returns XML responses.
Example:
<Response>
<Success>true</Success>
<Payout>50.00</Payout>
<TransactionId>104316639974</TransactionId>
</Response>
Example configuration:
Setting | Value |
Success Response Key |
|
Equal to the value |
|
PING Reference ID |
|
Bid Price |
|
Custom
Use the Custom option only when the buyer’s response does not follow a standard JSON or XML structure, or when values must be dynamically extracted using pattern matching.
This format supports regular expressions (regex) for advanced parsing.
Example regex patterns:
Purpose | Regex Example |
Success Detection |
|
Price Extraction |
|
PING Reference ID |
|
These expressions allow LeadExec to capture dynamic values that may change with every request.
Key Functionality
Success Response
Defines what LeadExec should look for to determine if the ping was accepted.
Example:
Field | Value |
Key |
|
Equal to the value |
|
PING Reference ID
Specifies the field that contains the buyer’s transaction or ping reference token.
This value is commonly required later during the POST request.
Example:
Field | Value |
Key |
|
Bid Price
Defines which field contains the payout or bid amount returned by the buyer.
Example:
Field | Value |
Key |
|
Enable Ping during Sort
This setting should be enabled for all Ping/Post delivery methods.
When enabled, LeadExec executes the ping during the sorting process to retrieve the buyer’s real-time payout.
Successful pings update the account ranking using the returned payout.
Failed pings exclude the account from selection.
How to Configure
Navigate to the Response Settings (PING) tab within your delivery method.
Select the appropriate Response Format:
JSON
XML
Custom
Configure the Success Response:
Enter the response field name.
Enter the expected success value.
Configure the PING Reference ID field.
Configure the Bid Price field.
Enable Ping during Sort for Ping/Post delivery methods.
Save the configuration.
Best Practices
Always match the configuration to the buyer’s API documentation.
Use JSON or XML formats whenever possible.
Only use Custom when regex or advanced parsing is required.
Test using sample responses before enabling the delivery method in production.
Verify that the payout and transaction ID are being captured correctly.
Troubleshooting
Ping Not Accepted
Verify the Success Response key and value exactly match the buyer’s response.
Payout Not Captured
Confirm the Bid Price field name matches the response field.
Missing PING Reference ID
Verify the correct transaction/reference field is configured.
Custom Regex Not Working
Validate the regex pattern against a real sample response from the buyer.
Ensure escape characters are properly formatted.
Next article: Retry Settings Tab>