link fixes - 1flow > adobe analytics

Author: forstisabella

src/connections/destinations/catalog/1flow-analytics/index.md

@@ -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

src/connections/destinations/catalog/1flow/index.md

@@ -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

src/connections/destinations/catalog/2mee/index.md

@@ -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.
 

src/connections/destinations/catalog/ab-smartly/index.md

@@ -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.

src/connections/destinations/catalog/actions-algolia-insights/index.md

@@ -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
 

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

@@ -51,12 +51,12 @@ To manually add the Log Purchases Action:
 
 ### Connection Modes for Amplitude (Actions) destination
 
-The Amplitude (actions) destination does not offer a device-mode connection mode. If you're using one of Segment's new libraries ([Analytics.js 2.0](/docs/connections/sources/catalog/libraries/website/javascript/), [Swift](https://github.com/segmentio/analytics-swift) or [Kotlin](https://github.com/segmentio/analytics-kotlin)) with the Actions-framework version of the destination, you do not need the device-mode connection.
+The Amplitude (actions) destination does not offer a device-mode connection mode. If you're using one of Segment's new libraries ([Analytics.js 2.0](/docs/connections/sources/catalog/libraries/website/javascript/), [Swift](https://github.com/segmentio/analytics-swift){:target="_blank”} or [Kotlin](https://github.com/segmentio/analytics-kotlin){:target="_blank”}) with the Actions-framework version of the destination, you do not need the device-mode connection.
 
 
 Most previous deployments of the Amplitude Segment destination used the device-mode connection to use the `session_id` tracking feature. The new Actions-framework Amplitude destination, includes session ID tracking by default. When connected to the Analytics.js 2.0 source, Segment automatically loads a plugin on your website for session tracking and enrichment as an alternative to the Amplitude SDK. This means you don't need to bundle any software to run on the user's device, or write any code. It also means that you can use more of the Segment platform features on data going to Amplitude, such as Protocols filtering and transformations, and Profiles Identity Resolution.
 
-Session tracking is available with Segment's new libraries: [Analytics.js 2.0](/docs/connections/sources/catalog/libraries/website/javascript/), [Swift](https://github.com/segmentio/analytics-swift) or [Kotlin](https://github.com/segmentio/analytics-kotlin)
+Session tracking is available with Segment's new libraries: [Analytics.js 2.0](/docs/connections/sources/catalog/libraries/website/javascript/), [Swift](https://github.com/segmentio/analytics-swift){:target="_blank”} or [Kotlin](https://github.com/segmentio/analytics-kotlin){:target="_blank”}.
 
 
 ### Device ID Mappings
@@ -72,28 +72,28 @@ The session ID Segment passes to Amplitude stores locally in a key-value pair. V
 
 ### Enable Amplitude session tracking for Swift
 
-To enable session tracking in Amplitude when using the [Segment Swift library](https://github.com/segmentio/analytics-swift):
+To enable session tracking in Amplitude when using the [Segment Swift library](https://github.com/segmentio/analytics-swift){:target="_blank”}:
 1. Enable `trackApplicationLifecycleEvents` in your configuration.
-2. Add the [Amplitude Session plugin](https://github.com/segment-integrations/analytics-swift-amplitude/blob/main/Sources/SegmentAmplitude/AmplitudeSession.swift) to your project.
-3. Initialize the plugin ([example](https://github.com/segmentio/analytics-swift/blob/main/Examples/apps/DestinationsExample/DestinationsExample/AppDelegate.swift))
+2. Add the [Amplitude Session plugin](https://github.com/segment-integrations/analytics-swift-amplitude/blob/main/Sources/SegmentAmplitude/AmplitudeSession.swift){:target="_blank”} to your project.
+3. Initialize the plugin ([example](https://github.com/segmentio/analytics-swift/blob/main/Examples/apps/DestinationsExample/DestinationsExample/AppDelegate.swift){:target="_blank”})
    ```swift
    analytics?.add(plugin: AmplitudeSession(name: "Amplitude"))
    ```
 
 ### Enable Amplitude session tracking for Kotlin
 
-To enable session tracking in Amplitude when using the [Segment Kotlin library](https://github.com/segmentio/analytics-kotlin):
+To enable session tracking in Amplitude when using the [Segment Kotlin library](https://github.com/segmentio/analytics-kotlin){:target="_blank”}:
 1. Enable `trackApplicationLifecycleEvents` in your configuration.
-2. Add the [Amplitude Session plugin](https://github.com/segment-integrations/analytics-kotlin-amplitude/blob/main/lib/src/main/java/com/segment/analytics/kotlin/destinations/amplitude/AmplitudeSession.kt) to your project.
+2. Add the [Amplitude Session plugin](https://github.com/segment-integrations/analytics-kotlin-amplitude/blob/main/lib/src/main/java/com/segment/analytics/kotlin/destinations/amplitude/AmplitudeSession.kt){:target="_blank”} to your project.
 2. Initialize the plugin
    ```kotlin
    analytics.add(AmplitudeSession())
    ```
 
 ### Enable Amplitude session tracking for iOS
 
-To enable session tracking in Amplitude when using the [Segment iOS library](https://github.com/segmentio/analytics-ios):
-1. Add the [Amplitude Session middleware](https://github.com/segment-integrations/analytics-ios-integration-amplitude/blob/amplitude-session/Pod/Classes/SEGAmplitudeSession.m) to your project.
+To enable session tracking in Amplitude when using the [Segment iOS library](https://github.com/segmentio/analytics-ios){:target="_blank”}:
+1. Add the [Amplitude Session middleware](https://github.com/segment-integrations/analytics-ios-integration-amplitude/blob/amplitude-session/Pod/Classes/SEGAmplitudeSession.m){:target="_blank”} to your project.
 2. Add the middleware & enable `trackApplicationLifecycleEvents` in your configuration:
    ```objective-c
    	NSString *const SEGMENT_WRITE_KEY = @" ... ";
@@ -105,8 +105,8 @@ To enable session tracking in Amplitude when using the [Segment iOS library](htt
 
 ### Enable Amplitude session tracking for Android
 
-To enable session tracking in Amplitude when using the [Segment Android library](https://github.com/segmentio/analytics-android):
-1. Add the [Amplitude Session middleware](https://github.com/segment-integrations/analytics-android-integration-amplitude/blob/master/src/main/java/com/segment/analytics/android/integrations/amplitude/AmplitudeSessionId.java) to your project.
+To enable session tracking in Amplitude when using the [Segment Android library](https://github.com/segmentio/analytics-android){:target="_blank”}:
+1. Add the [Amplitude Session middleware](https://github.com/segment-integrations/analytics-android-integration-amplitude/blob/master/src/main/java/com/segment/analytics/android/integrations/amplitude/AmplitudeSessionId.java){:target="_blank”} to your project.
 	```gradle
 	implementation 'com.segment.analytics.android.integrations:amplitude:3.1.0'
 	```
@@ -171,7 +171,7 @@ Property names should be `camelCase` for Android implementations, and `snake_cas
 
 If `true`, the destination sends events to Amplitude's `batch` endpoint rather than the `httpapi` endpoint. Because Amplitude's `batch` endpoint throttles traffic less restrictively than the Amplitude `httpapi` endpoint, enabling this setting can help to reduce 429 errors (throttling errors) from Amplitude.
 
-Amplitude's `batch` endpoint throttles data when the rate of events sharing the same `user_id` or `device_id` exceeds an average of 1,000/second over a 30-second period. See the Amplitude documentation for more about [429 errors and throttling in Amplitude](https://developers.amplitude.com/#429s-in-depth).
+Amplitude's `batch` endpoint throttles data when the rate of events sharing the same `user_id` or `device_id` exceeds an average of 1,000/second over a 30-second period. See the Amplitude documentation for more about [429 errors and throttling in Amplitude](https://developers.amplitude.com/#429s-in-depth){:target="_blank”}.
 {% endcapture %}
 
 

src/connections/destinations/catalog/actions-blend-ai/index.md

@@ -8,8 +8,7 @@ id: 64244158b33d1380a79dc85c
 
 [Blend-AI](https://blnd.ai/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} identifies the most valuable product interaction in your product data and cross references it with new incoming leads.
 
-Blend-AI maintains this destination. For any issues with the destination, [contact their Support 
-team](mailto:[email protected]).
+Blend-AI maintains this destination. For any issues with the destination, [contact their Support team](mailto:[email protected]).
 
 {% include content/ajs-upgrade.md %}
 

src/connections/destinations/catalog/actions-braze-cloud/index.md

@@ -6,7 +6,7 @@ hidden: true
 ---
 {% include content/plan-grid.md name="actions" %}
 
-[Braze](https://www.braze.com/), formerly Appboy, is an engagement platform that empowers growth by helping marketing teams to build customer loyalty through mobile, omni-channel customer experiences.
+[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!

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

@@ -7,7 +7,7 @@ hide-dossier: true
 
 {% include content/plan-grid.md name="actions" %}
 
-[Cordial](https://cordial.com/) is an all-in-one marketing platform that enables brands to collect, normalize, and activate real-time data from anywhere in your technology stack to create and deliver tailored messages that flex and adapt to changing customer signals.
+[Cordial](https://cordial.com/){:target="_blank”} is an all-in-one marketing platform that enables brands to collect, normalize, and activate real-time data from anywhere in your technology stack to create and deliver tailored messages that flex and adapt to changing customer signals.
 
 > info "Good to know"
 > This page is about the [Actions-framework](/docs/connections/destinations/actions/) Cordial Segment destination. There's also a page about the [non-Actions Cordial destination](/docs/connections/destinations/catalog/cordialio/). Both of these destinations receive data from Segment.

src/connections/destinations/catalog/actions-friendbuy-cloud/index.md

@@ -17,10 +17,10 @@ If you're using Segment with a Friendbuy referral program you probably want to u
 
 The Friendbuy cloud mode destination sends information about your customers and their actions to Friendbuy. It supports the following [Friendbuy MAPI events](https://developers.friendbuy.com/#tracking-events){:target='_blank'}.
 
-- **Track Customer**: Converts Segment [Identify](/docs/connections/spec/identify/) calls to Friendbuy [*track customer* MAPI calls](https://developers.friendbuy.com/#tracking-customer-details). Use this to add your customer ID and other customer data to the information that Friendbuy has about the customer.
-- **Track Purchase**: Converts Segment [Order Completed](/docs/connections/spec/ecommerce/v2/#order-completed) calls to Friendbuy [*track purchase* MAPI calls](https://developers.friendbuy.com/#tracking-a-purchase). Use this to send purchase data to Friendbuy and reward advocates based on their friends' purchases.
-- **Track Sign-Up**: Converts Segment [Signed Up](/docs/connections/spec/b2b-saas/#signed-up) calls to Friendbuy [*track sign_up* MAPI calls](https://developers.friendbuy.com/#tracking-a-signup). Use this to reward customers for account creation and other sign-up actions.
-- **Track Custom Event**: Converts an arbitrary Segment [`analytics.track`](/docs/connections/sources/catalog/libraries/website/javascript/#track) call with an event name and properties of your choosing to a Friendbuy [track custom event MAPI call](https://developers.friendbuy.com/#tracking-a-custom-event). Use this to reward your customers for actions other than purchases or sign-ups.
+- **Track Customer**: Converts Segment [Identify](/docs/connections/spec/identify/) calls to Friendbuy [*track customer* MAPI calls](https://developers.friendbuy.com/#tracking-customer-details){:target="_blank”}. Use this to add your customer ID and other customer data to the information that Friendbuy has about the customer.
+- **Track Purchase**: Converts Segment [Order Completed](/docs/connections/spec/ecommerce/v2/#order-completed) calls to Friendbuy [*track purchase* MAPI calls](https://developers.friendbuy.com/#tracking-a-purchase){:target="_blank”}. Use this to send purchase data to Friendbuy and reward advocates based on their friends' purchases.
+- **Track Sign-Up**: Converts Segment [Signed Up](/docs/connections/spec/b2b-saas/#signed-up) calls to Friendbuy [*track sign_up* MAPI calls](https://developers.friendbuy.com/#tracking-a-signup){:target="_blank”}. Use this to reward customers for account creation and other sign-up actions.
+- **Track Custom Event**: Converts an arbitrary Segment [`analytics.track`](/docs/connections/sources/catalog/libraries/website/javascript/#track) call with an event name and properties of your choosing to a Friendbuy [track custom event MAPI call](https://developers.friendbuy.com/#tracking-a-custom-event){:target="_blank”}. Use this to reward your customers for actions other than purchases or sign-ups.
 
 ## Benefits of Friendbuy Cloud Mode (Actions) vs Friendbuy Classic