How do customer and CRM lists work for B2B on Meta?
Short answer
Upload lists from your CRM as customer list custom audiences: customers, qualified leads, disqualified leads and employees. Meta matches hashed identifiers such as email addresses and phone numbers to its users, so personal contact details match better than generic work addresses. Use the lists as lookalike seeds and exclusions, and upload only data you have permission to use.
Meta accepts identifiers including email addresses, phone numbers, names, dates of birth, gender, locations and some app and device IDs. Data must be hashed with SHA256, and Meta says providing several identifiers for each record increases the match rate (Meta for Developers). Ads Manager does the hashing for you when you upload a file.
Why B2B lists match poorly
A CRM full of work addresses, such as j.mehta@company.com or procurement@company.com, holds details most people never used to sign up for Facebook or Instagram. Shared inboxes match nobody. Mobile numbers and personal email addresses, where you collected them lawfully, match far more often. Before blaming the audience, check how many of each list’s records carry a phone number.
Refresh and consent
- Refresh on a schedule. A qualified-lead list uploaded once in March is wrong by June: some leads became customers, others were disqualified. Monthly is a sensible default for lead lists.
- Check permission before uploading. Meta’s Custom Audience terms ask advertisers to confirm they have the permissions needed to use the data under applicable law. Whether your form consent covers uploading contacts to an ad platform depends on the market; see lead generation compliance.