From 87322b1e6cafb96410c8f9af9026bf9a19fffef2 Mon Sep 17 00:00:00 2001 From: Liz Kane <68755692+lizkane222@users.noreply.github.com> Date: Thu, 31 Aug 2023 17:17:44 -0700 Subject: [PATCH 1/2] Update index.md Autopilot requires userId or email in identify events --- src/connections/destinations/catalog/autopilothq/index.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/connections/destinations/catalog/autopilothq/index.md b/src/connections/destinations/catalog/autopilothq/index.md index 692883287b..b7c5fb6f99 100644 --- a/src/connections/destinations/catalog/autopilothq/index.md +++ b/src/connections/destinations/catalog/autopilothq/index.md @@ -49,3 +49,7 @@ Additional Autopilot Tracking code will be required on your site to unlock the f - User association using the Autopilot JavaScript library. For complete details, visit the Autopilot page [How to use Segment with Autopilot](https://support.autopilothq.com/hc/en-us/articles/203658119). + +## Important notes +### Engage +The Autopilot destination requires either email or userId in all Identify events. If neither are provided in the payload then the Autopilot destination's Event Delivery tab will show a 400 Bad Request error message : _"Missing unique identifier traits. Either `email` or `user_id` traits must be provided"_ From d41297cbabc8b1c5de8a609ac4d7eec49bdcb7e5 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Wed, 8 Nov 2023 08:47:18 -0800 Subject: [PATCH 2/2] Update index.md --- .../destinations/catalog/autopilothq/index.md | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/src/connections/destinations/catalog/autopilothq/index.md b/src/connections/destinations/catalog/autopilothq/index.md index 06c998dadd..0385ead9d2 100644 --- a/src/connections/destinations/catalog/autopilothq/index.md +++ b/src/connections/destinations/catalog/autopilothq/index.md @@ -10,9 +10,6 @@ This destination is maintained by Autopilot. See [Autopilot's documentation](ht 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](/docs/connections/sources/catalog/cloud-apps/autopilothq/) instead. ## Getting Started - - - 1. From the Segment web app, click **Catalog**. 2. Search for "Autopilot" in the Catalog, select it, and choose which of your sources to connect the destination to. 3. In the destination settings, enter your "API Key" from [here](https://login.autopilothq.com/login#settings/app-connections/segment-sync){:target="_blank”} or go to Autopilot: Settings -> App Connections -> Segment and copy/paste the API key which is listed there. @@ -29,6 +26,9 @@ analytics.identify('12091906-01011992', { }); ``` +> info "Engage requires Identify calls from the Autopilot destination to include email or userId" +> If neither are provided in the payload then the Autopilot destination's [Event Delivery](/docs/connections/event-delivery/) tab will show a 400 Bad Request error message : _"Missing unique identifier traits. Either `email` or `user_id` traits must be provided"_. + ## Track If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: @@ -49,7 +49,3 @@ Additional Autopilot Tracking code will be required on your site to unlock the f - User association using the Autopilot JavaScript library. For complete details, visit the Autopilot page [How to use Segment with Autopilot](https://support.autopilothq.com/hc/en-us/articles/203658119){:target="_blank”}. - -## Important notes -### Engage -The Autopilot destination requires either email or userId in all Identify events. If neither are provided in the payload then the Autopilot destination's Event Delivery tab will show a 400 Bad Request error message : _"Missing unique identifier traits. Either `email` or `user_id` traits must be provided"_.