AutopilotApp Destination

Autopilot helps thousands of organizations around the world automate their communications via email notifications, such as regular email newsletters, abandoned cart emails, as well as SMS messages, and more, to help organizations market and grow their businesses faster.

Once you connect Segment to AutopilotApp (the Autopilot product), you can leverage Autopilot’s powerful campaign features on your Segment customer data.

This destination is maintained by Autopilot. For any issues with the destination, contact the Autopilot Support team.

Getting Started

1. From the Destinations catalog page in the Segment App, click Add Destination.
2. Search for “AutopilotApp” in the Destinations Catalog, and select the “AutopilotApp” destination.
3. Click Configure AutopilotApp and choose which Source should send data to the “AutopilotApp” destination.
4. If requested, specify the Destination Name for your “AutopilotApp” destination, and click Save.
5. Complete integrating your Autopilot account with Segment, which automatically configures your Autopilot API keys within your “AutopilotApp” destination in Segment.

Supported methods

Autopilot supports the following methods, as specified in the Segment Spec.

Identify

Send Identify calls to create or update people in Autopilot. For example:

analytics.identify('userId123', {
  firstName: 'John',
  lastName: 'Doe',
  email: 'john.doe@example.com'
});

Segment sends Identify calls to Autopilot as an identify event.

Track

Send Track calls to create or update activities (including activity attributes) in Autopilot. For example:

analytics.track('Login Button Clicked', {
  action: "login-clicked"
});

Segment sends Track calls to Autopilot as a track event.

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.