Resources · 83
Email marketing: preferences and unsubscribe choices that take effect
Connect links, headers, CRM records and sending queues so preference changes reach every campaign.
· 3 min
What this guide helps achieve
- Map message purposes
- Make choices usable
- Separate visible links from the protocol
- Propagate suppression to sending
- Test edge cases
Quick check
- Can an import reactivate a subscriber?
- Can a lower frequency be offered?
- Must every trace of an opt-out be deleted?
Step-by-step method
- 01
Map message purposes
Inventory newsletters, follow-ups, offers and messages needed to deliver a service. Identify purposes and systems holding subscriptions. CNIL guidance distinguishes prospecting situations and applicable conditions; a display preference is not evidence of consent. Retain appropriate evidence for the situation being handled.
Deliverable: lists, purposes and ownership map.
- 02
Make choices usable
Present frequency, topics and stopping commercial communications separately. Preference options must not prevent unsubscribe. Test expired links, changed addresses, mobile and keyboard access. Confirm the choice without requiring account sign-in for the unsubscribe journey.
Deliverable: choice journey and failure cases.
- 03
Separate visible links from the protocol
The body link and headers processed by the email client are different mechanisms. RFC 8058 uses List-Unsubscribe with an HTTPS URL, List-Unsubscribe-Post and a POST request; the relevant headers must be covered by a valid DKIM signature. An automated GET must not perform this one-click unsubscribe.
Deliverable: raw message and request tests.
- 04
Propagate suppression to sending
Apply the choice to CRM records, segments, connectors and imported lists. Check status immediately before sending, including queued campaigns. Retain only information needed to prevent renewed solicitation, with defined retention and access. Re-importing a list must not cancel an opt-out.
Deliverable: suppression check and import replay.
- 05
Test edge cases
Test repeated requests, list changes and connector outages. Check messages needed for an order separately: adding promotional material can change their nature. If propagation fails, block affected commercial sends and notify the owner.
Deliverable: end-to-end scenario and enforcement evidence.
Reusable worksheet
Complete with your authorised observations. These fields are a working template, not observed results.
| Field | Information to record |
|---|---|
| Choice | Purpose, list, requested state and time |
| Propagation | Receiving systems and confirmations |
| Message | Visible link, headers, DKIM and GET/POST behavior |
| Sending | Final status check and queued campaign handling |
Worked example
Illustrative situation
Fictional example: a person unsubscribes after a newsletter is prepared but before it is sent.
Decision and expected evidence
The sending engine checks suppression at send time and excludes the address despite its presence in the prepared segment.
Distinguish the mechanisms
| Mechanism | Purpose | Check or limitation |
|---|---|---|
| Preferences | Choose topics or frequency | Do not replace complete unsubscribe |
| Message link | Offer a visible route to choices | Test redirects, expiry and keyboard access |
| One-click headers | Enable an email-client action | Verify HTTPS POST and DKIM coverage |
Management indicators
| Indicator | What it measures | First action |
|---|---|---|
| Propagation | Delay between request and enforcement across tools | Address delayed connectors |
| Post-opt-out sends | Commercial messages sent despite applicable suppression | Pause and investigate |
| Usable journey | Unsubscribe achievable on mobile and with keyboard | Remove barriers |
Common pitfalls
- Do not replace complete unsubscribe
- Test redirects, expiry and keyboard access
- Verify HTTPS POST and DKIM coverage
Frequently asked questions
Can an import reactivate a subscriber?
Suppression should prevent automatic reactivation. Treat a new subscription according to its context and evidence, not mere presence in a CSV.
Can a lower frequency be offered?
Yes, as a separate choice. Refusing all commercial communications must remain accessible and effective.
Must every trace of an opt-out be deleted?
A limited record may be needed to honor it. Define necessary information, access and retention instead of keeping the entire profile.
Official references
References consulted: . The method and worksheet propose checks to adapt to your context; they do not constitute certification.
Continue exploring
Related analysis
