Map every way an address enters the system
List website forms, event registrations, checkout, CRM imports, manual uploads and partner integrations. For each source record the stated purpose, consent language, timestamp, jurisdiction and evidence available to demonstrate permission where required. An address in the CRM is not automatically eligible for every campaign.
Distinguish promotional messages from genuinely transactional communication by primary purpose. A receipt and a newsletter can use the same provider but require different classifications and controls. Check the transactional-versus-marketing guide before changing global suppression rules.
Test unsubscribe like a real recipient
Send a test campaign to a controlled address, use the public unsubscribe path without admin access and confirm that marketing sends stop across relevant lists and sequences. Verify the confirmation is clear and that the platform records the action.
Test mobile unsubscribe, an older email, repeated clicks, a preference change followed by global opt-out, and a later CRM reimport. A synchronization rule must not silently restore marketing eligibility after someone unsubscribes.
Understand the legal differences
The U.S. FTC's CAN-SPAM guidance requires a clear opt-out method and honoring requests within 10 business days for covered commercial email. Canada's anti-spam rules also require functioning unsubscribe mechanisms for commercial electronic messages and generally processing requests without delay, no later than 10 business days. Consent requirements and exceptions differ by jurisdiction.
Treat legal deadlines as outer limits, not target response times. Apply suppression promptly and seek qualified advice for complex cross-border questions. Do not assume that U.S. opt-out rules replace Canadian consent requirements or that outsourcing email transfers away sender responsibility.
Preserve a durable suppression state
Choose an authoritative global suppression field respected by newsletters, nurture flows, reactivation and manual exports. Keep enough information to honor the request without unnecessary personal data. Decide how deletion requests interact with minimal suppression records so a later import cannot recreate unwanted subscriptions.
Document which system wins during conflicting updates. Test an integration that sends 'subscribed' after an unsubscribe event. If the integration can override the subscriber's choice, fix the mapping before the next campaign.
Check preferences and automation exits
A preference center may offer topics and frequency choices, but global marketing opt-out should remain easy to find. Verify that preference changes affect actual audience selection rather than merely updating a cosmetic profile field. Test queued automations after a subscriber opts out.
Check timing races: a campaign export may be created before suppression updates, or a welcome sequence may already be queued. Define how the platform handles scheduled sends and how staff should validate suppression before manual uploads.
Review sender identity and authentication
Audit the visible From and Reply-To details, domain authentication and SPF, DKIM and DMARC settings. Authentication is not consent, but broken configuration can damage deliverability and trust. Verify footer identification and physical address requirements where applicable.
Make unsubscribe and preference pages accessible and usable without a password. An obscure opt-out hidden behind account navigation is not an acceptable customer experience. Confirm the links still work after template and provider migrations.
Example and monthly QA checklist
A business imports a seasonal CRM list, and an incorrect mapping changes previously unsubscribed contacts back to subscribed. The root cause is data ownership, not a missing footer link. Pause the risky send, correct the import, reconcile affected records and retest using controlled addresses.
Each month, test consent capture, preference updates, global opt-out, automation exits, CRM synchronization, reimports, authentication and sender details. Track suppression delay, failed preference changes, complaints and accidental resubscriptions. Pair this audit with the preference-center, deliverability and automation-trigger guides.