description |
---|
Step-by-step guide to set up Autopilot as a destination in RudderStack. |
Autopilot is a popular marketing automation platform that allows you to track and capture new leads and create detailed customer journeys. With Autopilot, you can connect with your existing customers by sending them personalized messages, and surveys to improve your product design. Autopilot allows you to boost your customer retention rate, and automate repetitive tasks with ease.
RudderStack allows you to configure Autopilot as a destination to which you can send your event data seamlessly.
{% hint style="success" %} Find the open-source transformer code for this destination in our GitHub repo. {% endhint %}
To enable sending data to Autopilot, you will first need to add it as a destination to the source from which you are sending your event data. Once the destination is enabled, events from our SDK will start flowing to Autopilot.
Connection Mode | Web | Mobile | Server |
---|---|---|---|
Device mode | - | - | - |
Cloud mode | - | Supported | Supported |
{% hint style="info" %} To know more about the difference between Cloud mode and Device mode in RudderStack, read the RudderStack connection modes guide. {% endhint %}
Once you have confirmed that the platform supports sending events to Autopilot, perform the steps below:
- From your RudderStack dashboard, add the source. From the list of destinations, select Autopilot.
{% hint style="info" %} Please follow our Adding a Source and Destination guide to add a source and destination in RudderStack. {% endhint %}
- Give a name to the destination and click on Next. You should then see the following screen.
- Fill up the details and click on Next to complete the configuration. Autopilot should now be added and enabled as a destination in RudderStack.
The identify
call captures the relevant details about the visiting user.
{% hint style="info" %}
For more information on the identify
method, please refer to our guide on RudderStack API Specification.
{% endhint %}
A sample identify
payload is as shown in the snippet below:
[[RSClient sharedInstance] identify:@"developer_user_id"
traits:@{@"foo": @"bar", @"foo1": @"bar1"}];
The track
call captures the information related to the actions performed by the user, along with their properties, or traits.
{% hint style="info" %}
For more information on the track
method, please refer to our guide on RudderStack API Specification.
{% endhint %}
A sample track
payload is as shown in the snippet below:
[[RudderClient sharedInstance] track:@"test_event"
properties:@{@"key":@"value", @"foo": @"bar"}]
You can retrieve the API key from the settings page of the Autopilot dashboard. For more information, please check the Getting Started section above.
If you come across any issues while configuring Autopilot with RudderStack, please feel free to contact us. You can also start a conversation on our Slack channel; we will be happy to talk to you!