AutopilotHQ Source

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 is an Event Cloud Source which can not only export data into your Segment warehouse, but they can also federate the exported data into your other enabled Segment Destinations.

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, please let us know!

Getting Started

  1. From your Segment UI’s Sources page click on “Add Source”.
  2. Search for AutopilotHQ within the Sources Catalog and confirm by clicking “Connect”.
  3. Give the Source a nickname and follow the setup flow to “Add Source”. The nickname will be used to designate the source in the Segment interface, and Segment will create a related schema name. The schema name is the namespace you’ll be querying 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).
  4. Sign in to your Autopilot account and visit the Segment destination to connect.

Components

Stream

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.

Events

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 via Segment; otherwise Autopilot will send the email of the contact through as anonymousID.

Additionally, Autopilot also sends email and contact_id under context.traits.

Event NameDescription
Email BouncedReceiving server could not or would not accept message
Email DeliveredMessage has been successfully delivered to the receiving server
Email ClickedRecipient clicked on a link within the message
Email Marked as SpamRecipient marked message as spam
Email OpenedRecipient has opened the HTML message
Email UnsubscribedRecipient clicked on message’s subscription management link
Email RepliedRecipient replied to the message

Event Properties

Below are tables outlining the properties included in the events listed above.

Property NameDescription
eventThe email event type
campaign_idThe ID of the journey
campaign_nameThe name of the journey
email_idThe ID of the email
email_subjectThe subject line of the email
transactionalDefines the email as transactional or a one time send
link_idThe ID of the link clicked in an email
link_urlThe URL of the link clicked in an email

Adding Destinations

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 there are any issues with how the events are arriving to Segment, please 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.


If you have any questions, or see anywhere we can improve our documentation, please let us know!