Overview
What RudderStack is
RudderStack is a warehouse-first customer data platform (CDP) that collects events and traits from your product and routes them to your tools, through Identify, Track, and Group calls.
Pipe your RudderStack data and events into Courier, then use them to trigger notifications and kick off multi-step journeys, with no send pipeline to build or maintain.
You need a Courier account and a RudderStack workspace with a source already sending events.
Why Courier
What you get with RudderStack + Courier
Map events to notifications, no code
Add Courier as a RudderStack destination and your existing events map to notifications. No consumer or send pipeline to build.
Kick off multi-step journeys
Let a single event start an onboarding, drip, or lifecycle sequence in Courier with delays and branching, all from data you already collect.
Sync traits and profiles
Identify calls keep Courier recipient profiles current with names, emails, and traits, so every send has the data it needs.
Design messages without code
Compose and edit the notification content in Courier's visual editor. Product and marketing change copy without a deploy.
Reach every channel
The same event can send email, SMS, push, chat, and an in-app inbox. Add a channel when you need it, no change to your RudderStack setup.
Localize in seconds
Pick a language and let Courier translate the message with AI, then tweak any string. One template, every market.
How it works
How RudderStack connects to Courier
Courier is a RudderStack destination. In RudderStack's destination catalog you select Courier, connect one or more sources, and add your Courier API Key.
Once connected, Group, Identify, and Track events flow into Courier Studio. To trigger and supply data to a workflow, event properties are scoped under the courier.automation object, so an event can start a notification or a journey.
Use cases
What teams build with it
Setup
Connect it in minutes
Courier is a destination in RudderStack, so there is no pipeline to build. Add it once and your existing events start reaching Courier.
FAQ
Frequently asked questions
Can I use RudderStack with Courier?
Yes. RudderStack, a warehouse-first CDP, connects to Courier as an event destination, so the customer data it collects can trigger notifications. You add Courier as a destination and route your RudderStack sources to it.
How do RudderStack events trigger notifications in Courier?
Track calls forward to Courier and fire Automations, which run the multi-step notification logic. The event's properties become the automation payload, so a signup or usage event can start an onboarding or upgrade flow.
How do I connect RudderStack to Courier?
In RudderStack, search for Courier under destinations, connect the sources you want, and paste your Courier API Key. For the reverse flow, add your RudderStack write key and data plane URL on Courier's RudderStack integration page.
How does a RudderStack Identify call update a Courier profile?
Identify calls create or update a Courier recipient profile. The userId becomes the profile identifier and traits map to profile attributes, so a later notification can address that user by their stored contact details.
How does RudderStack event data map into a Courier notification?
Data flows through the courier.automation object. Properties nested under that scope, for example courier.automation.data, populate the notification payload, so template variables render values sent from RudderStack.
Can Courier send data back to RudderStack?
Yes. The integration is bidirectional. Courier forwards its notification events to RudderStack using a write key and data plane URL, so delivery data can activate downstream in your warehouse and other connected tools.
Is Courier a replacement for RudderStack?
No. RudderStack collects and routes your customer data; Courier turns those events into multi-channel notifications and Journeys across email, SMS, push, and Courier Inbox. They are complementary.
More
