Database marketing means using what you know about your customers and prospects to send each of them something relevant, instead of the same message to everyone. In B2B, the database is usually your CRM and marketing automation platform, and the “marketing” is everything from a nurture sequence to a renewal reminder to the list sales works from on Monday morning.

We first wrote about this in 2023. The basics have held up, but two things have changed: mailbox providers now enforce sending rules, and AI tools make it cheap to send more email, which makes a clean, consented list worth more than ever. This is the current version.

Start with data you are allowed to use

The best database is built from first-party data: information people give you directly or that comes from their own dealings with you, such as form fills, event registrations, purchases, support conversations, and product usage. It is more accurate than a purchased list, and you know where it came from.

  • Record consent and source on every contact. Store how and when each person joined, and what they agreed to. You will need it to answer an opt-out, a data request, or a deliverability problem.
  • Know the rules for the places you sell into. In the U.S., CAN-SPAM allows commercial email without prior consent but requires a working opt-out, honored within 10 business days, and a physical postal address. Canada’s CASL and the GDPR in Europe generally require consent first.
  • Be careful with bought and scraped lists. They bring unknown consent, high bounce rates, and spam complaints, which damage the reputation of the domain you send from.

Google has kept third-party cookies in Chrome after years of planning to remove them, but that does not make first-party data less important. Safari and Firefox block third-party cookies by default, consent rules still apply, and your own data is the only kind your competitors cannot buy.

Keep it clean, or it stops working

Contact data decays constantly. People change jobs, companies rename and merge, and every import, form, and integration adds near-duplicates. A database that is not maintained slowly turns into wasted sends, wrong personalization, and sales reps calling people who left a year ago.

  • Validate at the door. Check email syntax and domains on forms, require the fields you will actually segment on, and use picklists instead of free text for things like industry and country.
  • Find and merge duplicates. “Robert Johnson” and “Bob Johnson” at the same company may be one person; two companies sharing an email domain may be separate. Rules catch the easy cases; the hard ones need judgment. Our CRM duplicate reconciliation agent scores likely matches and explains them, and a person approves every merge.
  • Suppress what no longer works. Remove hard bounces immediately, and stop mailing contacts who have not opened or clicked in a long time before they hurt your sender reputation.
  • Assign an owner. Someone has to be responsible for data quality, with a short monthly review of new duplicates, missing fields, and bounce rates.

Segment on what changes the message

A segment is only useful if the people in it should get a different message. In B2B, the segments that tend to matter are:

  • Fit: industry, company size, region, and role, which decide which problems and proof points are relevant.
  • Stage: subscriber, lead, opportunity, customer, or former customer, which decides what to ask for.
  • Engagement: recent visits, downloads, replies, and event attendance, which show current interest. These signals feed lead scoring.
  • Account: several people at one company may be in the buying group, so look at engagement across the account, not only by contact.

Start with a handful of segments you can actually write for. Twenty segments with the same email in each are just extra work.

Send on triggers, not only on a calendar

Scheduled newsletters have their place, but the messages that perform best are usually triggered by something the person did or something that changed.

  • a welcome series after someone subscribes or downloads a guide;
  • a follow-up when a known contact returns to pricing or service pages;
  • an onboarding sequence when a deal closes, and a check-in before renewal;
  • a re-engagement message when a customer goes quiet.

Each of these is a nurture workflow in your marketing automation platform. Keep personalization to what you actually know and what helps: the right industry example beats a first name in the subject line. Our guide to marketing automation best practices for B2B covers building these workflows in more depth.

Meet the sending rules

Since February 2024, Gmail and Yahoo have required senders of more than about 5,000 messages a day to authenticate their mail with SPF, DKIM, and DMARC, offer one-click unsubscribe, honor unsubscribes within two days, and keep spam complaints low; Google names 0.3% as the rate to stay under. Microsoft began enforcing similar authentication rules for high-volume senders to Outlook.com, Hotmail, and Live addresses in May 2025.

Even if you send far less than that, follow the same rules. Authentication protects your domain from being spoofed, and the same filters judge small senders on the same signals. We cover SPF, DKIM, and DMARC in our website security guide.

Measure what the database earns

Opens are no longer a reliable measure; Apple Mail Privacy Protection preloads images and inflates them. Measure further down the funnel instead:

  • clicks, replies, and form submissions by segment;
  • meetings and pipeline influenced by campaigns, and revenue from existing customers;
  • list health: growth, bounce rate, complaint rate, and the share of records with the fields you segment on;
  • unsubscribes per campaign, which tell you when a message missed its audience.

Test one variable at a time, such as the offer, the subject line, or the timing, and give each test enough recipients to mean something.

Where we come in

We set up and clean up CRMs and marketing automation: consent and source tracking, deduplication, segments, triggered workflows, sender authentication, and the reports that tie them to pipeline. If your database has grown faster than anyone could maintain it, tell us what you are working with.