Map consent and suppression states

Inventory unsubscribed, bounced, complained, pending consent, transactional-only and jurisdiction-specific restrictions across CRM, ESP and forms. Record which system is authoritative for each state.

Do not collapse a promotional unsubscribe into a generic inactive flag. Preserve the source, timestamp and scope of consent so a later import cannot silently overwrite a restriction.

Test integration conflicts

Create test records representing common conflicts: unsubscribed in the ESP but subscribed in CRM, duplicate contacts with different emails and a new form submission from a previously suppressed address. Verify which state wins and whether the action is logged.

Ensure promotional automation entry checks suppression at send time, not only when a contact first enters a journey. Distinguish legitimate service messages from marketing content and review local legal requirements.

Monitor and recover

Audit unexpected list growth, reactivations, complaints and failed sync jobs. Build a reversible incident process: pause affected campaigns, identify the synchronization source and preserve evidence of the original status.

After fixing the mapping, rerun the conflict tests and sample real records with access controls. Treat complaint prevention and customer trust as primary outcomes, not merely deliverability optimization.

Implementation worksheet and evidence

Create a versioned working record for email suppression precedence across crm and marketing platforms. Include the affected pages, campaigns or audience segments; a baseline date range; sample identifiers; the decision owner; and evidence another practitioner can reproduce. Mark observations separately from hypotheses so a suspected cause is not mistaken for a confirmed finding.

Prioritize the highest-risk customer journeys first. Capture before-and-after examples and name the person responsible for reviewing exceptions. Where the process touches personal information, use minimum necessary data, restricted access and retention limits rather than copying raw customer records into a shared spreadsheet.

Failure modes and decision rules

Do not make multiple unrelated changes while trying to validate the intervention. Define a stop condition before launch: broken tracking, misleading claims, inaccessible journeys or a meaningful decline in qualified outcomes should trigger investigation. Small samples and delayed outcomes can make short-term percentages unreliable.

Compare the proposed improvement with the simplest alternative, including doing nothing until stronger evidence is available. Document what would falsify the hypothesis and what result would justify expanding the change beyond the pilot. A checklist is a control, not evidence of commercial success.

Reporting and follow-up

Summarize the original problem, the action taken, the test method, the owner and the observed outcome in language a non-specialist can understand. Include absolute volumes alongside rates and note any changes in measurement definitions, attribution or eligibility that limit comparison.

Schedule a follow-up after enough relevant activity has accumulated. Review both intended improvements and unintended effects, then update the operating procedure and related documentation. Keep an explicit record of what remains uncertain so the next review begins with evidence rather than assumptions.