Tools and providers
Part of Customer data platform for B2B companies: what UK teams should check
Customer data platform for B2B companies: what UK teams should check
A customer data platform for B2B UK teams has to resolve accounts, not just contacts. What to map, what to ask vendors and where lead to account matching fails.
What to take away
- A customer data platform for B2B UK work must resolve accounts as well as people, since buying decisions involve several contacts.
- Companies House, the CRM and product usage are the usual starting sources; LinkedIn data arrives through a licensed route rather than a scrape.
- Lead to account matching decides whether a CDP supports account based marketing or just produces a longer contact list.
- Map fields and agree suppression rules before any pilot, not after the contract is signed.
B2B data starts in fewer places than consumer work
Most CDP writing assumes millions of consumers and a web tag. A B2B estate is narrower: a CRM, a marketing automation tool, a support desk and a billing system. Firmographics arrive from a licensed provider or from public filings. Product usage may sit in a separate application database.
A UK business with a few thousand target accounts has a smaller row count than most consumer estates, but messier joins. The ONS digital economy collection publishes UK figures on business technology use, which is a useful starting point for sector context.
Companies House is the nearest thing to a public identity spine for UK limited companies. Company number, registered name and registered office give an anchor that a job title never will. It does not cover partnerships, sole traders or overseas parents, so plan for the gaps.
Build a source-to-field map before any demo
A tour of the product will not tell you whether the platform fits. A source-to-field map will. List every system that holds an account or contact record, then name the fields you need.
B2B data sources and gaps
Source
- CRM
- Account, contacts, deal stage
- Marketing automation
- Email engagement, form fills
- Product usage
- Feature use, seats, sign-ins
- Companies House
- Company number, registered name
- Third-party data
- Sector codes, employee band
- Billing or finance
- Contract value, renewal dates
Typical fields
- CRM
- Duplicates, stale titles
- Marketing automation
- Contact level only
- Product usage
- Rarely tied to hierarchy
- Companies House
- No contacts, limited names
- Third-party data
- Accuracy varies
- Billing or finance
- Closed to marketing
Known gaps
- CRM
- Marketing automation
- Product usage
- Companies House
- Third-party data
- Billing or finance
Source-to-field map
| Source | Typical B2B fields | Known gaps |
|---|---|---|
| CRM | Account name, contacts, owner, deal stage, activity | Duplicate accounts, stale job titles |
| Marketing automation | Email engagement, form fills, campaign membership | Contact level only, thin firmographics |
| Product or service usage | Feature use, seats, sign-in frequency | Rarely tied to an account hierarchy |
| Companies House | Company number, registered name, incorporation date | No contacts, limited trading names |
| Licensed third-party data | Sector codes, employee band, turnover estimate | Accuracy varies by segment and refresh date |
| Billing or finance | Contract value, invoices, renewal dates | Closed to marketing without a lawful route |
The map shows which fields are missing and forces a conversation about ownership. If finance owns billing data and marketing owns the CRM, both teams belong in the room. Cut any field with no source and no owner from the first phase.
Lead to account matching is the hard part
Identity resolution in B2B runs in two directions. A contact resolves to a person, then to a company, and often to a parent group. Get that order wrong and an account based marketing programme treats one buying committee as four strangers.
Lead to account matching order
- Contact resolves to a person
- Person resolves to a company
- Company resolves to parent group
- Apply deterministic rules first
- Add probabilistic for shared domains
- Label every match with confidence
Matching rules are usually deterministic first: company number, then email domain where the domain is not a free provider, then exact registered name. Probabilistic matching helps with shared domains, such as agency or group addresses. Every match needs a confidence label a person can review.
Confidence scoring is covered in how identity resolution works in UK CDPs. Matching contacts to accounts means processing personal data, so the lawful basis must be settled early; the ICO's UK GDPR guidance and resources hub sets out the tests.
Account based marketing needs account-level controls
PECR and UK GDPR apply to B2B outreach, even when the address looks corporate. Sole traders and some partnerships count as individuals. The ICO's direct marketing guidance covers consent, legitimate interests and the soft opt-in.
Suppression at two levels
Does the contact object?
suppress contact only
check account-level opt-out
Suppression has to work at two levels. If a contact objects, that does not always mean the account objects, and the reverse is also true. A platform that can only suppress one email address will struggle in an audit.
Ask how the system handles a company-wide opt-out, a group structure and a rebrand. Then ask what happens when two accounts merge.
Questions to put to a vendor before a pilot
Questions to put to a vendor
- Can one account hold several contacts, sites and a parent group without duplicating the account?
- Which fields drive lead to account matching, and what confidence score does a reviewer see?
- How does a source field map to a destination field, and who approves changes?
- Does suppression work at contact, domain and account level?
- What leaves the platform at contract end, and in what format?
- Which references run a comparable UK account structure?
Clean the source records before the pilot starts, and tie every B2B CDP use case to a named owner. The checks worth running first are set out in cleaning account data before implementation, and duplicates are cheaper to fix in the CRM than inside a new platform.
Common questions
Do B2B companies need a customer data platform, or is a CRM enough?
A CRM holds the sales relationship. A CDP joins it to engagement, product and third-party data, so teams outside sales see the same account view.
Can we load bought contact data straight into the platform?
Only with a lawful basis and an accuracy check. Bought contact data ages quickly, and the ICO expects you to explain the source of each record.
How should LinkedIn data enter a B2B CDP?
Through a licensed integration or a manual export, because scraping breaches its terms. Treat exports as personal data, with the same retention duties as a CRM record.
