Breaking Down the Exchange Ping Breakdown Report

The Exchange Ping Breakdown report provides a visual breakdown of the PINGs sent into a Ping Post Exchange. Use it to review supplier and buyer PING activity, identify errors, and optimize exchange performance.

To access the report, select a Ping Post Exchange and set a date range. You can define a custom range or choose from the defaults: Today, Yesterday, Last 7 Days, This Week, Last Week, Month to Date, or Previous Month.

Graph

The top section displays a dynamic graph that can visualize several different metrics across the selected date range:

• Suppliers by Total Requests — each supplier's total PING requests
• Suppliers by Status — each supplier broken down by status (ACCEPTED, ERROR, DUPLICATED)
• Suppliers by Error Group — each supplier broken down by Error Group
• Suppliers by Average Bid — each supplier's average bid price
• Buyers by Total Requests — total PING requests sent to each buyer
• Buyers by Status — each buyer broken down by status (ACCEPTED, ERROR, DUPLICATED)
• Buyers by Error Group — each buyer broken down by Error Group
• Buyers by Average Execution Time — the average time each buyer took to return a response
• Buyers by Average Bid — each buyer's average bid price

Different chart views surface different data points you can use to optimize your Ping Post Exchanges.

Suppliers

This section lists each Supplier and the PINGs they have sent into the Exchange. The following columns are available:

• ID — the lp_supplier_id  for the Supplier
• Supplier — the name of the Supplier
• Total Requests — the total number of PINGs sent into the Campaign for the selected date range
• Status — PINGs are grouped by status: ACCEPTED, DUPLICATED, or ERROR
• Error Group — if the PING status is ERROR, it is further grouped by one of the following Error Groups:
  • NO_BUYERS — no Buyers were available or no Buyers accepted the PING
  • CAP — the Supplier cap was reached
  • DUPE CHECK — the PING included values flagged by the campaign-level Dupe Checker as a duplicate
  • DUPLICATED - OTHER — an internal duplicate check flagged this lead (most likely a Duplicate Supplier Request)
  • FIELD_REQUIRED — the PING was missing one or more required field values
  • FIELD_BAD_INPUT — the PING contained a field value that was improperly formatted or contained an invalid allowed value
  • FILTER — the PING was rejected due to a Campaign or Supplier level filter
• Error Cause — the specific cause of the error, when available. For example, if a PING has an Error Group of FILTER, the Error Cause shows the campaign field whose value triggered the filter.
• Avg Bid — the average bid price returned for Accepted PINGs
• Avg Response Time — the average time it took for the PING request to receive a response from the Campaign

Buyers

This section breaks down the PINGs distributed to each Buyer in the Campaign, including their responses, average bids, and average response times. The following columns are available:

• ID — the lp_buyer_id  for the Buyer
• Buyer — the name of the Buyer
• Total Requests — the total number of PING requests sent to the Buyer
• Status — ACCEPTED, DUPLICATED, or ERROR
• Error Group — if the Buyer PING response is an ERROR, it is further grouped by one of the following Error Groups:
  • NOT_ACTIVE — the Buyer was not active when the PING was sent
  • BID_RULE_ERROR — the Buyer accepted the PING and returned a bid price, but a minimum bid price rule caused the PING to be rejected
  • CAP — the PING was rejected due to a Buyer cap being reached
  • CONNECTION_ERROR — the Buyer's response took longer than the Timeout settings and the connection was dropped or timed out
  • FILTER — the PING was rejected due to a Buyer level filter
  • POST_RULE_ERROR — the PING was accepted, but a Ping Condition Rule set up on the Buyer caused it to be rejected
  • RESPONSE_ERROR — the Buyer PING response contained something other than Accepted
• Error Cause — the specific cause of the error, when available. For example, if the Error Group is FIELD_REQUIRED, the Error Cause shows the campaign field name that is required but had no value.
• Avg Bid — the average bid price returned from the Buyer
• Avg Response Time — the average time it took the Buyer's system to return a response

Every Status and Error Group combination on both the Supplier and Buyer side can be individually exported and downloaded, making it easier to review and optimize by specific issue.

Supplier exports include the following columns: PING ID, Date, Status, Error Group, Error Cause, Supplier ID, Supplier, Duration (time it took to process the PING), Returned Bid(s) (the total bid amount returned to the Supplier), and all campaign fields with their values.

Buyer exports include the following columns: PING ID, Date, Supplier ID, Supplier, Buyer Status, Error Group, Error Cause, Bid Price, Response Time, the Buyer's PING API Response body, and all campaign fields with their values.

Use the date ranges, graph views, and exports together to get a full picture of the PINGs flowing into your Exchanges and each Buyer's PING behavior. Contact support if you need help.