The Match & Enrich API generates an enriched company based on your input criteria. Each company result provides enhanced explainability with a Confidence score (confidence_score) and detailed information on matched attributes Matched attributes (matched_on and attributes ) .

This section will guide you on how to use these attributes effectively to filter and refine the results according to your specific requirements.

Confidence score

The confidence_score attribute is a numerical value ranging from 0 to 1, which indicates the confidence level of the match between the input data and the retrieved company information.

📘
Score value meaning
A score closer to 1 indicates a higher level of confidence in the match, while a score closer to 0 suggests lower confidence.

During the scoring process, two primary factors are considered:

The presence and completeness of the information used for the matching.
The overall relevance of the information in establishing a match.

Completeness

This factor refers to the level of specificity in a particular data point.

For example, if the input address is specified down to the street level, but the API matches at the city level, the match score will be slightly lower compared to a street-level match, especially if there are no other strong signals supporting the same match.

This is done to consider the discrepancies in input and output street information, which typically serves as a highly reliable indicator of a correct match.

Relevance

In this specific context, the term refers to the probability of a particular data point resulting in a successful match.

For example, a company's website is highly relevant as it is generally unique and offers the best chance of a precise match. In contrast, a company name by itself is less relevant due to its common occurrence, making it better to combine it with additional validation, such as an address or phone number, for a more accurate match.

The scoring mechanism also considers the relevance of each Veridion data source used in the matching process. In general, information obtained from a company's website is granted greater weight due to its higher level of reliability compared to data obtained from social media profiles or other online mentions.

👍
Tip
By using the confidence_score, you can establish a threshold to filter out company results that do not meet your desired level of confidence.
For example, setting a min_confidence_score parameter of 0.6 will effectively exclude any API result with a lower overall confidence score.

Matched attributes

The matched_on field returns the set of attributes that were matched against the Veridion database using the provided input ( e.g. company name, location, website etc. ).

For each listed attribute, the attributes field details match information such as confidence scores, values matched, source and type of the match. Some attributes can include additional information.

Attributes and all associated information are listed below:

Company Name

Field	Description	Possible Values	Example
`confidence_score`	A decimal value between 0 and 1, indicating the reliability of the attribute match.	0-1	0.97
`match_type`	Type of match based on name similarity score. Exact - input name matches exactly name on record; legal name exact matches account for variations in the legal termination ( e.g. LTD is the same as Limited ) Fuzzy - input name matches partially name on record; fuzzy matches are never allowed on legal names	Exact, Fuzzy	"Exact"
`match_source`	Source of the matched name on record. Company Commercial Name - the main commercial name of the company Company Legal Names - any of the legal names available on record ( either extracted from the registry or digital footprint, main or historical ) Company Alternate Names - include all names extracted from the digital footprint i.e. secondary/historical names identified on the website, the website URL, or social media	Company Commercial Name, Company Legal Names, Company Alternate Names	“Company Commercial Name”
`value`	Matched company name on record	String value	"Nordic Service Group"

Address

Field	Description	Possible Values	Example
`confidence_score`	A decimal value between 0 and 1, indicating the reliability of the attribute match.	0-1	0.97
`match_type`	Type of match based on address string equality or geo proximity. String equality is performed at address element level, where an element is any of Country, Region, City, Postcode, Street, Street Number. Geo proximity is verified at latitude and longitude coordinates level. Exact - all address elements present in input are present and equal in output, using string equality Partial - address elements are missing or different in input or output Approximate - method checks distance between address coordinates ( lat, long ) in a radius of up to 3km	Exact, Partial, Approximate	"Exact"
`match_source`	Source where the address match was identified Registered - the legal address of registration, as provided by the registry with which this company incorporated. The legal address might differ from the operational (office) locations of the company. Primary - the HQ or primary place of business. It is typically the central hub where the company's core operations are managed, and key decisions are made. Secondary - include all other places where the company maintains a business presence, such as regional offices, branch locations, factories, or stores.	Registered, Primary, Secondary	"Primary"
`match_element`	Specific element of the address matched	Country, Region, City, Postcode, Street, Street Number, Coordinates	"Street Number"
`value`	Matched Location on record, in JSON format, including all location elements	JSON value	`{ "country_code":"DK", "country":"Denmark", "region":"Region Zealand", "city":"Holbæk Municipality", "street":"Tornved Byvej", "street_number":"150", "postcode":"4450", "latitude":55.6515623, "longitude":11.4399789 }`

Website

Field	Description	Possible Values	Example
`confidence_score`	A decimal value between 0 and 1, indicating the reliability of the attribute match.	0, 0.85, 1	0.85
`match_type`	Type of match based on matched domain elements. Exact - when input website matches website on record exactly; accounts for differences in schema ( e.g. www.veridion.com is the same as veridion.com ) Partial - when TLD differs between input website and website on record ( e.g. ikea.com vs ikea.nl )	Exact, Partial	"Partial"
`match_source`	Source of the web domain match	Main Domain, Redirecting Domain, Alternate Domain	"Main Domain"
`value`	Matched website on record	String value	“nordicservicegroup.com”

Phone Number

Field	Description	Possible Values	Example
`confidence_score`	Binary match score, either 0 or 1, indicating the reliability of the attribute match.	0, 1	1
`match_type`	Type of match for the phone number, always Exact	Exact	"Exact"
`match_source`	Source where the phone number was matched Primary - primary phone number used to contact the company Secondary - additional phone numbers linked to the company ( generally front-office phone numbers or departmental contact numbers )	Primary, Secondary	"Primary"
`value`	Matched phone number on record	String value	"+1234567890"

Registry ID

Field	Description	Possible Values	Example
`confidence_score`	Binary match score, either 0 or 1, indicating the reliability of the attribute match.	0, 1	1
`match_type`	Type of match based on the registry data, always Exact	Exact	"Exact"
`match_source`	Type of registry ID matched	VAT, LEI, EIN, TIN, Other	"VAT"
`value`	Matched registry ID on record	String value	"FR45448555268"

👍
Tip
To filter results effectively, you can combine the Confidence score and Match attributes to establish filtering criteria tailored to your specific requirements.
For instance, depending on the input provided, you might consider a Fuzzy match on an Alternate Commercial Name unsuitable, unless the address is fully matched ( address confidence score is 1 ) or the overall confidence score is 0.8 or above.