Skip to main content
Each template has a settings panel where you configure its identity, behavior, and publishing. To open it, click the gear icon next to the publish button in the designer.

​
General

General Settings

​
Notification ID

Every template gets a unique Notification ID assigned by Courier. You can use this ID in the template field of your Send API request, or map a human-readable event alias instead (see Event Mapping below).

​
Brand Config

Brands are enabled by default, so every new email template uses your Default Brand. You can disable branding per template or assign a Custom Brand.

​
Subscription Topic

Assign a subscription topic to group templates under a single preference. This lets end users opt in or out of a category of notifications at once rather than one template at a time.

​
Message Tags

Message tags are behind a feature flag. Contact Courier Support or your account team to enable them.
Add a comma-separated list of tags to a template. These tags are automatically included in metadata.tags on every message sent from that template, so you can filter by tag in an Inbox view or query them through the Messages API.
Message Tags in Template Settings

​
Event Mapping

Map an event name to a template so you can reference it by a readable alias instead of the Notification ID. This decouples your code from specific template IDs; you can swap the underlying template without redeploying your application.
Event Mapping Settings
Once mapped, use the event name in the template field of your send request: 
{
  "message": {
    "template": "order-confirmation",
    "to": { "user_id": "user_123" },
    "data": {
      "order_id": "ORD-12345"
    }
  }
}

​
Conditions

Use conditions to prevent a template from sending when specific criteria are met. You can reference properties from the data or profile objects provided in the Send API call or User Profile. See Send Conditions for details.

​
Notes

Notes let you attach internal context to a template. Once added, a note icon appears in the template list; clicking it opens a read-only preview without entering the designer.
Template Notes

​
Publishing & Versioning

Templates follow a publish workflow so you can iterate safely before going live:
  • Draft: Save changes without affecting live notifications
  • Publish: Make changes active for all new sends
  • Rollback: Revert to any previously published version
For API-based templates using Elemental, publishing is handled through your deployment process; new versions become active when you deploy updated code. You can view the full publish history to see who published each version and when.
Rolling back overwrites any unpublished draft changes.
Publish History