Good to know: Event source
The Autopilot Source is an event source. This means that it sends data as events, which are behaviors or occurrences tied to a user and a point in time. Data from these sources can be loaded into your Segment warehouses, and also sent to Segment streaming destinations. Learn more about cloud sources.
Autopilot makes automating customer journeys as simple as drawing on a whiteboard. Engage at just the right time with personalized emails, in-app messages, SMS, and postcards.
Take your company’s email analysis to the next level by adding Autopilot 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.
This source is maintained by Autopilot. For any issues with the source, you may contact their team.
This document was last updated on October 19, 2018. If you notice any gaps, outdated information or simply want to leave some feedback to help us improve our documentation, let us know!
- From your Segment UI’s Sources page click on “Add Source”.
- Search for AutopilotHQ within the Sources Catalog and confirm by clicking “Connect”.
- Give the Source a nickname and follow the set up flow to “Add Source”. The nickname is a label used in the Segment interface, and Segment creates a related schema name, which you query against in your warehouse. The nickname can be whatever you like, but we recommend sticking to something that reflects the source itself and distinguishes amongst your environments (Eg. SourceName_Prod, SourceName_Staging, SourceName_Dev).
- Sign in to your Autopilot account and visit the Segment destination to connect.
Autopilot uses our stream Source component to send events to Segment. These events are then available in any Destination that accepts server-side events, including your data warehouse.
Below is a table of events that Autopilot sends to Segment. These events will show up as tables in your warehouse, and as regular events in your other Destinations.
Autopilot will send the
userID if the contact has passed through the system before using Segment; otherwise Autopilot will send the email of the contact through as
Additionally, Autopilot also sends
|Email Bounced||Receiving server could not or would not accept message|
|Email Delivered||Message has been successfully delivered to the receiving server|
|Email Clicked||Recipient clicked on a link within the message|
|Email Marked as Spam||Recipient marked message as spam|
|Email Opened||Recipient has opened the HTML message|
|Email Unsubscribed||Recipient clicked on message’s subscription management link|
|Email Replied||Recipient replied to the message|
Below are tables outlining the properties included in the events listed above.
||The email event type|
||The ID of the journey|
||The name of the journey|
||The ID of the email|
||The subject line of the email|
||Defines the email as transactional or a one time send|
||The ID of the link clicked in an email|
||The URL of the link clicked in an email|
Now that your Source is set up, you can connect it with Destinations.
Log into your downstream tools and check to see that your events are populating and they contains all the properties you expect. If all your events and properties are not showing up, refer to the destination docs for troubleshooting.
If you experience any issues with how the events arrive in Segment, contact the Autopilot team.
Sending data to AutopilotHQ
The AutopilotHQ Source works better when you also connect AutopilotHQ as a Destination. With the AutopilotHQ Destination, you can use Segment to send Identify and Track calls to AutopilotHQ. Want to start sending website, mobile or server data TO AutopilotHQ? Head on over to our AutopilotHQ destination.
This page was last modified: 12 Jun 2020
Questions? Problems? Need more info? Contact us, and we can help!