First-Party CRM Onboarding and Match-Rate Repair for B2B

Expect a match rate between fifteen and thirty per cent when you onboard a business CRM list, not the sixty or seventy per cent a consumer retailer sees. Work addresses at a utility, a mine or a manufacturer rarely appear in the identity graphs the platforms match against. A list of four thousand contacts commonly resolves to somewhere between six hundred and a thousand addressable users, which sits at or below the thousand-member floor Google applies before a Customer Match audience will serve at all. Knowing that before the upload changes what you build. Match rates, honestly: Most of the recoverable loss is in preparation, not in the graph. Hashing has to be SHA-256 over a trimmed, lower-cased address with no other transformation, and a surprising number of exports arrive with trailing whitespace or mixed case that quietly halves the result. Role addresses, shared inboxes and long-departed contacts inflate the denominator and depress the reported rate. Splitting the file by recency before upload usually produces a better audience and a truthful number, because a contact who last engaged four years ago is not addressable in any meaningful sense. The pipe I build: Source of truth in your CRM or warehouse, a defined export contract with the fields and hashing fixed, and a scheduled refresh so the audience does not decay between campaigns. Onboarding through the route that fits your platform: publisher-advertiser identity reconciliation in DV360 where the publisher supports it, hashed email onboarding into Trade Desk's identity framework, or a third-party onboarder where you need the same audience present on several platforms. For account targeting where email match is hopeless, IP-to-organisation resolution is often the stronger path and I will say so rather than force the email route to work. Lawful basis before upload: South African advertisers are working under POPIA, and the direct marketing provisions in section 69 are not the same as the consent language your global template was written for. Before anything is uploaded I want to see where the addresses came from, what the contact was told at the point of collection, and how an objection is recorded and honoured downstream. If that record does not exist, building it is the first phase of the work and I will not shorten it. I will not onboard purchased or appended email files, and I will not onboard a list you cannot trace to its source. This is not a legal opinion and I am not your counsel; it is the line at which I stop. Out of scope: CRM hygiene and deduplication inside your own system, which your operations team does better and cheaper. Consent management platform selection. Campaign strategy; this engagement ends when the audiences are live, sized and refreshing, and the media planning that follows is separate. This is the wrong purchase if: Your customer list is under about two thousand contacts. Below that, matched audiences will not reach servable size on any platform, and the sensible route is account-level targeting from a named list, which costs less and starts sooner. It is also wrong if the data sits in a system nobody will give access to. I have seen this engagement stall for a quarter waiting on a warehouse permission, and the fee is the same whether we are waiting or working. What you receive: A working, refreshing audience pipeline, the match rate documented per segment with the reasons for the shortfall, a written processing basis covering the POPIA position on each source, and suppression audiences built at the same time so existing customers stop absorbing acquisition budget.