.png){kind=logo}
Understanding Lead & Buyer Error Groups
Lead Prosper provides granular error reporting based on the type of error that occurred. Error groups exist at both the Lead level and the Buyer level and serve two purposes:
- Filtering lead reports — narrow down leads in the Lead Reports area by specific error types.
- Campaign Trigger conditions — configure Campaign Triggers to fire only when a specific type of error occurs.
For example, you could set up a Campaign Trigger that alerts a Supplier only when leads are ingested with bad or invalid data, rather than firing on every error. This gives you precise control over automation and more useful reporting when running exports.
Error Groups in Campaign Trigger Conditions
Lead Status Error Groups
| Error Group | Description |
|---|---|
| Not Sold - Any Error | Catch-all for any leads that failed due to any error reason. |
| Invalid Supplier Data | Leads that came in with invalid Supplier data. Includes Missing Required Field, Improperly Formatted Data, and Invalid Values. |
| External Validations | Leads that failed due to a third-party integration. |
| Supplier Cap Reached | Leads rejected because a Supplier cap was reached. |
| Available Buyers - Cap Reached | Leads rejected because all available/eligible buyers are paused due to caps. |
| Invalid Day/Time | Leads rejected due to a Day/Time Parting filter. |
| Rejected By Filter(s) | Leads rejected due to any filters. |
| Not Sold - Buyer Related Errors Only | Leads that failed due to buyer-related errors when an attempt was made to distribute the lead to a buyer. This covers any leads where a buyer returned any response other than the Accepted response mapping. |
Buyer Status Error Groups
| Error Group | Description |
|---|---|
| Any Error | All leads that failed to the buyer for any reason, regardless of whether it was a real-time error or the buyer was not eligible. |
| Real-Time Errors | Leads where the buyer was eligible and the lead attempted to be sold to them, but the buyer returned any response other than the Accepted response mapping. These could range from the lead being unmatched on the buyer's end to the buyer rejecting it due to a misconfiguration. Review these errors to confirm whether a misconfiguration needs to be fixed. |
| Buyer Not Eligible | Leads where the buyer was not eligible for the lead. This can be due to filters, caps, validations, or anything else that would prevent the buyer from receiving that particular lead. |
Error Groups in Lead Reports
Lead Status Error Groups
| Error Group | Description |
|---|---|
| All Errors | Catch-all for any leads that failed due to any error reason. |
| Invalid Supplier Data | Leads that came in with invalid Supplier data. Includes Missing Required Field, Improperly Formatted Data, and Invalid Values. |
| External Validations | Leads that failed due to a third-party integration. |
| Supplier Cap Reached | Leads rejected because a Supplier cap was reached. |
| Available Buyers - Cap Reached | Leads rejected because all available/eligible buyers are paused due to caps. |
| Invalid Day/Time | Leads rejected due to a Day/Time Parting filter. |
| Rejected By Filter(s) | Leads rejected due to any filters. |
| Not Sold - Buyer Related Errors Only | Leads that failed due to buyer-related errors when an attempt was made to distribute the lead to a buyer. This covers any leads where a buyer returned any response other than the Accepted response mapping. |
Buyer Error Groups
| Error Group | Description |
|---|---|
| Any Status | The lead failed to sell to the buyer for any reason. |
| Buyer Not Eligible | Leads where the buyer was not eligible for the lead. This can be due to filters, caps, validations, or anything else that would prevent the buyer from receiving that particular lead. |
| Real Time Errors | Leads where the buyer was eligible and the lead attempted to be sold to them, but the buyer returned any response other than the Accepted response mapping. These could range from the lead being unmatched on the buyer's end to the buyer rejecting it due to a misconfiguration. Review these errors to confirm whether a misconfiguration needs to be fixed. |
| Ping Errors | Leads where a PING was sent to the buyer but failed for any reason. |
| Ping Conditions (Not Met) | Leads where a PING was sent to the buyer but the POST was never sent because PING conditions on that buyer were not met. For example, a PING is sent and the buyer returns a bid price of $2.00, but the buyer has a PING condition rule requiring the real-time price/bid returned to be greater than $4.00. |