Comment on page
This page describes how to use Census with Courier.
In this guide, we will show you how to connect Courier to Census and create your first sync.
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 Courier's API Key documentation 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.
- 1.Inside Census, click on Destinations in the left navigation, click New Destination and then find Courier in the menu.
- 2.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.
- 3.Copy in your API Key from Courier
And that's it! If this is your very first sync with Census, jump back to our guide on Creating Syncs. Otherwise, read on to learn more about how to get the most out of syncing data from your warehouse to Courier!
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!
Like Courier, we use the
recipient_idas the primary identifier for Profiles. A
recipient_idis 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.