View Categories

Trestle API Response Attribute Ranking

2 min read

When you submit a query to Trestle, some APIs will return multiple results in an array for a single phone number or person. This can include owners/people, addresses, or phone numbers.

Trestle ranks the results in order of confidence when relevant. Here is a list of all the different attributes that are ranked:

These rankings are based on the internal algorithms that use metadata signals from our providers and the association dates between the person or business and addresses, phone numbers, or emails. The rankings help businesses prioritize which phone numbers to call or what addresses to use for maximum engagement with people of interest.

Phone Ranking #

When Trestle enriches a query response with phone numbers, the ranking indicates how confident we are about the association between the person or business and the phone. So, the higher a phone number is in the order, the more confident we are about the phone’s association with the person or business. 

They are not ranked on line type or phone activity. This means that we wouldn’t immediately remove the linkage for a phone with a disconnected signal (low Activity Score) because it might be temporary. Hence, we recommend using our Phone Validation API to check the activity score on those phones to confirm they are active and appropriately decide the prioritization.

Address Ranking #

If we provide an array of addresses in a response, we will also rank these. The ranking for current or historical addresses is sorted by how recently the addresses are linked to the person or business. So, the most recent address linkage to the person is at the top, while the older ones are lower. 

It’s important to note that with addresses, this is not a confidence of the association between person and address but rather a list based on link date.

Person Ranking #

If your search produces a list of people (e.g., Reverse Phone API, Find Person API, or Reverse Address API), the ranking is based on the confidence that the person is the most relevant party for that query.

This could be the person who owns the phone, a resident at an address, or the person you are searching for with a name and location. Each use case has distinct algorithms to determine our confidence and return them from highest to lowest.

  • Reverse Phone API: The owners attribute has a ranked list of people along with their associated information based on the confidence of the owner associated with the phone. This confidence metric is derived from various metadata signals from our data providers, phone and subscriber association start and end dates, etc.
  • Reverse Address API: The current residents’ attribute has a ranked list of residents based on various provider signals and the start and end dates this resident was associated with the address.
  • Find Person API: Find Person API has a complex algorithm that ranks the person array based on numerous variables. For example, how closely a name matches to the input query name or the proximity of the person address to the location searched plays a role in determining how the results should be ranked.

Whenever a query has a hint in the parameters (e.g., Name Hint, Postal Code Hint, etc.), we will consider this in the ranking if it’s relevant and move the appropriate person to the top of the list. We apply name hints first and postal codes second if both are provided and relevant. Here is an article that goes into more detail about how to use the name hint parameter.

Lastly, you can apply our rankings to your call and outreach operations to focus your time and efforts on the highest-ranked results and improve efficiency.

If you have any other questions, let us know via support@trestleiq.com.