Know the moment users change notification preferences

Courier has introduced preference-change webhooks and a preference history API to help organizations track when users opt in, opt out, or alter notification channels for specific topics. The new `preferences:user:updated` webhook delivers each change from any source, including hosted preference pages, unsubscribe links, in-app settings, and the API, with both current and previous values where available. The `GET /preferences/logs` endpoint provides a paginated, newest-first audit history that can be filtered by user, tenant, or time, and is supported across Courier’s server SDKs, CLI, and MCP server. Courier recommends using webhooks to maintain current CRM or database records and using the history API to recover missed events, while ensuring idempotent processing and signature verification. Preference resets that remove an override do not create events or history entries, so applications must synchronize those changes directly. The features are available now and are intended to improve compliance, customer support, and analysis of notification engagement and opt-out patterns.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.