Courier
This page describes how to use Census with Courier.
Last updated
Was this helpful?
This page describes how to use Census with Courier.
Last updated
Was this helpful?
In this guide, we will show you how to connect Courier to Census and create your first sync.
Have your Courier account ready.
Have your Census account ready. If you need one, now.
Have the proper credentials to access to your data source. See our for more information.
Census only needs an API key for Courier to get started.
To access your API keys, visit the Settings by clicking the ⚙ icon in the top right and choosing API Keys from the menu. Depending on your Courier plan, you can generate a new key or reuse the existing keys provided to you. If generating new keys, you can optionally choose which Courier environment or routing you want to use for your key if you'd like to test the integrations first before sending notifications. See to understand the ins-and-outs for your API configuration.
Now that we have your API Key from Courier, we can set up Courier as a Destination Connection.
Inside Census, click on Destinations in the left navigation, click New Destination and then find Courier in the menu.
You can provide whatever name you like. This is helpful if you're using a test environment to start and want to label your connection to indicate that.
Copy in your API Key from Courier
Save
Courier is a service that lets you design, send, and manage notifications to your users across many different channels including email, SMS, push, in-app, chat, and more.
Using Census, you can sync your user data and give Courier super powers. For example:
Sync user profile attributes to the Courier profile to personalize notifications based on your users' up-to-the-minute activities.
With live data and programmatic notifications, the possibilities are endless. Let us know what you come up using Census and Courier together!
Profiles
✅
Recipient ID
Profile with List
✅
Recipient ID
Like Courier, we use the recipient_id as the primary identifier for Profiles. A recipient_id is a unique identifier for a recipient. This can be any string of your choosing. Be sure to choose a value that does not change. This prevents duplicate entries in the event that a recipient changes their email or some other identifying value. Typically, user ID values from your system make for good recipient_id's.
Behaviors
Supported?
Objects
Update or Create
✅
All
Mirror
✅
Profile with List
And that's it! If this is your very first sync with Census, jump back to our guide on . Otherwise, read on to learn more about how to get the most out of syncing data from your warehouse to Courier!
Add Courier to the set of destination services for your Census Segments. Sync them to new for targeting notifications.
Looking for another Courier feature? and let us know!
Learn more about all of our sync behaviors in our documentation.
Not seeing what you're looking for? about supporting alternative sync behaviors for this destination.
via support@getcensus.com or start a conversation with us via the chat.
