At a glance
Lead-to-account matching connects a person to the company record your CRM uses for ownership and reporting. Define how operating businesses, parent groups and shared email domains should be handled. This guide gives marketing operations teams a rule hierarchy and a review process for uncertain records.
A new lead arrives and your CRM recognises the email domain. It links the person to a large parent group and assigns an owner. Everything looks complete, except your sales team covers the subsidiary separately and the lead has gone to the wrong colleague.
That’s why a populated account field isn’t enough. The association determines who follows up, whether the contact belongs in your target list and how you report engagement. A wrong match can look tidy while quietly changing several campaign decisions.
A matching decision your delivery team can reproduce
Use a short decision record when a domain does not settle the account. Consider this illustrative record: the supplied company is Northbridge Group, the email uses the parent domain, the verified employer is its industrial subsidiary, and the person’s operating location is the UK. The campaign brief includes that subsidiary but excludes other divisions.
The matching decision is to retain the parent relationship for group reporting and associate the response with the approved operating entity for this campaign. The reason is verified employment and location, not the email suffix alone. If employment is unconfirmed, the record stays unresolved; a plausible association is not sufficient for an account-specific claim.
Keep the supplied value, resolved entity, evidence, date, reviewer and exception reason together. Then test the downstream consequence: does the accepted association preserve campaign eligibility, and does sales see the same business? Our lead-generation methodology explains the campaign checks and delivery fields we agree. Your CRM team owns how those agreed relationships are represented in its system.
This article concerns which company the person belongs to. Whether that person counts as a new billable lead and who should follow up are separate decisions. Resolve identity first so neither commercial counting nor routing has to compensate for an uncertain match.
Agree which account should own the lead
Start with the campaign’s account unit. Is the target an operating company, a group, a country business or an individual site? The same person can be correctly linked to a parent for consolidated reporting and to a subsidiary for sales ownership.
Keep those relationships in separate fields or associations. Don’t make one account field carry several incompatible meanings. The primary commercial account, employer and reporting parent may need different treatment.
Document which relationship governs each action. Routing might follow the operating account owner. Group-level reporting might roll up to the parent. Suppression might apply to the entire corporate family if the brief explicitly requires it.
Set the order in which matching evidence takes precedence
Adobe’s matching documentation describes several inputs rather than relying only on a company name. HubSpot’s deduplication documentation also distinguishes email, domain and record identifiers, with behaviour varying by creation route. These product rules should be checked against your own entity model.
| Evidence | Suggested treatment | Main caution |
|---|---|---|
| Verified existing account ID | Preserve unless new evidence contradicts it | A historic association may be stale |
| Exact approved domain and entity | Match when the domain is unambiguous | Shared group domains can conceal subsidiaries |
| Verified employer plus location | Match after resolving the operating business | Similar names can refer to different entities |
| Parent-domain relationship | Link the parent and investigate the operating entity | Don’t assume the parent owns every local purchase |
| Fuzzy name similarity | Create a candidate for review | Similarity isn’t proof of identity |
| Personal email or conflicting evidence | Hold in an exception queue | Don’t force a match to improve coverage figures |
Use this order as a starting point for your own CRM rules. A verified account relationship should generally carry more weight than a new, weak resemblance, but you still need a way to review it when someone changes employer or the business structure changes.
How a shared domain can hide different businesses
Suppose Northbridge Group owns Northbridge Services and NBS Industrial. Some staff use the group domain, while others use a subsidiary domain. The campaign targets only the industrial business in the UK.
A group-domain contact with a verified industrial operations role may be eligible after review. A contact using the same domain in the group’s retail division isn’t eligible merely because the domain matches. A Canadian industrial contact may also fall outside the geographic brief.
Store the group parent, operating entity and person location separately. Record why each person was included or excluded. If the client later approves another division, the existing evidence can support a controlled change rather than a fresh guess.
In that example, the email domain helps identify the corporate family; it doesn’t settle campaign eligibility. Your brief and sales ownership model still determine which operating business matters. Keeping those decisions separate lets you fix one without rewriting the other.
Give uncertain matches an owner and a next step
Give each unresolved record a reason: multiple candidate accounts, shared domain, missing employer, conflicting location or possible job change. Assign an owner and a review deadline suited to the campaign.
The reviewer should see the original values and the candidate matches, not just a blank account field. Include the evidence date and source. Record the decision, reason and reviewer so later corrections are traceable.
Set a safe interim route. An unresolved contact might be held from an account-specific sequence while a general response to their enquiry is handled appropriately. It shouldn’t disappear because the automation can’t decide where it belongs.
Track how long records wait for review. An exception queue only protects the campaign if someone clears it. Five important leads left untouched for weeks may deserve more attention than a larger queue your team works through each day.
Preserve history when employment changes
A person changing employer doesn’t rewrite the organisation associated with every past interaction. Keep event-time account associations where the system supports them, alongside the current relationship used for new outreach.
Otherwise, a contact’s move could appear to transfer historical campaign engagement or opportunity influence to the new employer. That would distort reporting without any new campaign activity taking place.
When updating the current account, consider whether ownership, active sequences and suppression need review. A correct identity update can still trigger an incorrect operational action if those dependencies are ignored.
Test the rules against known difficult records
Use a labelled sample that includes clear matches and deliberate edge cases. Include subsidiaries sharing domains, companies with similar names, personal email addresses, recent job changes and regional entities.
Measure both false matches and unresolved valid matches. A system that assigns every record can look complete while producing unacceptable errors. A more cautious system may need a review queue but preserve trust in account reporting.
Review errors by rule. If most false matches come from fuzzy names, adjust that rule rather than weakening the entire process. If correct matches are blocked by missing domain aliases, repair the account reference data.
Check what the match will trigger
Reliable matching enables better buying-group coverage reporting and clearer ABM data management. It also prevents a contact from being routed to the wrong owner or counted against an ineligible target account.
Before launch, agree the account unit, evidence precedence, exception handling and change process. Then review a sample of actual campaign records against those rules. Matching is complete when the association supports a defensible action, not simply when a field is populated.
Talk to ABM Logic about account and persona specifications before a campaign relies on them.
