Integrations > Salesforce > Enrichment tab
Before HG can add firmographic, technographic or IT spend data, it has to work out which HG company each Salesforce Account or Lead is. These three settings control that step and what comes back.ntent goes here
This page corresponds to STEP 3 of the CRM enrichment setup guide.
Tweaking any of these is optional and entirely depends on your usecase and Salesforce setup. CRM enrichment works well without it.
Country Level Matching
This sends each record's country along with the website and name. A country that agrees with the candidate company adds weight to that match.
Which Salesforce field it reads:
On Accounts you choose BillingCountry or ShippingCountry.
On Leads it uses the standard Country field.
What it can't do: Country is a tiebreaker and can't create a match on its own. A record with no website and no usable name still won't match, and a wrong country doesn't exclude a company.
Use it when: You have many accounts using the same domain but based in different countries, such as regional subsidiaries. It helps most when the country data is clean.
Watch out for: Turning it on or off flags your Accounts for a re-match. Check the credit estimate before you confirm.
Localized Installation
What it does: It changes which technology installs HG returns, not how records are matched. Off means installs are reported for the company wherever they were detected. On means installs are reported per country, and only installs detected in the same country as the company are returned.
Where it applies: It applies to HG Technographic records (product installs) and to account scoring that depends on installs. It does not change firmographics or IT spend.
Use it when: The customer sells or supports by country and wants a company's tech stack in their own territory. A US parent's installs in another region would otherwise show as that company's stack.
Expect: Fewer install records per company, and some companies with none.
Watch out for: Changing it does not automatically re-enrich records you already enriched. To refresh existing data, ask Support for a Full Sync.
HG ID matching
What it does: It lets you tell HG which company a record is, instead of letting HG guess. You fill a custom Salesforce field with the company's HG ID. When it's on, HG uses that value first, and it outranks every other signal.
Setup:
Create a text field on Account and/or Lead. The default API name is
HGInsights_CustomerManaged_HGID__c. It is a field you create, not one the package installs.Populate it with HG IDs.
Turn the toggle on.
Use it when: You have a trusted mapping from a previous match, a data vendor or a manual clean-up, and want to fix records that match the wrong company. It is also the way to settle wrong-subsidiary matches.
Requirements: Managed package 1.11 or later.
Watch out for: Switching it triggers a re-match of Accounts. Records with a blank field fall back to the default signals.