Overview
The Ping Order List screen provides visibility into inbound Ping/Post activity within your LeadExec account. From this screen, you can review incoming ping requests, determine whether a ping was accepted, see which clients matched, and track whether the corresponding lead was successfully posted and sold.
The Ping Order List is particularly helpful for troubleshooting Ping/Post campaigns, reviewing client eligibility, and understanding how accepted pings translate into actual lead deliveries and revenue.
You can also access detailed request and response information, review client scan logs, and view the lead information associated with each ping.
Filtering and Reviewing Ping Orders
The Ping Order List provides several options to help locate and review specific ping requests.
Dates: Select a date range to review ping activity during a specific period.
Lead Type: Filter the list to display ping requests associated with a particular lead type.
Column Filters: Use the available filters and search options to narrow your results.
Refresh: Refresh the list to retrieve updated ping order information.
Select a row to review a specific ping request, then use the options in the main toolbar to access additional details.
Main Toolbar Options
The main toolbar provides access to additional information about ping requests, lead deliveries, and the client scan process.
View Send Information
Opens the Lead Deliveries window to display delivery activity associated with the selected ping order.
From this window, you can review:
Clients and delivery accounts associated with the lead.
Delivery date and time.
Whether the delivery was accepted, rejected, returned, or is pending.
Order and invoice information, when available.
Delivery price and revenue.
Delivery logs and process diagrams.
The request and response associated with a delivery attempt.
This is particularly useful when determining whether an accepted ping resulted in a successful lead sale.
View Lead
Opens the Lead Details window for the lead associated with the selected ping request.
From here, you can review:
General Information: Lead UID, lead type, lead source, campaign, and date received.
Lead Info: The lead fields and information submitted by the lead source.
Deliveries: Delivery attempts, client responses, and delivery history.
Properties: Lead status, revenue, send counts, and other lead properties.
Integrations: Available integration results, such as TrustedForm or phone validation services.
Additional Information: Files, appointments, offers, and TCPA information, when applicable.
This option is helpful when reviewing the full lead record or investigating why a posted lead was or was not delivered successfully.
View Scan Log
Displays the client scan log associated with the selected ping request.
The scan log provides a detailed record of how LeadExec evaluated the ping against the configured client distribution requirements.
Depending on the configuration and processing activity, the log can help you review:
When the client scan started.
Which delivery groups and distribution lists were evaluated.
How clients were filtered during the qualification process.
Which clients qualified for the ping.
The progression of the client scan.
Tip: If a ping did not match an expected client, start by reviewing the Scan Log to better understand how the system evaluated the available delivery opportunities.
View Request
Opens the Insert Request window, where you can review the original ping request and the response generated by LeadExec.
This window provides important information, including:
Ping Log ID
Request ID
Order ID
Lead UID, when applicable
Lead source and campaign
Date and time of the request
Whether the ping was accepted
Request and response formats
You can also view the original JSON request and response data to understand exactly what was submitted and how LeadExec responded.
This is particularly helpful when troubleshooting API integrations, rejected pings, missing lead fields, or unexpected responses.
Tip: Use View Request when you need to compare the response returned by LeadExec with the response recorded by your lead source.
Export
Export ping order information for reporting, troubleshooting, or further analysis.
Two export options are available:
· Export all data: Export the data available from the current list.
· Export selected rows: Export only the ping orders you have selected.
Exporting is useful when reviewing ping activity over a specific date range or comparing accepted pings with actual lead sales.
Choose Columns
Customize the Ping Order List by selecting which columns you want displayed.
Use the Column Chooser to find and add available columns to your list. You can also adjust the order of columns to organize the information most relevant to your workflow. To add or remove a column drag and drop the column header to or from the Column Chooser modal.
For example, you may want to display Request ID, Order ID, Accepted, Potential Sends, Actual Sends, and Actual Revenue together when monitoring Ping/Post performance.
Restore Layout
Restores the Ping Order List column layout to the system default.
Important: This will reset any custom column ordering you have configured.
Understanding the Ping Order List Columns
The Ping Order List contains several columns that provide insight into ping acceptance, client matches, lead delivery, and revenue.
Ping Request and Order Information
Column | Description |
Created On | The date and time the ping was validated and LeadExec sent a response back to the lead source. |
Request ID | A unique identifier generated by LeadExec to record and track the incoming request in the database. |
Order ID | A unique identifier generated when a ping is accepted. This identifies the accepted ping order and can be used when submitting the corresponding full lead. |
Expires | The date and time the accepted ping's Order ID expires. |
Accepted | Indicates whether the ping request was accepted by LeadExec. |
Matched With | Identifies the client or clients that matched the ping during the client scan process. |
Lead Posting and Delivery Information
Column | Description |
Received | Indicates whether the full lead was posted to LeadExec following the ping request. |
Lead UID | The unique LeadExec identifier assigned to the full lead when it is posted into the system. |
Potential Sends | The number of times an accepted lead can potentially be sold based on the qualifying delivery opportunities. |
Actual Sends | The number of successful lead sales. This represents how many clients successfully received and accepted the full lead. |
Important: An accepted ping does not necessarily mean the corresponding full lead was posted or sold.
For example, a ping may be accepted and assigned an Order ID, but if the lead source does not submit the full lead, the order may have no actual sends.
Similarly, a full lead may be received but fail to result in a successful delivery.
Revenue Information
Column | Description |
Potential Revenue | The calculated potential revenue based on the matching client's delivery account pricing, minus the lead cost. |
Actual Revenue | The revenue generated from successful lead sales, minus the lead cost. |
Potential Revenue represents the anticipated revenue opportunity, while Actual Revenue reflects completed sales.
For successfully sold leads, Actual Revenue should align with the applicable Potential Revenue calculation. If the values do not match as expected, review the delivery details and associated pricing.
Understanding Ping Acceptance vs. Lead Delivery
One of the most important distinctions when reviewing the Ping Order List is the difference between a ping being accepted and a full lead being successfully sold.
A typical Ping/Post workflow includes the following steps:
1. Ping Received: A lead source submits a ping containing the information needed for client qualification.
2. Client Scan: LeadExec evaluates the ping against available clients and configured distribution requirements.
3. Ping Response: LeadExec returns the applicable response to the lead source. An accepted ping is assigned an Order ID.
4. Full Lead Posted: The lead source submits the complete lead using the accepted ping order.
5. Lead Delivery: LeadExec processes the full lead for delivery to the applicable clients.
6. Revenue Recorded: Successful lead deliveries are reflected in Actual Sends and Actual Revenue.
An accepted ping indicates that LeadExec accepted the ping request, but it does not guarantee a completed lead sale.
Reviewing these stages helps distinguish between client coverage, ping acceptance, full lead submission, and successful distribution.
Best Practices
Monitor Accepted Pings vs. Actual Sends: Compare accepted ping orders against successful deliveries to understand how many accepted opportunities result in sales.
Review Expired Orders: Check the Expires column when a lead source reports issues posting a full lead after receiving an accepted ping response.
Use Scan Logs to Troubleshoot Client Matches: Review the client scan process when a ping does not match an expected client.
Review Request and Response Data: Use View Request to verify the data submitted by the lead source and the response returned by LeadExec.
Monitor Potential and Actual Revenue: Compare revenue values to identify differences between anticipated and completed sales.
Customize Your Columns: Arrange the most relevant columns together to make reviewing ping activity and troubleshooting easier.
Troubleshooting
Ping Was Accepted, but No Lead Was Received
If the Accepted column shows Yes, but Received shows No, the ping was accepted, but the corresponding full lead was not recorded as received.
Review the Order ID and expiration time. You can also use View Request to inspect the original response and confirm that the lead source received the accepted ping order information.
Ping Was Accepted, but Actual Sends Is Zero
An accepted ping does not guarantee a successful lead delivery.
First, confirm whether the full lead was received. If it was, use View Send Information to review delivery attempts and the responses returned by the receiving clients.
Expected Client Did Not Match
Open View Scan Log to review the client scan process.
Check the client's distribution requirements, geographic coverage, schedule, order availability, and other applicable qualification settings to determine why the client may not have qualified.
Order ID Is Missing
Order IDs are generated for accepted pings. If the ping was rejected, an accepted Order ID may not be available.
Use View Request to inspect the response and determine why the ping was not accepted.
Actual Revenue Is Different Than Expected
Review the successful deliveries associated with the ping order and confirm the pricing configured on the relevant client delivery accounts.
Compare the delivery price, lead cost, and actual sales to better understand the recorded revenue.
Related Articles