Merge pull request #277 from segmentio/repo-sync

repo sync

Author: bot-docsteam

src/connections/destinations/catalog/crossing-minds/index.md

@@ -0,0 +1,60 @@
+---
+title: Crossing Minds Destination
+id:
+hidden: true
+---
+
+[Crossing Minds](https://crossingminds.com/){:target="blank"} is a recommendation platform for businesses using next-gen AI that instantly anticipates customers’ wants and needs using only anonymized user data.
+
+Crossing Minds maintains this destination. For any issues with the destination, [contact the Crossing Minds Support team](mailto:[email protected]).
+
+{% include content/beta-note.md %}
+
+
+## Getting Started
+
+1. Contact your Crossing Minds Account Manager and request your integration API Key, API Password, and Database ID.
+2. From the Destinations catalog page in the Segment App, click **Add Destination**.
+3. In the Destinations Catalog, search for "Crossing Minds" and select the "Crossing Minds" destination.
+4. Choose which source should send data to the Crossing Minds destination.
+5. In the Crossing Minds destination settings in Segment, enter the Service Account Name as the **API Key**, Service Account Password as the **API Password**, and the **Database ID**.
+
+
+## Supported methods
+
+Crossing Minds supports the following methods, as specified in the [Segment Spec](/docs/connections/spec).
+
+
+### Identify
+
+Send [Identify](/docs/connections/spec/identify) calls to create or update a **Crossing Minds User** for any identified user on your site.
+
+For example:
+```js
+analytics.identify('userId123', {
+  email: '[email protected]'
+});
+```
+
+Segment sends Identify calls to Crossing Minds as an `identify` event.
+
+
+### Track
+
+Send [Track](/docs/connections/spec/track) calls to record User Interactions as:
+
+* All actions listed under [Browsing overview](/docs/connections/spec/ecommerce/v2/#browsing-overview)
+* All actions listed under [Core Ordering Overview](/docs/connections/spec/ecommerce/v2/#core-ordering-overview)
+* All actions listed under [Wishlisting overview](/docs/connections/spec/ecommerce/v2/#wishlisting-overview)
+* All actions listed under [Sharing overview](/docs/connections/spec/ecommerce/v2/#sharing-overview)
+* All actions listed under [Reviewing overview](/docs/connections/spec/ecommerce/v2/#reviewing-overview)
+
+
+For example:
+
+```js
+analytics.track('Login Button Clicked')
+```
+
+Segment sends Track calls to Crossing Minds as a `track` event.
+Any events that are not listed in the mentioned categories will be rejected.

src/connections/destinations/catalog/retentive/index.md

@@ -0,0 +1,46 @@
+---
+title: Retentive Destination
+id:
+hidden: true
+---
+[Retentive](https://retentive.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="blank"} makes your help docs searchable in product so go-to-market teams can act on data that each customer struggles with.
+
+Retentive maintains this destination. For any issues with the destination, [contact the Retentive Support team](mailto:[email protected]).
+
+## Getting Started
+
+{% include content/connection-modes.md %}
+
+1. From the Destinations catalog page in the Segment App, click **Add Destination**.
+2. In the Destinations Catalog, search for "Retentive" and select the Retentive destination.
+3. Choose which source should send data to the Retentive destination.
+4. Navigate to the [Retentive integrations tab](https://app.retentive.io/integrations){:target="blank"}.
+5. Toggle the Segment integration on, and copy the API key presented.
+6. In the Retentive destination settings in Segment, enter the API key.
+
+## Supported methods
+
+Retentive supports the following methods, as specified in the [Segment Spec](/docs/connections/spec).
+
+### Identify
+
+Send [Identify](/docs/connections/spec/identify) calls to track user metadata alongside their search queries in the Retentive dashboard. For example:
+
+```js
+analytics.identify('userId123', {
+  email: '[email protected]'
+});
+```
+
+Customer data only displays once customers perform searches on Retentive.
+
+### Alias
+
+Send [Alias](/docs/connections/spec/alias) calls to merge customers from different destinations into a single customer in Retentive. For example:
+
+```js
+analytics.alias(
+    'primaryId',
+    'previousId' // optional
+);
+```