Added redirects and related destinations (#2782)

Author: markzegarelli

src/_includes/content/actions-classic.md

@@ -0,0 +1,18 @@
+{% assign versions = page.versions %}
+
+<div class="premonition info">
+<div class="fa fa-info-circle"></div>
+<div class="content">
+<p class="header">Additional versions of this destination are available</p>
+<p>This page is about the {{page.title}}. See below for information about other versions of the {{page.title | split: " " | first}} destination:
+<ul>
+{% for version in versions%}
+<li><a href="{{version.link}}">{{version.name}}</a></li>
+
+{% endfor %}
+</ul>
+</p>
+
+
+</div>
+</div>

src/_layouts/destination.html

@@ -10,7 +10,11 @@
   {{destination-dossier | markdownify}}
 
 {% endif %}
-  
+
+{% if page.versions %}
+{% include content/actions-classic.md %}
+
+{% endif %}
 
 
 {% if page.maintenance == true %}

src/connections/destinations/catalog/actions-amplitude/index.md

@@ -3,6 +3,11 @@ title: Amplitude (Actions) Destination
 hide-boilerplate: true
 hide-dossier: false
 id: 5f7dd6d21ad74f3842b1fc47
+versions:
+  - name: "Amplitude (Classic)"
+    link: '/docs/connections/destinations/catalog/amplitude'
+redirect_from:
+  - '/connections/destinations/catalog/vendor-amplitude/'
 ---
 {% include content/plan-grid.md name="actions" %}
 

src/connections/destinations/catalog/actions-customer-io/index.md

@@ -3,56 +3,5 @@ title: Customer.io (Actions) Destination
 hide-personas-partial: true
 hide-boilerplate: false
 hide-dossier: true
+published: false
 ---
-{% include content/plan-grid.md name="actions" %}
-
-[Customer.io](https://customer.io/){:target="_blank"} lets you send automated email, push, SMS, letters, and webhooks based on your customer's activities in your app or product. It makes conversion tracking, optimization and remarketing easier. 
-
-> info ""
-> This document is about a feature which is in beta. This means that the Destination Actions are in active development, and some functionality may change before it becomes generally available
-
-
-> success ""
-> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Customer.io Segment destination. There's also a page about the [non-Actions Customer.io destination](/docs/connections/destinations/catalog/customer-io/). Both of these destinations receives data _from_ Segment. There's also the [Customer.io source](/docs/connections/sources/catalog/cloud-apps/customer-io/), which sends data _to_ Segment!
-
-## Benefits of Customer.io (Actions) vs Customer.io classic
-
-- **Track an anonymous event**. Track events from users who are not yet known to Customer.io. If you have the Customer.io *event merging* feature enabled, Customer.io associates all incoming events that share an `anonymous_id` received in the last 30 days.
-
-## Getting started
-
-1. From the Segment web app, click **Catalog**, then click **Destinations**.
-2. Find the Destinations Actions item in the left navigation, and click it.
-3. Select Customer.io (Actions).
-4. Click **Configure Actions Customer.io**.
-5. Select an existing Source to connect to Customer.io (Actions).
-6. Enter the **API Key** and **Site ID**. Find these values on the [Customer.io API Credentials Page](https://fly.customer.io/settings/api_credentials){:target="_blank"}.
-7. Select **Quick Setup** to start with pre-populated subscriptions, or **Customized Setup** to configure each action from scratch. Click **Configure Actions**.
-
-## Prebuilt subscriptions
-
-| Subscription Name       | Trigger                                                               | Customer.io Action      |
-| ----------------------- | --------------------------------------------------------------------- | ----------------------- |
-| Track Event             | All **Track** calls from the connected source.                        | Track Event             |
-| Create or Update Person | All **Identify** calls from the connected source.                     | Create or Update Person |
-| Create or Update Device | All **Track** calls where the Event Name is `Application Installed`. | Create or Update Device |
-
-## Available Customer.io actions
-
-Build your own subscription. Combine the supported [triggers](/docs/connections/destinations/actions/#components-of-a-destination-action) with the following Customer.io-supported actions:
-
-- [Track Event](#track-event)
-- [Create or Update Person](#create-or-update-person)
-- [Create or Update Device](#create-or-update-device)
-- [Track Anonymous Event](#track-anonymous-event)
-
-{% include components/actions-fields.html name="customer-io" %}
-
-
-## Migration from Customer.io classic
-
-{% include content/ajs-upgrade.md %}
-
-
-Keep the following in mind if you plan to move to Customer.io (Actions) from the classic Customer.io destination.
-{% include components/actions-map-table.html name="customer-io" %}

src/connections/destinations/catalog/actions-fullstory/index.md

@@ -3,14 +3,16 @@ title: FullStory (Actions)
 hide-boilerplate: true
 hide-dossier: false
 id: 6141153ee7500f15d3838703
+redirect_from:
+  - '/connections/destinations/catalog/vendor-fullstory'
+versions:
+  - name: Fullstory (Classic)
+    link: /docs/connections/destinations/catalog/fullstory
 ---
 {% include content/plan-grid.md name="actions" %}
 
 [FullStory](https://www.fullstory.com/){:target="_blank"} lets product and support teams easily understand everything about the customer experience. The Segment integration for FullStory helps accurately identify your customers within the FullStory dashboard.
 
-> success ""
-> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) FullStory Segment destination. There's also a page about the [non-Actions FullStory destination](/docs/connections/destinations/catalog/fullstory/). Both of these destinations receives data from Segment. 
-
 ## Benefits of FullStory (Actions) vs FullStory Classic
 
 - Greater control over the page properties you send.

src/connections/destinations/catalog/actions-slack/index.md

@@ -3,13 +3,16 @@ title: Slack (Actions) Destination
 hide-boilerplate: true
 hide-dossier: false
 id: 5f7dd8e302173ff732db5cc4
+redirect_from:
+  - '/connections/destinations/catalog/vendor-slack'
+versions:
+  - name: Slack (Classic)
+    link: /docs/connections/destinations/slack
 ---
 {% include content/plan-grid.md name="actions" %}
 
 [Slack](https://www.slack.com){:target="_blank"} is a team collaboration tool work flows. It's where the people you need, the information you share, and the tools you use come together to get things done.
 
-> success ""
-> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Slack Segment destination. There's also a page about the [non-Actions Slack destination](/docs/connections/destinations/catalog/slack/). Both of these destinations receives data from Segment. 
 
 ## Benefits of Slack (Actions) vs Slack Classic
 

src/connections/destinations/catalog/braze-web-device-mode-actions/index.md

@@ -4,18 +4,18 @@ hide-boilerplate: true
 hide-dossier: false
 redirect_from:
   - '/connections/destinations/catalog/actions-braze-web/'
+  - '/connections/destinations/catalog/vendor-braze/'
 id: 60fb01aec459242d3b6f20c1
+versions:
+  - name: 'Braze Cloud Mode (Actions)'
+    link: '/docs/connections/destinations/catalog/braze-cloud-mode-actions'
+  - name: 'Braze (Classic)'
+    link: '/docs/connections/destinations/catalog/braze'
 ---
 {% include content/plan-grid.md name="actions" %}
 
 [Braze](https://www.braze.com/){:target="_blank"}, formerly Appboy, is an engagement platform that empowers growth by helping marketing teams to build customer loyalty through mobile, omni-channel customer experiences.
 
-
-
-
-> success ""
-> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Braze Segment destination. There's also a page about the [non-Actions Braze destination](/docs/connections/destinations/catalog/braze/). Both of these destinations receives data _from_ Segment. There's also the [Braze source](/docs/connections/sources/catalog/cloud-apps/braze/), which sends data _to_ Segment.
-
 ## Benefits of Braze Web Mode (Actions) vs Braze Classic
 
 Braze Web Mode (Actions) provides the following benefits over Braze Classic:

src/connections/destinations/catalog/customer-io-actions/index.md

@@ -2,19 +2,19 @@
 title: Customer.io (Actions) Destination
 hide-personas-partial: true
 hide-boilerplate: true
-hide-dossier: true
 redirect_from:
 - '/connections/destinations/catalog/actions-customerio/'
 - '/connections/destinations/catalog/actions-customer-io/'
+- '/connections/destinations/catalot/vendor-customerio'
+versions:
+  - name: Customer.io (Classic)
+    link: /docs/connections/destinations/catalog/customer-io
 id: 5f7dd78fe27ce7ff2b8bfa37
 ---
 {% include content/plan-grid.md name="actions" %}
 
 [Customer.io](https://customer.io/){:target="_blank"} lets you send automated email, push, SMS, letters, and webhooks based on your customer's activities in your app or product. It makes conversion tracking, optimization and remarketing easier. 
 
-> success ""
-> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Customer.io Segment destination. There's also a page about the [non-Actions Customer.io destination](/docs/connections/destinations/catalog/customer-io/). Both of these destinations receives data _from_ Segment. There's also the [Customer.io source](/docs/connections/sources/catalog/cloud-apps/customer-io/), which sends data _to_ Segment!
-
 ## Benefits of Customer.io (Actions) vs Customer.io classic
 
 - **Track an anonymous event**. Track events from users who are not yet known to Customer.io. If you have the Customer.io *event merging* feature enabled, Customer.io associates all incoming events that share an `anonymous_id` received in the last 30 days.
@@ -44,7 +44,7 @@ Keep the following in mind if you plan to move to Customer.io (Actions) from the
 
 ## Convert timestamps
 
-When you map some actions, you'll see a **Convert Timestamps** setting. This setting is on by default, and converts traits containing ISO-8601 timestamps to Unix timestamps (seconds since epoch). We strongly suggest that you leave this setting enabled. While we support ISO-8601 timestamps in liquid, you must use Unix timestamps to take advantage of timestamp conditions when segmenting your audience in Customer.io.
+When you map some actions, you'll see a **Convert Timestamps** setting. This setting is on by default, and converts traits containing ISO-8601 timestamps to Unix timestamps (seconds since epoch). Segment recommends that you leave this setting enabled. While Segment does support ISO-8601 timestamps in liquid, you must use Unix timestamps to take advantage of timestamp conditions when segmenting your audience in Customer.io.
 
 For example, if you send an event with a `purchase_time` trait of `2006-01-02T18:04:07Z`, Customer.io converts it to `1136253847`. If the timestamp is *not* in ISO-8601 format, Customer.io doesn't convert it. This avoids inadvertently converting values like phone numbers or IDs. 
 

src/connections/destinations/catalog/sprig-cloud/index.md

@@ -4,13 +4,14 @@ rewrite: true
 redirect_from:
  - '/connections/destinations/catalog/userleap/'
 id: 5f2c35239094d175b6485eb1
+versions:
+  - name: Sprig (Actions)
+    link: /docs/connections/destinations/catalog/sprig-web
 ---
 [Sprig (formerly UserLeap)](https://sprig.com/?&utm_source=segment_2021-10-20&utm_medium=int&utm_campaign=integration) is an in-context user research platform that makes it fast and effortless for product teams to learn from their actual customers in real time, through microsurveys, concept tests, and video questions.
 
 Sprig maintains this destination. For any issues with the destination, consult [Sprig's documentation](https://docs.sprig.com/docs/segment) or contact [[email protected]](mailto:[email protected]).
 
-> success ""
-> **Good to know**: This page is about the [non-Actions Sprig (formerly UserLeap) destination](/docs/connections/destinations/catalog/userleap/). There's also a page about the [Actions-framework](/docs/connections/destinations/actions/) Sprig Segment destination. Both of these destinations receive data from Segment.
 ## Getting Started
 
 {% include content/connection-modes.md %}

src/connections/destinations/catalog/sprig-web/index.md

@@ -5,7 +5,11 @@ hide-boilerplate: true
 hide-dossier: true
 redirect_from:
   - '/connections/destinations/catalog/actions-sprig-web'
+  - '/connections/destinations/catalog/vendor-sprig'
 id: 61d8c74d174a9acd0e138b31
+versions:
+  - name: Sprig Cloud
+    link: /docs/connections/destinations/catalog/sprig-cloud
 ---
 <!-- In the section above, edit the `title` field. For example, Slack (Actions) Destination -->
 
@@ -16,13 +20,6 @@ id: 61d8c74d174a9acd0e138b31
 Sprig maintains this destination. For any issues with the destination, consult [Sprig's documentation](https://docs.sprig.com/docs/segment-web) or contact [[email protected]](mailto:[email protected]).
 
 
-<!-- In the section below, add your destination name where indicated. If you have a classic version of the destination, ensure that its documentation is linked as well. If you don't have a classic version of the destination, remove the second and third sentences. -->
-
-> success ""
-> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Sprig Segment destination. There's also a page about the [non-Actions Sprig Cloud (formerly UserLeap) destination](/docs/connections/destinations/catalog/userleap/). Both of these destinations receive data from Segment.
-
-<!-- In the section below, explain the value of this actions-based destination over the classic version, if applicable. If you don't have a classic version of the destination, remove this section. -->
-
 ## Benefits of Sprig (Actions) vs Sprig Classic
 
 Sprig (Actions) provides the following benefits over the classic Sprig destination: