Company identification for exports and syncs
At the most fundamental level, 6sense must match its Master Company Database (MCD) records to your CRM records to perform various enrichment functions in Data Workflows.
6sense leverages domain, country, and name fields to create a single source of truth in our MCD. Here’s how each attribute plays a role in matching:
Web Domain is the primary identifier: A company’s web domain is the most unique and stable attribute for identification. It helps 6sense distinguish between organizations even when company names are similar, such as “Acme Inc.”, in different industries.
Country name ensures regional accuracy: Many companies operate globally under the same domain but have separate regional entities. Including the country name ensures that your insights and engagement strategies align with the correct geographic market.
Company name for additional context and validation: Company names provide an additional layer of verification. This helps confirm matches when domains are shared (such as with parent companies and subsidiaries) or when domain information is incomplete.
Headquarters location for consistency: 6sense prioritizes HQ location in account records to ensure consistency. This means the primary account in 6sense reflects the company’s global headquarters, even if there are multiple regional offices.
For a deeper discussion refer to the RevCity post on Country vs. HQ Account Creation.
Headquarters matching in Data Workflows
Companies organize accounts in their CRM in different ways. Your organization may prioritize country-level hierarchies, while others consolidate everything under a single global HQ. 6sense supports both of these approaches when matching 6sense data to your CRM data. To learn how Data Workflows supports headquarters (HQ) matching refer to HQ Matching in Data Workflows.
Headquarters views in Sales Intelligence
To learn how Sales Intelligence shows headquarters information, refer to HQ Views in Sales Intelligence.