When using Real Contact API, it’s possible to receive a name match attribute response of “null” for phone to name, email to name, or address to name match.
Missing Input #
Real Contact API requires a name and phone number at a minimum. If a required input is not provided, all attributes except for the warnings will be null. Additionally, if an optional input like email address or address is not included in the request, a “null” response is expected in the name match field.
Null Response When an Input Is Provided #
It’s possible to receive a “null” response for a name match even if you provide a name in the request. Sometimes, Trestle does not have a name for a particular phone number or email address in its record.
Generally speaking, our coverage for phones (and other attributes) is over 90%, so this should not happen often. Suppose a null response happens more often than our coverage percentage suggests. In that case, this may be an indication of lead quality or an issue with the way the integration is passing the request parameters, so please re-verify the parameters as per the documentation.
In addition to a lack of coverage for a name, it’s possible that our identity graph only has a business name associated with a particular phone, email address, or physical address. In these cases, we will not provide true or false. This is because we assume that the input name is a person’s name, and trying to match a person with a business can result in false positives/negatives.
This logic applies to the following attributes:
- Phone to Name Match
- Email to Name Match
- Address to Name Match
If you have questions about this or want to discuss it further, please email us at support@trestleiq.com.