.png){kind=logo}
Lead Prosper Error Messages
Rejected by filter: '(field name)' is invalid: This error occurs when there is a filter in place for a field and the value for that field that is passed through doesn't match the filter. For example, if the filter was for zipcodes and it only allowed leads with the zipcode "33098", and a lead had the value "20967" then this error would occur and the lead would be rejected.
Duplicate supplier request: This message is returned if the supplier sends a request where the body of the request matches a prior request from the same supplier sent through the campaign within a 1 minute interval.
Solution:
Error: field '(field name)' has wrong format: This message is returned when your campaign field has a certain format that needs to be followed and the format that is being sent from the supplier doesn't match.
Solution: To fix this, either you need to change the format of the campaign field or you need to reach out to your supplier and ask them to change the format of the field before it's sent to Lead Prosper.
Error: no buyers available: This error will be returned in a multi buyer setup where all buyers failed with different errors. An example of this would be a campaign with 4 buyers, where buyer 1 is not eligible due to a configured filter, buyer 2 is paused, buyer 3 reached his configured cap and buyer 4 received the request, but returned an error.
Solution: Check your buyers configuration. Investigate the logs and make sure everything is setup correctly.
Error: field '(field name)' has wrong value: This error will occur when a value doesn't match one of the set values for a campaign field. For example, own_a_car could have a pick list of either Yes or No and if the value that comes in is anything but one of those two, this error will be raised.
Solution:
Rejected by buyer: This message is returned if the buyer rejected the lead or in case of a buyer configuration error. Lead Prosper needs to check the buyer's configuration after a response was received from the buyer in order to label the outcome of the request. However, if your buyer configuration is not correct, Lead Prosper can't correctly label the request. If everything is setup correctly, then this is not an error, as the lead was correctly rejected by the buyer's system
Solution: Check the logs associated with the request, specifically the buyer's Raw Response section. If you feel that the request was labeled incorrectly, check your buyer configuration and ensure that the ACCEPTED and DUPLICATE messages are correctly configured as per this article: https://support.leadprosper.io/article/61-response-parsing. Feel free to contact our support if this is overwhelming for you
Duplicate data: This error is returned when a supplier sends the same data points as defined by the dupe-checker settings in a request more than once in a 1m interval. This check ignores previous requests status.
Error: lead rejected - daily cap reached: Your buyer has reached it's allowed configured cap
Solution: Check your buyer cap configuration and make sure it is set at your desirable levels
Rejected by 3rd-party integration: One of your configured integration providers has failed to validate the data passed to them
Solution: Please contact Lead Prosper support if you feel any provider is incorrectly marking leads
Duplicated by buyer: This message is returned if your campaign buyer configuration response parsing matches the buyer's response
Solution: Check the logs associated with the request, specifically the buyer's Raw Response section. If you feel that the request was not duplicate, check your buyer configuration and ensure that the check your buyer configuration and ensure that the ACCEPTED and DUPLICATE messages are correctly configured as per this article: https://support.leadprosper.io/article/61-response-parsing. Feel free to contact our support if this is overwhelming for you
Ping not successful: This message is returned if the buyer's system rejected the PING or in case of a buyer PING configuration error. Lead Prosper needs to check the buyer's PING configuration after a response was received from the buyer in order to label the outcome of the PING request. However, if your buyer PING configuration is not correct, Lead Prosper can't correctly label the request. If everything is setup correctly, then this is not an error, as the PING was correctly rejected by the buyer's system
Solution: Check the logs associated with the request, specifically the buyer's PING Raw Response section. If you feel that the PING was labeled incorrectly, check your buyer PING configuration and ensure that the ACCEPTED messages are correctly configured as per this article: https://support.leadprosper.io/article/61-response-parsing. Feel free to contact our support if this is overwhelming for you
Duplicated by dupe-checker: This message is only returned when you have enabled the Dupe-Checker feature for your campaign and a supplier is trying to pass the same data that was accepted previously by your buyers
Solution: If you see a large number of errors, you might want to check that your supplier is sending good lead information and that your campaign Dupe-Checker settings contain enough unique fields. Something unique like a phone or email is better than just a state field, which is too general
Error: could not process request. Contact your campaign manager: Our servers encountered an internal error or misconfiguration and was unable to complete your request
Solution: Contact Lead Prosper Support
Error: invalid request URL: Your request could not be completed due to missing required parameters
Solution: Please ensure all of the following required parameters are sent: lp_campaign_id, lp_supplier_id, lp_key
Error: Field is required: Your request could not be completed due to missing required parameters
Solution: Please ensure all the required fields defined in your campaign are sent
Buyer Server Error: This error is caused by the buyer's server in one of these conditions: the request timed out, server was down and returned a 4XX or 5XX error, DNS errors. Our connect timeout is set to 10 seconds. This is different from their response timeout, which is set at 45 seconds.
Solution: More ofthen than not, the issue is on your buyer's end. In some extraordinary cases, Lead Prosper's network might encounter issues. Contact your buyer and/or Lead Prosper and inquire about possible outages
Error: duplicate lead: This message is only returned when suppliers are dupe checking the campaign with partial data. If your campaign was configured to accept Dupe Checker requests and the data passed was sent before, this message will be returned to your supplier
Solution: If you see a large number of errors, you might want to check that your supplier is sending good lead information and that your campaign dupe settings contain enough unique fields. Something unique like a phone or email is better than just a state field, which is too general
Error: supplier is paused: This error is returned when the supplier has been paused. No leads are stored in the system'
Solution: Resume the supplier from the campaign configuration.
Error: buyer is paused: This error is returned when your buyer has been paused. If all buyers in one campaign are paused, no leads are stored in the system
Solution: Resume the buyer(s) from the campaign configuration
Error: all buyers paused: This error happens when every buyer in a campaign is paused. With no active buyers, incoming leads can’t be processed and will fail to save.
Solution
If you still need to capture leads while your real buyers are paused:
- Create a “dummy” buyer (give it any name).
- Set its delivery method to “Store Lead.”
- Resume the dummy buyer. Now all new leads will be accepted and stored by this buyer.
- Once your regular buyers are ready to go live again, simply pause the dummy buyer and resume your real buyers.
Error: missing or invalid field value - 3rd-party integration missing field: It is possible that one of the required fields by one of our integration providers was not passed.
Solution: Check your campaign configuration and ensure all integrations are correctly saved. If the error persists, please contact Lead Prosper support.
Error: lead validation failed - 3rd-party integration request failed: This message will be returned if there are network issues between our hosting providers and the integration partner network or their service is down or experiencing issues. This error should rarely be triggered.
Solution: Please contact Lead Prosper support if this occurs regularly.
Error: buyer configuration error: This message will be returned in case of a wrong buyer configuration, like URL, payload or headers.
Solution: Check your buyer configuration. Make sure the URL, payload configuration and headers are correct. Contact support if further assistance is required.
Error: account innactive: This message will be returned if the Lead Prosper account is inactive.
Solution: Contact Lead Prosper Support
Error: lead rejected - ping connection failed: This error is caused by the buyer's server in one of these conditions: the request timed out, server was down and returned a 4XX or 5XX error, DNS errors. Our connect timeout is set to 10 seconds. Total allowed execution for the ping request is 30 seconds.
Solution: More often than not, the issue is on your buyer's end. In some extraordinary cases, Lead Prosper's network might encounter issues. Contact your buyer and/or Lead Prosper and inquire about possible outages.
Error: lead rejected - POST conditions not met: This error will trigger when one of the POST conditions defined in your buyer PING/POST configuration is not met. These conditions are executed after a successful PING, right before the POST request.
Solution: Check your request logs and ensure that your PING/POST conditions are correct.
Error: buyer configuration is incomplete: Buyer configuration is incomplete.
Solution: Check your campaign buyers configuration.
Error: lead rejected - Ping did not return a bid: This error applies only to Highest Bidder multi buyer campaigns. This is triggered when the buyer's received PING response does not contain a bid or price, as defined by the configuration. Without it, the buyer is excluded from the list of potential candidates for a request.
Solution: Check your buyer PING price key configuration. Check the request logs and confirm the configuration is correct, as per this article: https://support.leadprosper.io/article/61-response-parsing
Error: lead rejected - cap reached: Your supplier has reached it's allowed configured cap.
Solution: Check your supplier cap configuration and make sure it is set at your desirable levels. Contact your supplier if this error shows up excesively.
Rejected by Supplier filter: A request will return this error if the passed data matched the pattern of a supplier defined filter. This could be an error if the filter was improperly configured and your rejection rate is high. It could also be normal, when the data that the supplier passes does not match the configured filters.
Solution: Check your supplier filters to make sure they are the correctly setup.
Rejected by Buyer filter: A request will return this error if the passed data matched the pattern of a buyer defined filter. This could be an error if the filter was improperly configured and your rejection rate is high. It could also be normal, when the data that the supplier passes does not match the configured filters.
Solution: Check your buyer filters to make sure they are the correctly setup.
Error: PING rejected - PING conditions not met: This error will trigger when one of the buyer defined PING conditions in the PING/POST configuration is not met.
Solution: Check your request logs and ensure that your PING/POST conditions are correct.
Error: PING rejected - No bids available: This error will be returned on a PING request when all buyers failed with different errors. An example of this would be a campaign with 4 buyers, where buyer 1 is not eligible due to a configured filter, buyer 2 is paused, buyer 3 reached his configured cap and buyer 4 received the request, but returned an error.
Solution: Check your buyers configuration. Investigate the logs and make sure everything is setup correctly.
Error: invalid lp_ping_id: The value of lp_ping_id does not match a valid previous PING request.
Solution: Ensure that your POST request is sending the correct lp_ping_id from a previous PING request. The value can be grabbed by reading the "id" from the PING response.
Error: POST sent outside of PING timeout window - PING timeout exceeded: This error is returned when the POST request was attempted after a long time after the PING. Lead Prosper currently allows POST requests to be sent up to 1 hour after the PING request. This limit might be changed in the future.
Solution: Ensure that the POST request is sent after the PING request in the allowed time interval.
Error: POST not accepted due to PING failure: This error will be returned when a POST requests was sent after a PING that failed or PING did not return any bids.
Solution: Ensure supplier POST requests are only sent after a valid PING request.
Error: lp_bids contains invalid bid(s): This error applies only to Shared Ping Post Exchange enabled campaigns. It is caused when a supplier sent a POST request where the lp_bids parameter contains bid ids that do not match the bid ids returned by the PING request.
Solution: Ensure that the POST request contains the correct bid ids from the PING response.
Error: buyer was not found in the PING request: This error happens when a POST request contains buyers that were not present when the PING was sent. This is possible when new buyers are added while the campaign is running.
Solution: No action is needed on your end, requests should start working organically. If this error shows many times, contact support.
Error: buyer configuration changed between PING and POST request: This error happens when a buyer configuration has been changed between the time the system received the PING and the POST request.
Solution: No action is needed on your end, requests should start working organically. If this error shows many times, contact support.
Error: buyer excluded by lp_bids: This error happens in a Shared Ping/Post exchange campaign when a supplier explicitly sends the lp_bids parameter in the POST request and certain buyer bids are left out.
Solution: No action is needed.
Error: buyer was not successful in the PING request: This error happens when a buyer had any kind of error (cap, filters, server, paused) in the PING request.
Solution: Investigate the PING request log to check the exact error that was logged from the PING request.
Error: lp_ping_id was already processed: This error happens if more than one POST request is sent with the same lp_ping_id.
Solution: Make sure that each POST request that is sent corresponds with a unique lp_ping_id. If you need to resend the same lead twice, you have to send a new PING request, get a new id and send it over in a new POST request.
Error: pre-ping dupe checker is not enabled on this campaign: This error is returned when a supplier tries to send a request to a campaign that does not have pre-ping dupe checker API enabled.
Solution: Make sure that your suppliers are aware of the status of the pre-ping dupe checker API.
Error: skipped by repost configuration: Buyers flagged with this error do not receive requests because, at the time of the repost, the buyer was excluded.
Solution: As this is not really an error, nothing is required on your end. If you want to repost leads to this buyer, ensure you selected it from the list before reposting.
Error: lead rejected - Buyer response parse error: This error is returned when our system cannot parse a buyer response.
Solution: Please contact support. Provide the Lead ID or the Request ID, along with the buyer that failed.
Error: supplier budget cap exceeded: This error is returned when the supplier allocated budget was exceeded.
Solution: Check your supplier budget cap configuration and make sure it is set to your desirable levels.
Error: buyer budget cap exceeded: This error is returned when the buyer allocated budget was exceeded.
Solution: Check your buyer budget cap configuration and make sure it is set to your desirable levels.
Error: supplier PING cap exceeded: This error is returned when the supplier allocated number of pings was exceeded.
Solution: Check your supplier PING cap configuration to make sure it is set to your desirable levels.
Error: PING cap exceeded - Buyer PING cap exceeded: This error is returned when the buyer allocated number of pings was exceeded.
Solution: Check your buyer PING cap configuration to make sure it is set to your desirable levels.
Error: PING rejected - Buyer bid lower than supplier required bid: This error is returned when the buyer returned bid is lower than the supplier minimum bid configured.
Solution: Check your buyer supplier minimum bid configuration to make sure it is set to your desirable levels.
Excluded due to bids limit: Bid was excluded in concordance with the bids limit configuration.
Solution: Adjust your lp_max_bids parameter value when sending the ping request