amplitude > mixpanel

Author: forstisabella

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

@@ -16,7 +16,7 @@ Segment's Amplitude destination code is open source and available on GitHub. You
 In addition to Segment's Amplitude documentation, Amplitude provides a [Segment integration guide](https://docs.developers.amplitude.com/data/sources/segment/){:target="_blank"}, as well.
 
 > note ""
-> To delete users based on GDPR regulations, you must include a secret key in the **Secret Key** setting of every Amplitude destination. You can find your Secret Key on the [General Settings](https://help.amplitude.com/hc/en-us/articles/235649848-Settings#general) of your Amplitude project.
+> To delete users based on GDPR regulations, you must include a secret key in the **Secret Key** setting of every Amplitude destination. You can find your Secret Key on the [General Settings](https://help.amplitude.com/hc/en-us/articles/235649848-Settings#general){:target="_blank"}  of your Amplitude project.
 
 
 
@@ -85,7 +85,7 @@ If you use Analytics.js (in either [device- or cloud-mode](/docs/connections/des
 
 Before you choose a setting, read about the Amplitude event type volume considerations.
 
-When you use the **Track Named Pages** or **Track Categorized Pages** settings, Segment sends a Page or Screen call that includes the name or category. This option stores the page and screen name as a top-level event type. However, Amplitude [limits the number of distinct event types per project](https://help.amplitude.com/hc/en-us/articles/115002923888-Limits#h_8d90ca72-bf91-4161-88b2-01b5448b0859). Each unique Page and Screen name, Page and Screen category, and Track event counts towards the event type limit. Anything past the instrumentation limit is not visualized in Amplitude.
+When you use the **Track Named Pages** or **Track Categorized Pages** settings, Segment sends a Page or Screen call that includes the name or category. This option stores the page and screen name as a top-level event type. However, Amplitude [limits the number of distinct event types per project](https://help.amplitude.com/hc/en-us/articles/115002923888-Limits#h_8d90ca72-bf91-4161-88b2-01b5448b0859){:target="_blank"}. Each unique Page and Screen name, Page and Screen category, and Track event counts towards the event type limit. Anything past the instrumentation limit is not visualized in Amplitude.
 
 When you use the **Track All Pages** setting, Segment sends a `Loaded a Page` event type to Amplitude. When you use the generic event name, it is applied to all Page and Screen calls, so you don't hit the event type limit in your project in Amplitude. The page or screen name is still available as an attribute of the `Loaded a Page` event, and you can query it as an event property. The `Loaded a Page` event is counted as one event type, and Amplitude does not place any limits on the number of unique event property values in Amplitude.
 
@@ -504,7 +504,7 @@ analytics.alias({
 
 ### sessionId
 
-[Segment doesn't have a concept for a session](https://segment.com/blog/facts-vs-stories-why-segment-has-no-sessions-api/).
+[Segment doesn't have a concept for a session](https://segment.com/blog/facts-vs-stories-why-segment-has-no-sessions-api/){:target="_blank"}.
 
 Device-mode calls to Amplitude include session information because Segment bundles Amplitude's SDK. To set up the same `sessionId` for cloud-mode calls to Amplitude, you must explicitly set the [`session_id`](https://developers.amplitude.com/docs/http-api-v2#optional-keyst){:target="_blank"} as an integration-specific option, as in the example below.
 

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

@@ -26,7 +26,7 @@ Segment's Appsflyer destination code is open source and available on GitHub. You
 
 #### Additional device-mode set up for iOS 14 support
 
-Segment updated the AppsFlyer iOS SDK to use version `6.0 beta` to prepare for tracking changes in iOS 14. The SDK beta version is compatible with the beta version of iOS 14 released by Apple, and supports both AppsFlyer's aggregate attribution, and Apple's `AppTrackingTransparency` framework, and more. See [the AppsFlyer blog post](https://www.appsflyer.com/blog/privacy-centric-attribution-ios14/) about AppsFlyer's new privacy-centric attribution model.
+Segment updated the AppsFlyer iOS SDK to use version `6.0 beta` to prepare for tracking changes in iOS 14. The SDK beta version is compatible with the beta version of iOS 14 released by Apple, and supports both AppsFlyer's aggregate attribution, and Apple's `AppTrackingTransparency` framework, and more. See [the AppsFlyer blog post](https://www.appsflyer.com/blog/privacy-centric-attribution-ios14/){:target="_blank"} about AppsFlyer's new privacy-centric attribution model.
 
 To use the latest AppsFlyer SDK to collect IDFAs, do the following:
 
@@ -66,7 +66,7 @@ To prevent this, you can enable the new **Fallback to send IDFV when advertising
 
 ### Server
 
-AppsFlyer offers an **augmentative** server-side [HTTP API](https://support.appsflyer.com/hc/en-us/articles/207034486-Server-to-Server-In-App-Events-API-HTTP-API-) intended for use along side the AppsFlyer mobile SDK. Use the cloud-mode destination _with_ the mobile SDK to link out-of-app events (such as website or offline purchases) with attributed users and devices.
+AppsFlyer offers an **augmentative** server-side [HTTP API](https://support.appsflyer.com/hc/en-us/articles/207034486-Server-to-Server-In-App-Events-API-HTTP-API-){:target="_blank"} intended for use along side the AppsFlyer mobile SDK. Use the cloud-mode destination _with_ the mobile SDK to link out-of-app events (such as website or offline purchases) with attributed users and devices.
 
 **Important**: The cloud-mode destination is not meant to replace the device-mode destination, and you should not use the cloud-mode destination by itself. AppsFlyer requires that you bundle the mobile SDK to correctly attribute user actions. Remember that if you pass in an `appsFlyerId` on cloud-mode calls, you cannot prevent events from sending to AppsFlyer from the Segment app.
 
@@ -109,7 +109,7 @@ AppsFlyer requires the following properties for this attribution:
 **AppsFlyer ID**
 
 Send the **AppsFlyer ID** with each event at `integrations.AppsFlyer.appsFlyerId`, see example below.
-This identifier is unique to each device and can be [retrieved using the AppsFlyer SDK](https://support.appsflyer.com/hc/en-us/articles/207034486-Server-to-Server-In-App-Events-API-HTTP-API-). It is a good idea to store this value in an external database where it may be easily accessible by a server or website environments.
+This identifier is unique to each device and can be [retrieved using the AppsFlyer SDK](https://support.appsflyer.com/hc/en-us/articles/207034486-Server-to-Server-In-App-Events-API-HTTP-API-){:target="_blank"}. It is a good idea to store this value in an external database where it may be easily accessible by a server or website environments.
 
 **Device Type**
 
@@ -162,7 +162,7 @@ If you track events server-side, AppsFlyer can still send attribution postbacks,
 2. Enter the configuration options and input your Segment Write Key. 
 Once enabled, successfully attributed app installs begin showing up as `Install Attributed` events similar to the client side behavior documented above.
 
-If you are sending in the attribution data yourself, for iOS be sure the following properties are sent in within the campaign object on the `Install Attributed` or `Application Opened` event so Appsflyer can correctly attribute it as an Apple Search Ad event. These values should be returned by the [Apple Search Ads API](https://searchads.apple.com/help/reporting/0028-apple-ads-attribution-api):
+If you are sending in the attribution data yourself, for iOS be sure the following properties are sent in within the campaign object on the `Install Attributed` or `Application Opened` event so Appsflyer can correctly attribute it as an Apple Search Ad event. These values should be returned by the [Apple Search Ads API](https://searchads.apple.com/help/reporting/0028-apple-ads-attribution-api){:target="_blank"}:
 
 ```
 "campaign": {
@@ -222,4 +222,4 @@ The destination does not automatically support out-of-the-box deeplinking (you n
 
 Therefore, you can use AppsFlyer's OneLink integration which is a single, smart, tracking link that can be used to track on both Android and iOS. OneLink tracking links can launch your app when it is already installed instead of redirecting the user to the app store.
 
-For more details, review the [AppsFlyer OneLink set up Guide](https://support.appsflyer.com/hc/en-us/articles/207032246-OneLink-Setup-Guide). More information is available in the AppsFlyer SDK Integration Guides ([iOS](https://support.appsflyer.com/hc/en-us/articles/207032066-AppsFlyer-SDK-Integration-iOS), [Android](https://support.appsflyer.com/hc/en-us/articles/207032126-AppsFlyer-SDK-Integration-Android)) and Segment's mobile FAQs ([iOS](/docs/connections/sources/catalog/libraries/mobile/ios/#faq), [Android](/docs/connections/sources/catalog/libraries/mobile/android/#faq)).
+For more details, review the [AppsFlyer OneLink set up Guide](https://support.appsflyer.com/hc/en-us/articles/207032246-OneLink-Setup-Guide){:target="_blank"}. More information is available in the AppsFlyer SDK Integration Guides ([iOS](https://support.appsflyer.com/hc/en-us/articles/207032066-AppsFlyer-SDK-Integration-iOS{:target="_blank"}), [Android](https://support.appsflyer.com/hc/en-us/articles/207032126-AppsFlyer-SDK-Integration-Android){:target="_blank"}) and Segment's mobile FAQs ([iOS](/docs/connections/sources/catalog/libraries/mobile/ios/#faq), [Android](/docs/connections/sources/catalog/libraries/mobile/android/#faq)).

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

@@ -3,7 +3,7 @@ rewrite: true
 title: Apptimize Destination
 id: 5537d3e80a20f4e22f0fb385
 ---
-[Apptimize](https://apptimize.com/) empowers product teams to efficiently run A/B tests, rollout and manage new features, and deliver personalized user experiences. Our Apptimize destination code is open-source. You can browse the code on GitHub for [iOS](https://github.com/Apptimize/analytics-ios-integration-apptimize) and [Android](https://github.com/Apptimize/analytics-android-integration-apptimize).
+[Apptimize](https://apptimize.com/){:target="_blank"} empowers product teams to efficiently run A/B tests, rollout and manage new features, and deliver personalized user experiences. Our Apptimize destination code is open-source. You can browse the code on GitHub for [iOS](https://github.com/Apptimize/analytics-ios-integration-apptimize){:target="_blank"} and [Android](https://github.com/Apptimize/analytics-android-integration-apptimize){:target="_blank"}.
 
 ## Getting Started
 
@@ -60,7 +60,7 @@ Set the plist property `ApptimizeAppKey` to the corresponding app key for the ap
 
 #### Android
 
-Use the [Apptimize.setup](https://sdk.apptimize.com/android/javadocs/javadoc-2.12.10/com/apptimize/Apptimize.html#setup(android.content.Context,%20java.lang.String) API to initialize Apptimize with the app key.
+Use the [Apptimize.setup](https://sdk.apptimize.com/android/javadocs/javadoc-2.12.10/com/apptimize/Apptimize.html#setup(android.content.Context,%20java.lang.String){:target="_blank"} API to initialize Apptimize with the app key.
 
 It is important to note that if the app keys in the plist/code and the Segment dashboard do not match, the SDK will use the app key from the plist/code as it finishes initialization first. While it is safe to initialize Apptimize multiple times in the app, to avoid confusion, be very careful that the app key is the same in both the places.
 

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

@@ -3,7 +3,7 @@ rewrite: true
 title: Asayer Destination
 id: 5d00754256e478000114784f
 ---
-[Asayer](https://asayer.io) is a session replay tool for engineering teams. It lets you capture the full picture of each user session on your website so you can quickly solve issues and improve your customer experience.
+[Asayer](https://asayer.io){:target="_blank"} is a session replay tool for engineering teams. It lets you capture the full picture of each user session on your website so you can quickly solve issues and improve your customer experience.
 
 This destination is maintained by Asayer. For any issues with the destination, [contact the Asayer Support team](mailto:support@asayer.io).
 
@@ -45,7 +45,7 @@ analytics.identify("userId123", {
 });
 ```
 
-**NOTE:** All traits, as well as `userId` and `anonymousId` fields must be explicitly enabled within the Asayer dashboard under [Preferences -> Custom Fields](https://app.openreplay.com/client/custom-fields) before they will successfully send.
+**NOTE:** All traits, as well as `userId` and `anonymousId` fields must be explicitly enabled within the Asayer dashboard under [Preferences -> Custom Fields](https://app.openreplay.com/client/custom-fields){:target="_blank"} before they will successfully send.
 
 ## Track
 

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

@@ -4,7 +4,7 @@ hidden: true
 id: 54c02204db31d978f14a7f6d
 ---
 
-[Atatus](https://www.atatus.com/) provides visibility into the performance of an application and its underlying infrastructure under a single dashboard. This visibility can help businesses identify and diagnose issues, and take corrective action to prevent or resolve application issues.
+[Atatus](https://www.atatus.com/){:target="_blank"} provides visibility into the performance of an application and its underlying infrastructure under a single dashboard. This visibility can help businesses identify and diagnose issues, and take corrective action to prevent or resolve application issues.
 
 ## Getting Started
 Before you start, make sure Atatus supports the source type and connection mode you’ve chosen to implement. You can learn more about [connection modes here](/docs/connections/destinations/#connection-modes).

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

@@ -3,15 +3,15 @@ title: Attribution Destination
 rewrite: true
 id: 54521fd525e721e32a72ee96
 ---
-[Attribution](http://attributionapp.com/) is an easy to use one stop dashboard for multi-touch attribution across all marketing channels. Attribution prides itself on high-fidelity and allows marketers to trace every visit, conversion or revenue dollar to the source. Marketers can easily integrate Attribution and Segment to begin measuring the effectiveness of their campaigns today.
+[Attribution](http://attributionapp.com/){:target="_blank"} is an easy to use one stop dashboard for multi-touch attribution across all marketing channels. Attribution prides itself on high-fidelity and allows marketers to trace every visit, conversion or revenue dollar to the source. Marketers can easily integrate Attribution and Segment to begin measuring the effectiveness of their campaigns today.
 
 ## Getting Started
 
 
 
 1. From the Segment web app, click **Catalog**.
 2. Search for "Attribution" in the Catalog, select it, and choose which of your sources to connect the destination to.
-3. Enter the "Project ID" into your Segment Settings UI which you can find from your [Attribution settings](https://dashboard.attributionapp.com/v1/#!/settings).
+3. Enter the "Project ID" into your Segment Settings UI which you can find from your [Attribution settings](https://dashboard.attributionapp.com/v1/#!/settings){:target="_blank"}.
 4. It will take 15 - 30 minutes for data to begin populating on your Attribution dashboard.
 
 ![gettingstarted](images/att1.png)

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

@@ -19,7 +19,7 @@ This destination is maintained by Ortto. For any issues with the destination, [c
 2. Search for "Ortto" in the Destinations Catalog, and select the "Ortto" destination.
 3. Click **Configure Ortto** and choose which Source should send data to the "Ortto" destination.
 4. If requested, specify the Destination Name for your "Ortto" destination, and click **Save**.
-5. Complete [integrating your Ortto account with Segment](https://help.ortto.com/user/latest/data-sources/configuring-a-new-data-source/3rd-party-integrations/segment.html), which automatically configures your Ortto API keys within your "Ortto" destination in Segment.
+5. Complete [integrating your Ortto account with Segment](https://help.ortto.com/user/latest/data-sources/configuring-a-new-data-source/3rd-party-integrations/segment.html){:target="_blank"}, which automatically configures your Ortto API keys within your "Ortto" destination in Segment.
 
 
 ## Supported methods

src/connections/destinations/catalog/azure-function/index.md

@@ -6,7 +6,7 @@ id: 5cbf95e258453600011d6d8f
 ---
 Segment makes it easy to send your data to Azure Function (and lots of other destinations). When you track your data using Segment's open-source [libraries](/docs/connections/sources/catalog/), Segment can translate and route your data to an Azure Function in the format it expects.
 
-[Azure Function](https://azure.microsoft.com/en-us/services/functions) is a serverless compute service that enables you to run code on-demand without having to explicitly provision or manage infrastructure. Use Azure Functions to run a script or piece of code in response to a variety of events.
+[Azure Function](https://azure.microsoft.com/en-us/services/functions){:target="_blank"} is a serverless compute service that enables you to run code on-demand without having to explicitly provision or manage infrastructure. Use Azure Functions to run a script or piece of code in response to a variety of events.
 
 
 {% include content/beta-note.md %}

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

@@ -3,7 +3,7 @@ title: Batch Destination
 beta: true
 id: 596d11f870a3e552b957e6d9
 ---
-The Batch.com integration code is open sourced on GitHub. Feel free to check it out: [iOS](https://github.com/BatchLabs/ios-segment-integration), [Android](https://github.com/BatchLabs/android-segment-integration).
+The Batch.com integration code is open sourced on GitHub. Feel free to check it out: [iOS](https://github.com/BatchLabs/ios-segment-integration){:target="_blank"}, [Android](https://github.com/BatchLabs/android-segment-integration){:target="_blank"}.
 
 ## Getting Started
 

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

@@ -3,7 +3,7 @@ title: Bento Destination
 id: 5ff25116284da6d5091e21b1
 ---
 
-[Bento](https://www.trybento.co/) allows you to create embedded onboarding solutions to support your users as they get started with your product, and beyond. Using your customer data you can tailor user experiences providing a personalized journey through your product.
+[Bento](https://www.trybento.co/){:target="_blank"} allows you to create embedded onboarding solutions to support your users as they get started with your product, and beyond. Using your customer data you can tailor user experiences providing a personalized journey through your product.
 
 This destination is maintained by Bento. For any issues with the destination, [contact the Bento Support team](mailto:support@trybento.co).