Asking company details using domain parameter is returning wrong results sometimes. Some examples being:
1. shop.com
1. eservices.com
1. business.com
While it works fine for some domains like google.com etc.
Query used:
http://api.zoominfo.com/PartnerAPI/XmlOutput.aspx/?CompanyDomain=shop.com&pc=<key>&query_type=company_detail
You are correct about the behavior. The issue appears to be that ZoomInfo doesn't have the three companies you mentioned. If shop.com, eservices.com and business.com were in the ZoomInfo index, their company profiles would be returned. Our crawlers are pretty remarkable but don't capture all companies. There are plans in the works to allow submission of new companies.
Our indexing and matching algorithms for company domain queries lean toward broader recall. I see your point and think that company domain queries should probably do an exact match. I'll look into the possibility of enhancing the API to support exact matching on company domains.
As a workaround, one could compare the queried company domain with the resulting company website element to ensure an accurate match was made.
Asking company details using domain parameter is returning wrong results sometimes. Some examples being:
1. shop.com
1. eservices.com
1. business.com
While it works fine for some domains like google.com etc.
Query used:
http://api.zoominfo.com/PartnerAPI/XmlOutput.aspx/?CompanyDomain=shop.com&pc=<key>&query_type=company_detail
ZoomInfo Admin – 2 years ago
Hi Nakul,
You are correct about the behavior. The issue appears to be that ZoomInfo doesn't have the three companies you mentioned. If shop.com, eservices.com and business.com were in the ZoomInfo index, their company profiles would be returned. Our crawlers are pretty remarkable but don't capture all companies. There are plans in the works to allow submission of new companies.
Our indexing and matching algorithms for company domain queries lean toward broader recall. I see your point and think that company domain queries should probably do an exact match. I'll look into the possibility of enhancing the API to support exact matching on company domains.
As a workaround, one could compare the queried company domain with the resulting company website element to ensure an accurate match was made.
Cheers,
Daryl Gies