
Thomas Schiavone
July 18, 2026

A notification preference center is where your users decide what they hear from you, on which channels, and how often. Get it right and people mute the one topic that's bugging them instead of unsubscribing from everything. The catch is that building one is a real project, and keeping it branded and responsive across every device is more work still.
We've made it much easier. Courier's redesigned preference tooling lets you build a preference center in a visual editor, preview it before anyone sees it, and give users a page that looks great on web and mobile, with no frontend code.
Configure topics, sections, and branding on the left. Preview the live page on the right, on desktop or mobile.
The Preferences Editor is where you decide what users can control. We rebuilt it to be quicker to work in, with a live preview so you see exactly what users will get before you publish. The whole page is yours to shape:
Your changes save as a draft and never reach users until you publish. Hit Preview Page to see the preference center exactly as a user will, marked with a "Draft mode" banner, then Publish when it's right. No more guessing what an edit will look like, and no more pushing changes straight to live users.
Courier hosts this page for you, so there's nothing to build, deploy, or maintain.
The hosted preference center, matched to your brand. Users toggle topics on or off and pick a digest schedule, like daily or weekly.
The page picks up your brand automatically. Your logo, colors, and typography carry over, so it looks like part of your product instead of a bolt-on, and it follows along when you change your brand.
It's responsive, so it looks right on everything from a laptop to a phone without you touching any CSS. And one-click unsubscribe is built in, so you stay compliant without building opt-out flows yourself.
Many teams start with the hosted page to launch in an afternoon, then build a fully custom experience once they know exactly what they want. You can embed the same preferences directly in your own product, with prebuilt components for web (React, web components) and mobile (iOS, Android, React Native, Flutter), and take full control of the layout and styling.
It's the same preference data underneath, so moving from hosted to embedded is a step forward, not a rebuild.
New bulk API endpoints update all of a user's preferences in a single request. Importing your existing subscription and opt-out data from another system becomes one call per user, instead of setting topics one at a time. Replace a user's entire set at once, or update only the topics you name.
Open the Preferences Editor to set up your topics, or read the preferences overview to see how it all fits together.
A page where your users manage which notifications they receive from your product, on which channels, and how often. It usually covers subscription topics they can opt in or out of, channel choices, digest frequency, and one-click unsubscribe.
No. You configure and brand the whole page in the visual Preferences Editor and link to the hosted version, with no frontend code. Developers can step in later to embed a custom version or manage preferences over the API.
A hosted preference center is a page Courier hosts and you link to, with no frontend code. Embedded preferences render inside your own web or mobile app with prebuilt components, for full control over layout and styling. Both read and write the same preference data, so you can start hosted and move to embedded later without a rebuild.
Yes. Turn on digests for a topic and users pick a schedule, like instant, daily, or weekly, so a busy topic arrives as one summary instead of a stream of messages.
Every subscription topic includes one-click unsubscribe, and you can add an unsubscribe link to any notification. Because users opt out of a single topic rather than all of your messages, you keep more of them subscribed overall.
Yes. The hosted page uses your brand automatically for its logo, colors, and typography, and it's responsive on web and mobile out of the box.
Use the bulk API to set all of a user's preferences in one request. You can import your existing subscription and opt-out data one user at a time, without rebuilding it topic by topic.

Experiments: A/B test your messages inside Journeys
Experiments bring A/B testing into Journeys. On any send node, run 2 to 10 message variants, split traffic by weight, and Courier buckets each recipient deterministically, keeping them in the same variant across sends. Compare sent, delivered, open, and click rates per variant, then promote the one you want, without leaving your journey or bolting on a separate testing tool.

AI Translation: localize any template in seconds
Courier AI Translation brings built-in localization to Design Studio. Add a language to any template and AI translates every string in seconds. Works across email, SMS, push, in-app, and chat. Review side by side, override anything, and publish from the same editor you already use.

Inbox SDKs for Vue and Angular: a native in-app notification center
Courier now ships first-class inbox SDKs for Angular and Vue. Drop in a real-time notification center, toasts, and a preferences center with native components, an injectable service, and a composable, all backed by the same in-app inbox that already powers React and JavaScript apps.
© 2026 Courier. All rights reserved.