segmentio · rchinn1 · Oct 31, 2023 · Aug 28, 2023 · Aug 28, 2023 · Aug 30, 2023
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination categories last updated 2023-10-26 
+# destination categories last updated 2023-10-31 
 items:
 - display_name: A/B Testing
   slug: a-b-testing

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2023-10-26 
+# destination data last updated 2023-10-31 
 items:
 - id: 637e8d185e2dec264895ea89
   display_name: 1Flow
@@ -20824,9 +20824,9 @@ items:
   display_name: Emarsys (Actions)
   name: Emarsys (Actions)
   slug: actions-emarsys
-  hidden: true
+  hidden: false
   endpoints:
-  - US
+  - EU
   regions:
   - us-west-2
   - eu-west-1
@@ -49884,14 +49884,14 @@ items:
 - id: 64b6a221baf168a989be641a
   display_name: Listrak (Actions)
   name: Listrak (Actions)
-  slug: listrak-actions
+  slug: actions-listrak
   hidden: false
   endpoints:
   - US
   regions:
   - us-west-2
   - eu-west-1
-  url: connections/destinations/catalog/listrak-actions
+  url: connections/destinations/catalog/actions-listrak
   previous_names:
   - Listrak (Actions)
   website: https://www.listrak.com/

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2023-10-26 
+# destination data last updated 2023-10-31 
 items:
   - id: 54521fd725e721e32a72eec6
     display_name: Intercom

@@ -225,6 +225,15 @@ sources:
       - us
     endpoints:
       - us
+  - id: NC2jsEkA8Y
+    display_name: Elastic Path CX Studio
+    hidden: false
+    slug: elastic-path-cx-studio
+    url: connections/sources/catalog/cloud-apps/elastic-path-cx-studio
+    regions:
+      - us
+    endpoints:
+      - us
   - id: mazatB39IS
     display_name: Facebook Ads
     hidden: false
@@ -638,15 +647,6 @@ sources:
       - us
     endpoints:
       - us
-  - id: o9OyD6xsVJ
-    display_name: OneSignal
-    hidden: false
-    slug: onesignal
-    url: connections/sources/catalog/cloud-apps/onesignal
-    regions:
-      - us
-    endpoints:
-      - us
   - id: QhEUZnE5uF
     display_name: OneTrust
     hidden: false

@@ -122,4 +122,6 @@ destinations:
   - original: "algolia-insights-actions"
     override: "actions-algolia-insights"
   - original: "iterable-actions"
-    override: "actions-iterable"
+    override: "actions-iterable"
+  - original: "listrak-actions"
+    override: "actions-listrak"
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# source categories last updated 2023-10-26 
+# source categories last updated 2023-10-31 
 items:
   - display_name: A/B Testing
     slug: a-b-testing

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# sources last updated 2023-10-26 
+# sources last updated 2023-10-31 
 items:
   - id: 8HWbgPTt3k
     display_name: .NET
@@ -476,6 +476,24 @@ items:
     categories:
       - Raw Data
       - Personalization
+  - id: NC2jsEkA8Y
+    display_name: Elastic Path CX Studio
+    isCloudEventSource: true
+    slug: elastic-path-cx-studio
+    url: connections/sources/catalog/cloud-apps/elastic-path-cx-studio
+    hidden: false
+    regions:
+      - us
+    endpoints:
+      - us
+    source_type: cloud-app
+    description: Automated commerce events from CX Studio
+    logo:
+      url: >-
+        https://cdn-devcenter.segment.com/2defdd87-4bd6-4dc0-95eb-cde4cd1e2f50.png
+    categories:
+      - Raw Data
+      - Personalization
   - id: mazatB39IS
     display_name: Facebook Ads
     isCloudEventSource: false
@@ -1332,23 +1350,6 @@ items:
       url: https://d3hotuclm6if1r.cloudfront.net/logos/nudgespot-default.svg
     categories:
       - Email Marketing
-  - id: o9OyD6xsVJ
-    display_name: OneSignal
-    isCloudEventSource: true
-    slug: onesignal
-    url: connections/sources/catalog/cloud-apps/onesignal
-    hidden: false
-    regions:
-      - us
-    endpoints:
-      - us
-    source_type: cloud-app
-    description: Multi-channel messaging automation
-    logo:
-      url: >-
-        https://cdn-devcenter.segment.com/8a3ac3c4-1518-421a-8193-0d7fc27f568b.png
-    categories:
-      - SMS & Push Notifications
   - id: QhEUZnE5uF
     display_name: OneTrust
     isCloudEventSource: true

@@ -5,7 +5,7 @@ hidden: true
 published: false
 ---
 
-[1Flow](https://1flow.app/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) is a leading in-app user survey and messaging platform for Mobile app and SaaS businesses.
+[1Flow](https://1flow.app/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} is a leading in-app user survey and messaging platform for Mobile app and SaaS businesses.
 
 Using 1Flow, you can reach users _in-the-moment_ while they are interacting with your website or application, to collect highly contextual user insights that help you improve your product offering and customer experience.
 
@@ -17,7 +17,7 @@ This destination is maintained by 1Flow. For any issues with the destination, [c
 1. From the Destinations catalog page in the Segment App, click **Add Destination**.
 2. Search for **1Flow** in the Destinations Catalog, and select the **1Flow** destination.
 3. Choose which Source should send data to the 1Flow destination.
-4. Go to the [1Flow dashboard](https://dashboard.1flow.app/){:target="\_blank"} and find the **API Key** in Project Settings.
+4. Go to the [1Flow dashboard](https://dashboard.1flow.app/){:target="_blank"} and find the **API Key** in Project Settings.
 5. Enter the **API Key** in the 1Flow destination settings in Segment.
 
 ## Supported methods

@@ -5,7 +5,7 @@ redirect_from:
   - '/connections/destinations/catalog/1flow-analytics'
 ---
 
-[1Flow](https://1flow.app/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) is a leading in-app user survey and messaging platform for Mobile app and SaaS businesses.
+[1Flow](https://1flow.app/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} is a leading in-app user survey and messaging platform for Mobile app and SaaS businesses.
 
 Using 1Flow, you can reach users _in-the-moment_ while they are interacting with your website or application, to collect highly contextual user insights that help you improve your product offering and customer experience.
 
@@ -16,7 +16,7 @@ This destination is maintained by 1Flow. For any issues with the destination, [c
 1. From the Destinations catalog page in the Segment App, click **Add Destination**.
 2. Search for **1Flow** in the Destinations Catalog, and select the **1Flow** destination.
 3. Choose which Source should send data to the 1Flow destination.
-4. Go to the [1Flow dashboard](https://dashboard.1flow.app/){:target="\_blank"} and find the **API Key** in Project Settings.
+4. Go to the [1Flow dashboard](https://dashboard.1flow.app/){:target="_blank"} and find the **API Key** in Project Settings.
 5. Enter the **API Key** in the 1Flow destination settings in Segment.
 
 ## Supported methods

@@ -3,7 +3,7 @@ title: 2mee Destination
 rewrite: true
 id: 60b5d0a01f3726b85dc05aab
 ---
-[2mee](https://2mee.com ) is a Human Hologram platform that automatically cuts the person out from the background, removing the visual clutter, and places them in the familiar context of your phone or website so that they dominate the screen.
+[2mee](https://2mee.com){:target="_blank”} is a Human Hologram platform that automatically cuts the person out from the background, removing the visual clutter, and places them in the familiar context of your phone or website so that they dominate the screen.
 
 This destination is maintained by 2mee. For any issues with the destination, [contact the 2mee Support team](mailto:[email protected]).
 
@@ -15,7 +15,7 @@ This destination is maintained by 2mee. For any issues with the destination, [co
 2. Search for **2mee** in the Destinations Catalog and it.
 3. Click **Configure 2mee**. 
 4. Choose which Source should send data to the 2mee destination.
-5. Go to 2mee and copy the [API Key and Application ID](https://docs.2mee.com/documentation/segment) from the 2mee Dashboard.
+5. Go to 2mee and copy the [API Key and Application ID](https://docs.2mee.com/documentation/segment){:target="_blank”} from the 2mee Dashboard.
 6. Go back to Segment and paste the API Key and Application ID you just copied in the 2mee destination settings. Make sure to paste the API Key in this format: `Bearer <API Key>`.
 
 ## Supported methods
@@ -41,7 +41,7 @@ Identify calls with a `userId` not mapped to a device fails with a `400` error c
 
 Send [Track](/docs/connections/spec/track/) calls to track the actions your users perform.
 
-Configure the HoloCapsule setting in the [2mee](https://go.2mee.com/) app.
+Configure the HoloCapsule setting in the [2mee](https://go.2mee.com/){:target="_blank”} app.
 
 Segment requires the `userId`. Track calls without a `userId` or with a `userId` not mapped to a device fail with a `400` code.
 

@@ -3,7 +3,7 @@ title: Aampe Destination
 id: 6188d844be5cf0e3b59189d2
 ---
 
-[Aampe](https://aampe.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) uses automated, rapid learning to personalize notifications, and continuously learns what messages bring value to your customer.
+[Aampe](https://aampe.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} uses automated, rapid learning to personalize notifications, and continuously learns what messages bring value to your customer.
 
 This destination is maintained by Aampe. For any issues with the destination, [contact the Aampe Support team](mailto:[email protected]).
 
@@ -14,7 +14,7 @@ This destination is maintained by Aampe. For any issues with the destination, [c
 1. From the Destinations catalog page in the Segment App, click **Add Destination**.
 2. Search for "Aampe" in the Destinations Catalog, and select the "Aampe" destination.
 3. Choose which Source should send data to the "Aampe" destination.
-4. Go to the [Data Integrations page](https://compose.aampe.com/configure/integrations) on Aampe Composer, click on "Add Integration", select "Segment" and click "Next".
+4. Go to the [Data Integrations page](https://compose.aampe.com/configure/integrations){:target="_blank”} on Aampe Composer, click on "Add Integration", select "Segment" and click "Next".
 5. Copy the Segment API Key from the resulting page.
 6. Enter this key in "API Key" in the "Aampe" destination settings in Segment.
 
@@ -24,7 +24,7 @@ Aampe supports the following methods, as specified in the [Segment Spec](/docs/c
 
 ### Track
 
-Segment sends [Track](/docs/connections/spec/track) calls to Aampe as a `track` event. These are used by Aampe to display engagement activity and reports in the [Aampe Composer](https://compose.aampe.com). You can use these to configure goals that are used for monitoring and creating campaigns. It may take up to 24 hours for events to show up in the Aampe Composer.
+Segment sends [Track](/docs/connections/spec/track) calls to Aampe as a `track` event. These are used by Aampe to display engagement activity and reports in the [Aampe Composer](https://compose.aampe.com){:target="_blank”}. You can use these to configure goals that are used for monitoring and creating campaigns. It may take up to 24 hours for events to show up in the Aampe Composer.
 
 ```js
 analytics.track("Login Button Clicked");

@@ -24,7 +24,7 @@ Segment provides specific implementation details for A/B Smartly in the sections
 1. From the Destinations catalog page in the Segment App, click **Add Destination**.
 2. Search for "A/B Smartly" in the Destinations Catalog, and select the "A/B Smartly" destination.
 3. Choose which Source should send data to the "A/B Smartly" destination.
-4. Go to the A/B Smartly dashboard(https://your-org-name.absmartly.com/apikey/list), find and copy the "API key" that you created for segment.
+4. Go to the A/B Smartly dashboard(https://your-org-name.absmartly.com/apikey/list){:target="_blank”}, find and copy the "API key" that you created for segment.
 5. Enter the "API Key" in the "A/B Smartly" destination settings in Segment.
 6. If the integration requests for an Application name go to your A/B Smartly dashboard (`https://your-org-name.absmartly.com/application/create`) and create an Application named "Segment", or whatever you would like to call it. Use that name in the Application field of the integration settings.
 7. Add also your A/B Smartly Collector endpoint. It's the same endpoint that you are using in all your A/B Smartly SDKs.

@@ -13,7 +13,7 @@ With the [Algolia Insights (Actions)](https://www.algolia.com/products/analytics
 - Personalization
 - Algolia Recommend
 
-This destination is maintained by [Algolia](https://www.algolia.com/). For any issues with the destination, [contact the Algolia team](mailto:[email protected]).
+This destination is maintained by [Algolia](https://www.algolia.com/){:target="_blank”}. For any issues with the destination, [contact the Algolia team](mailto:[email protected]).
 
 ## Getting Started
 
@@ -44,7 +44,7 @@ index.search('query', {
 })
 ``` 
 
-Once this is enabled you will be able to send properties like queryId in your segment events. You can read more about how to send Algolia-related data to Segment from [the documentation at Algolia](https://www.algolia.com/doc/guides/sending-events/implementing/connectors/segment/).
+Once this is enabled you will be able to send properties like queryId in your segment events. You can read more about how to send Algolia-related data to Segment from [the documentation at Algolia](https://www.algolia.com/doc/guides/sending-events/implementing/connectors/segment/){:target="_blank”}.
 
 ## Mapping Events