All Collections
How do I work out why a lead has been rejected?
How do I work out why a lead has been rejected?

Have a rejected lead? Want to know why it was rejected. This article is for you

James Dodd avatar
Written by James Dodd
Updated over a week ago

The following

Simply Rejection Checks

When dealing with rejected leads, the first thing to do is head to leads, and search for the lead you are dealing with.

From here, you can actually see the leads status

Hovering over the Rejected status will give you a quick overview of the rejection reason

Clicking view will bring up the full information, where you can see in this instance, the age isn't greater than 30 as required, as it's set as -1 (don't worry this is just a test example to demonstrate, it's not really a lead).

Client Rejections

When you're dealing with client rejections, there is further information listed under the View Forwarding Info button when viewing the lead.

Below is an example of a client rejection:

The first thing to check is the Raw Response.

This is what your clients system has returned as the rejection reason.

Sometimes it can contain useful information, but it all depends on their system.

This one says:


Now that doesn't take a rocket scientist to work out!

It may contain messages such as duplication, client already exists, request timeout, validations being failed or missing fields etc.

The main thing to do here is keep talking to your client so you can make sure you're giving them to best data possible and they'll be able to confirm anything that's not covered in this error message.

Internal Forwarding

Similar to a client rejection, when dealing with internal forwardings there is further information listed under the View Forwarding Info button when viewing the lead.

This one says:

{"result":"error","lead_id":"94729318" ....

As you can see there is a lead_id here of 94729318
If you search this lead on your databowl instance you will see more details of the lead and how it was rejected.

This is particularly useful if your forwarded lead has a client rejection as it will only be on this new lead, or useful for checking ping tree evaluation results if you're forwarding into a ping tree

Ping Tree Rejections

When working with a ping tree, there is a little more complexity to working out where the lead has been rejected, this is because there are multiple end locations it can be delivered to.

If you find the ping tree lead - this is the lead on the actual ping tree, if you're working with a receiving campaign before the ping tree, please see above for details of how to grab your ping tree lead ID - click Ping Tree Evaluation Results


This page will show you all the campaigns you have set up and will break down where.
It will detail success, rejections, and explain why a lead wouldn't be sent on a ping tree.

Ping tree rejections can include

Matching rejection condition sets/rule groups

Matching suppression file rejections

Missing Fields and Validation messages

Outside the inclusion rules of your ping tree delivery campaign

Outside of the campaign CAP

Suppression File Rejections

|f you're seeing a rejection due to suppression file matches, you can verify this by checking your suppression file settings

Click set mappings from the three dot button

And you'll see what is being matched from the suppression file.

You can now go to the suppression file section of the menu

And then search the value that is matched to confirm it's presence in the file.

Hopefully this helps you understand more about why your leads are rejected.

Good luck and happy hunting

Did this answer your question?