Trying to understand something that's not defined here? Ask us in a message — and we can add it to the list. 😄


Brands is a Courier feature set that lets you apply a consistent look and feel to your email notifications. You can also use this feature to "white-label" email notifications you send on behalf of your customers to their end-user recipients or if you have multiple brands internally. Courier Brands are also fully API enabled. Developers can get, create, update and delete brands programmatically using our Brands API.

Keep reading: Brands


Courier allows you to build notifications for four different notification types or Channels: email, SMS, push notification and direct message. In order to send notifications via a channel, you must add one or more integrations. You can prioritize the send order of the channels and set conditions to disable them.

Keep reading: Channels and Integrations.

Channel Rules

Courier's channel rules allow you to prioritize which Integrations are used to send your Notifications. Selected Integrations are arranged in a top-to-bottom hierarchy. The Notification sends via the highest-ranked Integration for which the user has contact information listed. For example, a Notification could utilize Slack and email, in that order. If the recipient has a Slack account in their Courier recipient profile, the Notification will send via Slack only. If they have no Slack account listed, but do have an email address listed, it will send via email.

Keep reading: Channel rules

Content Blocks

Content blocks are pieces of content that you add to your notification in Couriers drag and drop LINK <Notification Designer>. Content blocks are responsive and reusable across channels.

Keep reading: Content Block basics.

Channel Conditions

The "Conditions" tab in Channel Settings (the gear that expands on the sidebar when you hover over a channel in the template editor) lets you apply conditionals to decide which channel the notification is routed to, and even which integration.

Direct Message

A direct message (DM) is a private form of communication between you and your users that is only visible to the sender and recipient(s). Direct messaging apps are increasingly the preferred communication channel for most users. Courier integrates with a number of popular Direct Message providers.


An event is a unique identifier that can be mapped to an individual Notification. This could be the "Notification ID," or a custom string mapped to the event in the Event Maps settings. These events can be defined by you, i.e. new-user or by an incoming integration, i.e., Segment.

You can manage your Event Maps via the Events API.


Handlebars is a simple email templating language that generates HTML. The Courier Notification Designer lets you insert Template Blocks that use Handlebars or switch to the Handlebars editor and build your entire template in HTML.

Keep reading: Working with Template Blocks.


Integrations are the service providers you connect to Courier so that it can send your notifications. Rather than replacing your existing providers, Courier passes your Notifications to the providers you already use via these channel integrations. This allows you to create and manage notification content across multiple service providers in one place.

See a list of all available Integrations here.


Notifications are the messages you build in Courier and send through channels via the delivery systems you integrate with Courier. Each notification has a unique identifier known as the Event ID (you can find this id in the notification settings)

More specifically, a Notification is a template for a type of message that can be sent more than once. For example, you might create an "Appointment Reminder" Notification or "Reset Password" Notifications. Notifications can contain variables, (e.g. {name} or {apt_time}) so that the same Notification can be sent to many people.

Keep reading: What is Courier?

Notification Design Studio

Courier's Notification Design Studio empowers every team member to build beautiful, multi-channel notifications with and easy to use graphic user interface. Its drag & drop interface lets you build branded notification content without writing code that consistently renders across every email client and reusable in any channel.

Keep reading: the Notification Design Studio.


Overrides can be used to change the request body that Courier sends to a provider. Overrides are useful when a field is not yet supported by Courier, or you would like to override the value that Courier generates. Here's an Override example using SendGrid.


A profile is a JSON object that includes any key-value pairs required by our Integrations. You can find the required keys for any Integration on its "Integrations" page. See the "Integration Introduction" for details. The Profiles API allows you to create and manage the profile information associated with an individual recipient.

Push Notification

A push notification is a message or alert that is sent to users who have installed your client app on their device and enabled notifications in their settings. Push notifications are powerful because your users do not have to have the app open to receive the message. Courier integrates with multiple push notification providers.

Transactional (relationship) emails

Many courier customers use us to build transactional email notification templates. Although Courier does not actually send emails (that's done by the email service providers you integrate with Courier) you can add unsubscribe links to your Courier email templates. Understanding when an email notification is transactional or relationship is important and the CAN-SPAM act's definition is a good place to start.


White labeling is when you remove your brand and logo from notifications and instead use branding defined by your customer. In other words, white-label email notifications are sent by you on behalf of your customers to their end-users. This means end-users receiving email notifications you send see your customers' branding on the email.

Read more: White-labeling

Did this answer your question?