Source is an automated email tool. It lets you set up rules to automatically send emails to your users after they perform actions, making drip email campaigns really easy. Visit Website

Take your company’s email analysis to the next level by adding as a Source to Segment. We’ll automatically collect email events like Email Delivered and Email Opened, forward them to your destinations, and load them into your data warehouse.

In your favorite BI or analytics tool, you’ll be able to analyze your email campaigns in SQL or through drag-and-drop reports. And, you’ll be able to join your data with the event data you’re already sending through Segment to analyze the down-funnel effects of your emails. Learn more about how you can use with Segment.

Getting Started

If you have previously enabled sending email events via the destination during our beta (using a project write key), you do not need to create new source. Your email data will continue to flow as normal.

  1. From your workspace’s<your-workspace>/sources page, click Add source.

  2. Choose

  3. Give the Source a nickname and a schema name. The nickname is a label used in the Segment interface, and the schema name is the namespace you query against in your warehouse. You can name them however you’d like, but we recommend sticking to something that reflects the Source itself, like Customerio for nickname and customerio for the schema name.

  4. The next page (“Overview”) will surface your Segment write key for Copy this write key.

  5. To finish the setup, you’ll have to go into your account and enter this Segment write key in their integrations settings. Find the right place in by clicking Settings > Integrations > Segment.

  1. Click Save.

  2. In Segment, click into your Source in<your-workspace>/sources. From there you’ll be able to add Destinations where you want to see email events.

That’s it! As you send emails, events will now be sent to your destinations and automatically loaded into any warehouses you have enabled.


Stream uses our stream Source component to send Segment email events. It uses a server-side track method to send data to Segment. These events are then available in any destination that accepts server-side events, and available in a schema in your data warehouse, so you can query via SQL.

The default behavior is for to pass the userId associated with the email recipient as the userId. There are cases in which does not have an associated userId, in which case the email address will be passed in as the anonymousId.


Collections are the groupings of data we pull from your Source. In your warehouse, each collection gets its own table, as well as a tracks table that aggregates all the events into a single table.

Email DeliveredEventMessage has been successfully delivered to the receiving server
Email OpenedEventRecipient has opened the HTML message. You need to enable Open Tracking for getting this type of event
Email Link ClickedEventRecipient clicked on a link within the message. You need to enable Click Tracking for getting this type of event
Email UnsubscribedEventRecipient clicked on message’s subscription management link
Email BouncedEventReceiving server could not or would not accept message
Email Marked as SpamEventRecipient marked message as spam

Send data to

The Source works better when you also connect as an destination. With the Destination, you can use Segment to send user and event data from which you trigger email campaigns. Want to start sending website or mobile data TO Head on over to our destination docs.

Questions? Need help? Contact us!
Can we improve this doc?
Email us:!