Restrict Location Matching
This feature will restrict the LS Match (BU) entity to be the same country as the input. This feature allows Leadspace customers to ensure that the LS Match results (usually found in the 'company' level fields) will bring back a company's entity that's located in the country that was initially specified as input.
The benefit of this feature is ensuring that inbound records are assigned to the correct countries based on the lead location, versus for example the headquarters location. The downside is that often the lead location does not match the company location, and in these instances the record is changed to 'not enriched', therefore reducing overall enrichment rates.
Why Do Customers Need This?
-
This feature was added following specific requests from customers that their data is very location-oriented.
-
The feature allows customers to ensure that the LS Match (Business Ultimate) will bring back a company's entity that's located in the country that was initially specified as input.
-
It is important for customers to be confident in their input location data in order to initiate this feature.
-
Use Case
If the location you send in as input does not exist, we will still want to provide the social entity
-
Example:
-
Input Company: Leadspace
-
Input Country: South Africa
-
Output Company: Leadspace
-
Output Country = United States
-
Why: We did not find Leadspace in South Africa so fell back to the BU (social entity)
-
From a Person perspective, a lead can be anywhere in the world. If we use the person’s country as the company country as input instead of returning Not Enriched, we still want to know the information on the company as a whole
Restrict Location Matching Logic
-
We will try to find the entity in the Input Country; a comparison between the input country (if populated) and the LS match country is completed
-
We put the DU into the LS Matched Level
-
If there is no entity found in the Input Country, we will fallback to the main enrichment flow of Social Entity (BU) and the company-level data is replaced with BU data where available.
-
RLM On
-
LS matched = Find against Input Country / DU
-
Fall Back: BU
RLM Off
-
LS Matched = BU
-
No Fall Back = main enrichment flow
|
input "company": { |
"country": "Brazil", |
Because we couldnt find Vale Europe in United Kingdom, we defaulted to their Social Entity (BU) of Brazil. |
"country": "Brazil", |
|
"company": {
"name": "Leadspace", "website": null, "phone": null, "address": { "city": null, "state": null, "country": "south africa" |
"address": {
"country": "United States", "state": "CA", "city": "San Francisco", "zipcode": "94025", "region": "North America" |
We did not find Leadspace in South Africa and defaulted back to Leadspace social Entity (BU) of United States (HQ) |
"address": { |
|
"company": { |
company": { |
We did find Deloitte in South Africa and matched it to the same company input. If there was no Deloitte in South Africa, we would have LS Matched to United States as this is the Social Entity (BU). |
"address": { |