Unsubscribe Groups (category‑based opt‑out)
Let subscribers choose what types of emails they receive instead of unsubscribing completely.
Create custom preference centers with multiple subscription categories.
Reduce total unsubscribes while respecting user preferences and maintaining compliance.
Log in to comment and vote
Comments1
Marta from Support Team
May 22
1. Webhook event for resubscription
When a recipient clicks "Resubscribe" on the hosted suppression page, the entry is correctly removed (we can confirm via the Suppressions API). However, no webhook event is emitted to notify senders. This is asymmetric with the unsubscribe event, which fires reliably on opt-out. Is a subscription.resumed (or similar) event on the roadmap?
2. Per-recipient substitution in the auto-footer unsubscribe URL
A custom unsubscribe URL can already be configured at account/template level - but the URL is static across all recipients. This means it can't carry per-recipient context (e.g. a signed token identifying which user clicked, or which topic the campaign was about). Would it be possible to support template-variable substitution inside the configured URL - for example, https://example.com/unsubscribe/{{unsub_token}} resolved from template_variables like the rest of the template? The compliance behavior (List-Unsubscribe-Post, one-click) would remain intact.
3. Opt-out of the auto-footer when senders provide compliant headers themselves
When the outbound payload already includes a valid RFC 8058 List-Unsubscribe plus List-Unsubscribe-Post: List-Unsubscribe=One-Click, could the auto-footer be suppressed? This shifts compliance responsibility to the sender, so we recognize it's the highest-friction ask - mentioning it for completeness.