Consent management: the email nine days later

A prospect unsubscribes from a marketing email on a Monday, and the marketing platform records it straight away. The CRM syncs with marketing overnight, and the sales engagement tool syncs with the CRM once a week. Neither sync carries the opt-out field.

Nine days later, a sales sequence sends the prospect three emails in a week. They reply asking to be removed, and copy in their data protection officer.

Consent and preferences are the part of compliance automation that marketing and sales teams touch every day. A withdrawal only counts once every tool has heard about it.

What is consent management?

Consent management records what each person has agreed to, and makes every system that contacts them respect it. One system holds the record. A change, above all a withdrawal, reaches every tool that sends email, calls or ads within seconds, with a log of when each one updated.

Why opt-outs don’t reach every tool

1. Each tool keeps its own record. Marketing, sales engagement, the CRM and the ad platforms each store opt-outs separately.
2. Syncs run on a schedule. Overnight or weekly syncs leave days when the tools disagree.
3. The field isn’t mapped. A sync copies names and companies and leaves the consent field behind.
4. New tools start empty. A newly connected tool gets contacts without their preferences.
5. Nobody can prove when it changed. Without a log, there’s no record that a withdrawal was honored in time.

What it costs

Contacting someone who has withdrawn consent can breach privacy rules, and it damages trust either way. Complaints reach the data protection officer instead of the marketing team. Without a log, the company can’t show that it acted on the request.

What to fix first

1. Pick one system to hold consent. Every other tool reads from it.
2. Send withdrawals as they happen. Push each change to every tool in seconds, not in the next batch.
3. Map the consent field in every sync. Check that each integration carries it, including new ones.
4. Check consent at send time. A sequence or campaign checks it before each send, as well as at enrollment.
5. Log every update. Record when each tool received the change, as evidence.

The guide to building a consent and preference sync has the prompts for each step.

Where it fits

Consent travels with the rest of the contact record, covered in CRM and marketing automation sync. A request to delete someone’s data goes further than an opt-out, and that’s the job of the DSAR process.

For every part of compliance automation, from policy to audit evidence, see continuous compliance.