Autopilot Destination
AutopilotHQ quick info
AutopilotHQ accepts Track, and Identify calls. If you reference it in the Integrations object, call it “AutopilotHQ”.
AutopilotHQ accepts cloud-mode data from all Segment source types. It does not offer device-mode connections.
Autopilot helps thousands of organizations around the world automate their marketing with visual and simple customer journey marketing software.
This destination is maintained by Autopilot. See Autopilot’s documentation for more information. For any issues with the destination, contact our friends at Autopilot.
Are you instead trying to set up Autopilot as a Source to get data from Autopilot into your data warehouse or other downstream tools? See our documentation on our Autopilot source instead.
This document was last updated on October 12, 2018. If you notice any gaps, outdated information or simply want to leave some feedback to help us improve our documentation, let us know!
Getting Started
Before you start, make sure AutopilotHQ supports the source type and connection mode you’ve chosen to implement. You can learn more about connection modes here.
Web | Mobile | Server | |
---|---|---|---|
📱 Device-mode | ⬜️ | ⬜️ | ⬜️ |
☁️ Cloud-mode | ✅ | ✅ | ✅ |
- From the Segment web app, click Catalog.
- Search for “Autopilot” in the Catalog, select it, and choose which of your sources to connect the destination to.
- In the destination settings, enter your “API Key” from here or go to Autopilot: Settings -> App Connections -> Segment and copy/paste the API key which is listed there.
- Once enabled ‘identify’ and ‘track’ calls will be sent to Autopilot.
Identify
If you’re not familiar with the Segment Specs, take a look to understand what the Identify method does. An example call would look like:
analytics.identify('12091906-01011992', {
name: 'John Joe',
email: 'john.doe@example.com'
});
Track
If you’re not familiar with the Segment Specs, take a look to understand what the Track method does. An example call would look like:
analytics.track("Step Activated", {
property: "test"
});
Appendices
Additional Autopilot Tracking code will be required on your site to unlock the following features:
- Website activity for anonymous and known visitors (‘page’ calls).
- Capturing form submissions.
- Triggering Headsup messages.
- User association using the Autopilot Javascript library.
For complete details, visit the Autopilot page How to use Segment with Autopilot.
Personas
You can send computed traits and audiences generated using Segment Personas to this destination as a user property. To learn more about Personas, contact us for a demo.
For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Personas sends an Identify call with the property order_completed_last_30days: true
. When the user no longer satisfies this condition (for example, it’s been more than 30 days since their last order), Personas sets that value to false
.
When you first create an audience, Personas sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.
Settings
Segment lets you change these destination settings from the Segment app without having to touch any code.
API Key
Get your API key from here or go to Autopilot: Settings -> App Connections -> Segment and copy/paste the API key which is listed there.
This page was last modified: 20 Oct 2020
Need support?
Questions? Problems? Need more info? Contact us, and we can help!