The B2B identity problem nobody talks about honestly
Consumer CDP architecture assumes a relatively stable, person-centric identity model: one person, a handful of identifiers, a reasonably clean graph. In B2B, especially in manufacturing, this assumption fails almost immediately.
A procurement lead at a mid-size industrial company might appear in your systems as: a named contact in Salesforce under their corporate email; an anonymous session in your web analytics, tracked by a shared corporate IP address; a delegate at your annual user conference registered under a different division; a contact in your partner portal under a subsidiary name; and the contract holder on four service agreements for plants in three different regions.
Run a standard person-centric identity resolution algorithm over this and one of two things happens. Either these records get merged into a single profile that is technically unified but practically unusable, because it now carries signals from contexts that should have remained separate. Or they stay fragmented, and the “unified” view you promised the board does not exist at all.
We have seen production environments where aggressive identity stitching produced profiles with hundreds of associated email addresses. That kind of over-stitching does as much damage as never resolving identity at all, because it actively misleads the people making decisions from it.
The installed base: the most valuable data you probably are not activating
Here is a number worth sitting with: 62% of manufacturers report lacking full integration between their IoT and operational systems and their enterprise data platforms.
That gap matters enormously, because the data that lives in those operational systems (equipment telemetry, firmware versions, service histories, warranty status, usage rates) is the primary commercial signal, not supplementary context.
A customer who has three machines approaching end-of-warranty and a declining maintenance score is a retention risk and a commercial opportunity simultaneously. A high-tech customer whose product adoption has dropped 40% in the last quarter is a churn signal weeks before any human in customer success notices it in their dashboard.
None of this intelligence lives in a web session log. It lives in the ERP, the IoT platform, and the field service system. And it is almost never in the CDP, not because it cannot be connected, but because the connection has not been prioritized, and in many cases the right architectural approach for connecting it (without replicating millions of records into a marketing data store with looser controls) has not been obvious.
The distributor blind spot
Most industrial manufacturers do not sell to end users. They sell through distributors, resellers, and channel partners who hold the customer relationship, the transaction data, and often the installation records. In many cases, 60 to 80 percent of actual revenue flows through these intermediaries.
A CDP that can only see direct digital interactions, your website, your email campaigns, your events, is systematically blind to the channel that carries most of the revenue, so it mis-scores account health, mistimes outreach, and personalizes based on a relationship it doesn't actually understand.
This is not a gap that can be closed by adding another connector. It requires a fundamentally different approach to how partner data is incorporated, one that the channel partner will accept, which means it cannot require them to hand over raw customer records.
