Email Preference Center Examples for Topics, Cadence, and Channels
A preference center is a consent and routing surface, not a maze designed to save every subscriber. It should let people choose the relationship they want: topics, cadence, channel, or no optional messages.
What to show
| Control | Example |
|---|---|
| Topics | Product updates, education, offers, events |
| Cadence | Immediate, weekly, monthly, pause |
| Channel | Email, SMS, push when separately consented |
| Account status | Which address or workspace is being changed |
| Unsubscribe | Stop the selected category or all optional mail |
Show the current state, not a default state. A successful save should confirm exactly what changed.
Example page copy
Choose the updates you want from {{company_name}}
Email address: {{email_address}}
Topics
- Product and feature updates
- Education and guides
- Offers and recommendations
- Events and research
Frequency
- As available
- Weekly summary
- Monthly summary
- Pause for 30 days
[Save preferences] [Unsubscribe from all optional email]
You will continue to receive account, security, and transaction messages needed to provide the service.
Design and data rules
- Use a signed or authenticated preference URL.
- Do not require a password reset just to unsubscribe from optional email.
- Apply changes immediately and show a confirmation.
- Preserve consent history, source, timestamp, and category.
- Keep required service messages separate from optional marketing.
- Make the all-unsubscribe action visible.
If an old category no longer exists, map it to a documented replacement rather than silently re-subscribing the person.
QA checklist
- Every checkbox maps to a real send rule.
- Unchecking a topic suppresses future sends and dynamic blocks.
- Frequency changes affect scheduled jobs.
- Unsubscribe works without extra navigation.
- The page is accessible by keyboard and screen reader.
- Confirmation states are clear on mobile.
For frequency-specific controls, see email frequency options.
Organize controls around real subscriptions
Start from the categories the sending system can enforce. If there is no separate rule for “research,” do not expose it as a checkbox. A small, accurate preference center is better than a detailed form that is ignored by the campaign query.
Use a hierarchy when categories overlap:
| Level | Example | Effect |
|---|---|---|
| Global optional | All marketing | Stops every optional category |
| Topic | Product news | Stops product-news campaigns and blocks |
| Cadence | Weekly digest | Changes timing for eligible topics |
| Channel | Email or SMS | Requires separate channel consent |
| Service | Receipt or security | Governed by account and legal need |
Explain inheritance. If someone turns off global optional email, topic toggles should not appear to re-enable it. If a topic is paused, show when it resumes.
Use a stable preference record
Store subscriber, workspace or brand, category, state, source, timestamp, effective timestamp, and preference schema version. Treat an email link as a scoped authorization, not as a public form that can change another address. Expire or rotate signed links according to the risk of the action.
When categories are renamed, map old values explicitly and preserve the original consent history. Never migrate an old unsubscribe into a new opt-in because the labels changed.
Confirmation should be specific
After save, show “Product updates: off; education: weekly; offers: unchanged” rather than “Preferences saved.” Provide a link back to the center and a clearly visible all-unsubscribe option. For mobile, keep the save and unsubscribe actions separated enough to prevent an accidental tap.
Test keyboard navigation, screen-reader labels, localized dates, expired links, duplicate submissions, and a preference change immediately before a queued send. Monitor the percentage of sends suppressed correctly; it is a better reliability signal than page completion alone.