segmentio
diff --git a/‎.github/release.yml
+1-1 b/‎.github/release.yml
+1-1
diff --git a/‎src/_includes/content/actions-classic.md
+18 b/‎src/_includes/content/actions-classic.md
+18
diff --git a/‎src/_layouts/destination.html
+5-1 b/‎src/_layouts/destination.html
+5-1
diff --git a/‎src/connections/destinations/catalog/actions-adobe-target-cloud/index.md
+12-10 b/‎src/connections/destinations/catalog/actions-adobe-target-cloud/index.md
+12-10
diff --git a/‎src/connections/destinations/catalog/actions-adobe-target-web/index.md
+22-20 b/‎src/connections/destinations/catalog/actions-adobe-target-web/index.md
+22-20
diff --git a/‎src/connections/destinations/catalog/actions-amplitude/index.md
+5 b/‎src/connections/destinations/catalog/actions-amplitude/index.md
+5
diff --git a/‎src/connections/destinations/catalog/actions-close/index.md
+40 b/‎src/connections/destinations/catalog/actions-close/index.md
+40
@@ -17,7 +17,7 @@ changelog:
         - new-integration
     - title: Improvements
       labels:
-        - enhancement
+        - content-update
     - title: Fixes
       labels:
         - fixed-content
 
@@ -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>
@@ -10,7 +10,11 @@
   {{destination-dossier | markdownify}}
 
 {% endif %}
-  
+
+{% if page.versions %}
+{% include content/actions-classic.md %}
+
+{% endif %}
 
 
 {% if page.maintenance == true %}
 
@@ -2,8 +2,7 @@
 title: Adobe Target Cloud Mode Destination
 hide-boilerplate: true
 hide-dossier: false
-hidden: true
-beta: true
+strat: adobe
 id: 61aa712b857e8c85c3b5a849
 ---
 Adobe Target is the A/B testing and personalization component of Adobe Experience Cloud. Segment’s Adobe Target integration enables customers to send data from Segment to Adobe Target to create and update user profiles. You can leverage these profiles in Adobe Target to construct audiences and personalize onsite visitor experiences.
@@ -12,8 +11,11 @@ Segment offers two destinations for Adobe Target:
 - [Adobe Target Web](/docs/connections/destinations/catalog/actions-adobe-target-web/)
 - [Adobe Target Cloud Mode](/docs/connections/destinations/catalog/actions-adobe-target-cloud/)
 
-> success ""
-> **Good to know**: This page is about Segment's Adobe Target Cloud Mode destination. There's also a page about Segment's [Adobe Target Web destination](/docs/connections/destinations/catalog/actions-adobe-target-web/). **In order to use Adobe Target Cloud Mode, you must have a parallel web integration with Adobe Target as profiles can only be created by the Adobe Target `at.js` web script.**
+> info ""
+> The Adobe Target Cloud Mode destination is in beta and is in active development. Some functionality may change before it becomes generally available.
+
+> success "Good to know"
+> This page is about Segment's Adobe Target Cloud Mode destination. There's also a page about Segment's [Adobe Target Web destination](/docs/connections/destinations/catalog/actions-adobe-target-web/). **In order to use Adobe Target Cloud Mode, you must have a parallel web integration with Adobe Target as profiles can only be created by the Adobe Target `at.js` web script.**
 
 ## Getting started
 
@@ -53,10 +55,10 @@ This scenario assumes that your users authenticate and have a `userId` upon arri
 If the same known user visits on a different device, assuming they authenticate immediately, they will have the same `userId` and therefore the same `mbox3rdPartyId`. This means you can target known users across devices.
 
 #### Scenario 3. Anonymous user becomes a known user.
-When an anonymous user first arrives on your website, one Adobe Target profile will be created and the `mbox3rdPartyId` will be equal to the Segment `anonymousId`. However, once the user is identified, they will be assigned a new `mbox3rdPartyId` equal to the Segment `userId`. There will be two profiles in Adobe Target; both will be available for targeting.
+When an anonymous user arrives on your website, one Adobe Target profile will be created and the `mbox3rdPartyId` will be equal to the Segment `anonymousId`. However, once the user is identified, they will be assigned a new `mbox3rdPartyId` equal to the Segment `userId`. There will be two profiles in Adobe Target; both will be available for targeting.
 
 ### How to use Adobe Target with Personas
-Adobe Target Cloud Mode operates as an [Event Destination](/docs/personas/using-personas-data/#personas-destination-types-event-vs-list/). This means Personas sends computed traits and audiences as traits in `identify` calls or properties in `track`  calls. Please see [this example](/docs/personas/using-personas-data/#audience-generated-events/) of the payload Personas would send to Adobe Target.
+Adobe Target Cloud Mode operates as an [Event Destination](/docs/personas/using-personas-data/#personas-destination-types-event-vs-list). This means Personas sends computed traits and audiences as traits in `identify` calls or properties in `track`  calls. Please see [this example](/docs/personas/using-personas-data/#what-do-the-payloads-look-like-for-personas-data) of the payload Personas would send to Adobe Target.
 
 When you connect Adobe Target Cloud Mode to a Personas space, you will need to set up a mapping for Update Profile. Within the Update Profile mapping, please ensure you have something mapped to Profile Attributes. If you plan to send multiple Personas computed traits and/or audiences to Adobe Target, you can click **Edit Object** and set Profile Attributes to the entire `traits` object. This ensures any audience Personas generates sends to Adobe Target.
 
@@ -68,15 +70,15 @@ You can use Profile Attributes in the Adobe Target Audience builder to construct
 ## Viewing Segment data in Adobe Target
 To view and use your Segment data in Adobe Target, navigate to **Adobe Target > Audiences > Create Audience > Add Rule**.
 
-- Profile Attributes appear under the **Visitor Profile** attributes.
+- Profile Attributes appear under **Visitor Profile** attributes.
 - Page Parameters appear under **Custom** attributes. Fields have `page.` prepended to the key.
 
-Audiences can then be used in Adobe Target Activities, such as A/B Testing and Experience Targeting. Please note that while Standard and Premium Adobe Target packages allow access to the SDK and API, certain personalization functionality may only be available with Adobe Target Premium. 
+Adobe Target Audiences can be used in Activities, such as A/B Testing and Experience Targeting. Please note that while Standard and Premium Adobe Target packages allow access to the SDK and API, certain personalization functionality may only be available with Adobe Target Premium. 
 
 ## FAQ
 ### Why am I getting a `Profile Not Found` error?
-The Adobe Target API can only be used for profile updates. Profiles must be created on the web first, either using Segment’s [Adobe Target Web destination](/docs/connections/destinations/catalog/actions-adobe-target-web/) or a native implementation of `at.js`. Please ensure you are creating profiles via `at.js` first.
+The Adobe Target API can only be used for profile updates. You must first create profiles on the web by using either Segment’s [Adobe Target Web destination](/docs/connections/destinations/catalog/actions-adobe-target-web/) or a native implementation of `at.js`. Please ensure you create profiles on the web first.
 
-Segment’s Adobe Target Web destination sends data in realtime, but it may take up to 1-hour for a user to be available via the Adobe Target API. This means you may see delivery errors for `Profile Not Found` in Adobe Target Cloud until the profile is available for API updates.
+Segment’s Adobe Target Web destination sends data in realtime, but it may take up to 1-hour for a user to be available via the Adobe Target API. This means you may see delivery errors for `Profile Not Found` in Adobe Target Cloud Mode until the profile is available for API updates.
 
 In addition, Adobe Target visitor profiles expire after 14 days. [Profile lifetime](https://experienceleague.adobe.com/docs/target/using/audiences/visitor-profiles/visitor-profile-lifetime.html){:target="_blank"} could be another reason a profile is not found.
@@ -2,66 +2,68 @@
 title: Adobe Target Web Destination
 hide-boilerplate: true
 hide-dossier: false
-hidden: true
-beta: true
+strat: adobe
 id: 61fc2ffcc76fb3e73d85c89d
 ---
-Adobe Target is a personalization solution that makes it easy to identify your best content through tests that are easy to execute. So you can deliver the right experience to the right customer. When you have Segment installed, you can make efficient use of your existing tracking implementation by using Segment to fulfill your data collection needs across all your tools that integrate with Segment, including Adobe Target.
+Adobe Target is the A/B testing and personalization component of Adobe Experience Cloud. Segment’s Adobe Target integration enables customers to send data from Segment to Adobe Target to create and update user profiles. You can leverage these profiles in Adobe Target to construct audiences and personalize onsite visitor experiences.
 
 Segment offers two destinations for Adobe Target:
 - [Adobe Target Web](/docs/connections/destinations/catalog/actions-adobe-target-web/)
 - [Adobe Target Cloud Mode](/docs/connections/destinations/catalog/actions-adobe-target-cloud/)
 
-> success ""
-> **Good to know**: This page is about Segment's Adobe Target Web destination. There's also a page about Segment's [Adobe Target Cloud Mode destination](/docs/connections/destinations/catalog/actions-adobe-target-cloud/).
+> info ""
+> The Adobe Target Web destination is in beta and is in active development. Some functionality may change before it becomes generally available.
+
+> success "Good to know"
+> This page is about Segment's Adobe Target Web destination. There's also a page about Segment's [Adobe Target Cloud Mode destination](/docs/connections/destinations/catalog/actions-adobe-target-cloud/).
 
 ## Getting started
 
 The Adobe Target Web destination loads Adobe's `at.js` script for you in order to upsert user profiles, trigger views and track events. 
 
 1. From the Segment web app, click **Catalog**, then click **Destinations**.
-2. Search for "Adobe Target Web" in the Destinations Catalog, and select the destination.
+2. Search for **Adobe Target Web** in the Destinations Catalog, and select the destination.
 3. Click **Configure Adobe Target Web** in the top-right corner of the screen.
 4. Select the web source that will send data to Adobe Target Web and follow the steps to name your destination. The web source chosen must use [Analytics.js 2.0](/docs/connections/sources/catalog/libraries/website/javascript/).
 5. On the **Settings** tab, input your Adobe Target destination settings.
 6. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customizing-mappings).
-7. Enable the Destination and configured Mappings.
+7. Enable the destination and configured mappings.
 
 {% include components/actions-fields.html %}
 
 ## Relationship between Adobe Target Web and Adobe Target Cloud Mode
 
 Adobe Target is unique because you must have a web integration with Adobe Target in order to utilize the Target server-side API for profile updates. This is because Adobe Target only allows creation of user profiles via client-side web. 
 
-To support this, we provide an Adobe Target Web destination for user profile creation, updates, and page/event tracking and an [Adobe Target Cloud Mode destination](/docs/connections/destinations/catalog/actions-adobe-target-cloud/) for additional profile updates. The cloud mode destination is especially useful if you would like to send Personas data to Adobe Target as profile parameters.
+To support this, Segment provides an Adobe Target Web destination for user profile creation, updates, and page/event tracking and an [Adobe Target Cloud Mode destination](/docs/connections/destinations/catalog/actions-adobe-target-cloud/) for additional profile updates. The cloud mode destination is useful if you would like to send Personas data to Adobe Target as profile parameters.
 
 ### How does it work?
-Adobe Target’s `at.js` script identifies each visitor uniquely through a `PCID`, which is auto-generated in the visitor’s cookies. Since we do not expect you to pass the `PCID` to Segment, Segment will update profiles using the `mbox3rdPartyId`. 
+Adobe Target’s `at.js` script identifies each visitor uniquely through a `PCID`, which is auto-generated in the visitor’s cookies. Since Segment doesn't expect you to include the `PCID` on your Segment events, Segment updates profiles using the `mbox3rdPartyId` instead.
 
-Segment recommends setting the `mbox3rdPartyId` to `userId` (falling back on `anonymousId`) and we set this as the default for your implementation. This allows for a common identifier that can be used to tie server-side data back to the original profile that was created on the web.
+Segment recommends setting the `mbox3rdPartyId` to `userId` (falling back on `anonymousId`) and sets this as the default for your implementation. This allows for a common identifier that can be used to tie server-side data back to the original profile that was created on the web.
 
-Depending on your users’ typical journey, a few scenarios can occur when using web and cloud mode together.
+Depending on your user's typical journey, a few scenarios can occur when using web and cloud mode together.
 
-#### Scenario 1. Anonymous user always, never becomes known.
-When the user arrives on your website, one Adobe Target profile will be created and the `mbox3rdPartyId` will be equal to the Segment `anonymousId`.
+#### Scenario 1. Anonymous user never becomes known.
+When an anonymous user arrives on your website, one Adobe Target profile will be created and the `mbox3rdPartyId` will be equal to the Segment `anonymousId`.
 
-If the same user visits on a different device, they will have a new `anonymousId` and therefore a different `mbox3rdPartyId`, and a separate Adobe Target profile will be created. This is in line with how Adobe’s `PCID` behavior works too.
+If the same anonymous user visits on a different device, they will have a new `anonymousId` and therefore a different `mbox3rdPartyId`, and a separate Adobe Target profile will be created. This is in line with how Adobe’s `PCID` behavior works too.
 
-#### Scenario 2. Known user always, from first point of contact.
+#### Scenario 2. The user is known from the first point of contact.
 This scenario assumes that your users authenticate and have a `userId` upon arriving on your website. When the user arrives on your website, one Adobe Target profile will be created and the `mbox3rdPartyId` will be equal to the Segment `userId`.
 
 If the same known user visits on a different device, assuming they authenticate immediately, they will have the same `userId` and therefore the same `mbox3rdPartyId`. This means you can target known users across devices.
 
 #### Scenario 3. Anonymous user becomes a known user.
-When the user first arrives on your website, one Adobe Target profile will be created and the `mbox3rdPartyId` will be equal to the Segment `anonymousId`. However, once the user is identified, they will be assigned a new `mbox3rdPartyId` equal to the Segment `userId`. There will be two profiles in Adobe Target; both will be available for targeting.
+When an anonymous user arrives on your website, one Adobe Target profile will be created and the `mbox3rdPartyId` will be equal to the Segment `anonymousId`. However, once the user is identified, they will be assigned a new `mbox3rdPartyId` equal to the Segment `userId`. There will be two profiles in Adobe Target; both will be available for targeting.
 
 ### How to use Adobe Target with Personas
-For information on how to use Adobe Target with Personas, please see [Adobe Target Cloud Mode destination](/docs/connections/destinations/catalog/actions-adobe-target-cloud/).
+For information on how to use Adobe Target with Personas, please see [Adobe Target Cloud Mode destination](/docs/connections/destinations/catalog/actions-adobe-target-cloud/#how-to-use-adobe-target-with-personas).
 
 ## Viewing Segment data in Adobe Target
 To view and use your Segment data in Adobe Target, navigate to **Adobe Target > Audiences > Create Audience > Add Rule**.
 
-- Profile Attributes will appear under the “Visitor Profile” attributes.
-- Page Parameters will appear under “Custom” attributes. Fields will have `page.` prepended to the key.
+- Profile Attributes appear under **Visitor Profile** attributes.
+- Page Parameters appear under **Custom** attributes. Fields have `page.` prepended to the key.
 
-Audiences can then be used in Adobe Target **Activities**, such as A/B Testing and Experience Targeting. Please note that while Standard and Premium Adobe Target packages allow access to the SDK and API, certain personalization functionality may only be available with Adobe Target Premium. 
+Adobe Target Audiences can be used in Activities, such as A/B Testing and Experience Targeting. Please note that while Standard and Premium Adobe Target packages allow access to the SDK and API, certain personalization functionality may only be available with Adobe Target Premium. 
@@ -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" %}
 
 
@@ -0,0 +1,40 @@
+---
+# The end name should be similar to `Slack  Destination`
+title: Close (Actions) Destination
+hide-boilerplate: true
+hide-dossier: true
+hidden: true
+---
+
+<!-- This template is meant for Actions-based destinations that do not have an existing Classic or non-Actions-based version. For Actions Destinations that are a new version of a classic destination, see the doc-template-update.md template. -->
+
+{% include content/plan-grid.md name="actions" %}
+
+<!-- Include a brief description of the destination here, along with a link to your website. -->
+[Close](https://close.com/){:target="_blank"} is the inside sales CRM of choice for startups and small and midsize businesses (SMBs.)
+
+
+<!-- This include describes the requirement of A.js 2.0 or higher for Actions compatibility, and is required if your destination has a web component. -->
+
+{% include content/ajs-upgrade.md %}
+
+<!-- The section below explains how to enable and configure the destination. Include any configuration steps not captured below. For example, obtaining an API key from your platform and any configuration steps required to connect to the destination. -->
+
+## Getting started
+
+1. Go to your Close app and select the Organization you want to use.
+2. Click **Settings** in the bottom left, then click **API Keys** in the left menu. Create a new API Key.
+3. From the Segment web app, click **Catalog**, then click **Destinations**.
+4. Find the Destinations Actions item in the left navigation, and click it.
+5. Click the “Close” item to select it and click Configure.
+6. Choose which of your sources to connect the destination to. (You can connect more sources to the destination later.)
+
+<!-- The line below renders a table of connection settings (if applicable), Pre-built Mappings, and available actions. -->
+
+{% include components/actions-fields.html %}
+
+<!--
+Additional Context
+
+Include additional information that you think will be useful to the user here. For information that is specific to an individual mapping, please add that as a comment so that the Segment docs team can include it in the auto-generated content for that mapping.
+-->