From 4ed6ced4e26ad1c06f69fc7c967249faea995401 Mon Sep 17 00:00:00 2001 From: Sarah Rudy <78389005+sarahrudy@users.noreply.github.com> Date: Wed, 31 Jan 2024 14:19:22 -0500 Subject: [PATCH 1/4] Amplitude Actions: Update "tracking sessions" for clarity - Add new subsection for "Track sessions" - Reword paragraph about connection modes for Amplitude Actions for clarity - Add link to Amplitude's documentation for tracking sessions --- .../destinations/catalog/actions-amplitude/index.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/src/connections/destinations/catalog/actions-amplitude/index.md b/src/connections/destinations/catalog/actions-amplitude/index.md index cf54f10903..22c6585b1c 100644 --- a/src/connections/destinations/catalog/actions-amplitude/index.md +++ b/src/connections/destinations/catalog/actions-amplitude/index.md @@ -51,13 +51,15 @@ 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){: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. +The Amplitude (Actions) destination does not offer a device-mode connection mode. Most previous deployments of the Amplitude Segment destination required the device-mode connection to use the `session_id` tracking feature. However, the Amplitude (Actions) destination now includes session ID tracking by default when you use 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”}). - -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. +### Track sessions 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”}. +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 for data going to Amplitude, such as Protocols filtering and transformations, and Profiles Identity Resolution. + +You can read more about Amplitude's [tracking sessions](https://help.amplitude.com/hc/en-us/articles/115002323627-Track-sessions){:target="_blank”} feature in Amplitude's documentation. ### Device ID Mappings The Amplitude destination requires that each event include either a Device ID or a User ID. If a User ID isn't present, Amplitude uses a Device ID, and vice versa, if a Device ID isn't present, Amplitude uses the User ID. From bac6dfffc920f6212eaf2718115b7b008140e707 Mon Sep 17 00:00:00 2001 From: Sarah Rudy <78389005+sarahrudy@users.noreply.github.com> Date: Fri, 9 Feb 2024 11:01:36 -0500 Subject: [PATCH 2/4] Clarify automatic session tracking --- .../destinations/catalog/actions-amplitude/index.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/connections/destinations/catalog/actions-amplitude/index.md b/src/connections/destinations/catalog/actions-amplitude/index.md index 22c6585b1c..c0951f7111 100644 --- a/src/connections/destinations/catalog/actions-amplitude/index.md +++ b/src/connections/destinations/catalog/actions-amplitude/index.md @@ -51,7 +51,9 @@ 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. Most previous deployments of the Amplitude Segment destination required the device-mode connection to use the `session_id` tracking feature. However, the Amplitude (Actions) destination now includes session ID tracking by default when you use 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”}). +The Amplitude (Actions) destination does not offer a device-mode connection mode. Most previous deployments of the Amplitude Segment destination required the device-mode connection to use the `session_id` tracking feature. However, the Amplitude (Actions) destination now includes session ID tracking by default when you use Segment's ([Analytics.js 2.0](/docs/connections/sources/catalog/libraries/website/javascript/){:target="_blank”} libaray. + +If you're using Segment's [Swift](https://github.com/segmentio/analytics-swift){:target="_blank”}, [Kotlin](https://github.com/segmentio/analytics-kotlin){:target="_blank”}, or [React Native](https://segment-docs.netlify.app/docs/connections/sources/catalog/libraries/mobile/react-native/){:target="_blank”} library, you will need to include the [desitnation plugin](https://segment-docs.netlify.app/docs/connections/sources/catalog/libraries/mobile/react-native/destination-plugins/amplitude-react-native/) to enable session tracking. ### Track sessions From b1c19ba1cb53e646e504c849e918a79f2fed90f5 Mon Sep 17 00:00:00 2001 From: Sarah Rudy <78389005+sarahrudy@users.noreply.github.com> Date: Fri, 9 Feb 2024 11:04:02 -0500 Subject: [PATCH 3/4] Move paragraph to Track sessions --- .../destinations/catalog/actions-amplitude/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/connections/destinations/catalog/actions-amplitude/index.md b/src/connections/destinations/catalog/actions-amplitude/index.md index c0951f7111..eb1a6078f2 100644 --- a/src/connections/destinations/catalog/actions-amplitude/index.md +++ b/src/connections/destinations/catalog/actions-amplitude/index.md @@ -53,14 +53,14 @@ To manually add the Log Purchases Action: The Amplitude (Actions) destination does not offer a device-mode connection mode. Most previous deployments of the Amplitude Segment destination required the device-mode connection to use the `session_id` tracking feature. However, the Amplitude (Actions) destination now includes session ID tracking by default when you use Segment's ([Analytics.js 2.0](/docs/connections/sources/catalog/libraries/website/javascript/){:target="_blank”} libaray. -If you're using Segment's [Swift](https://github.com/segmentio/analytics-swift){:target="_blank”}, [Kotlin](https://github.com/segmentio/analytics-kotlin){:target="_blank”}, or [React Native](https://segment-docs.netlify.app/docs/connections/sources/catalog/libraries/mobile/react-native/){:target="_blank”} library, you will need to include the [desitnation plugin](https://segment-docs.netlify.app/docs/connections/sources/catalog/libraries/mobile/react-native/destination-plugins/amplitude-react-native/) to enable session tracking. - ### Track sessions 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”}. 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 for data going to Amplitude, such as Protocols filtering and transformations, and Profiles Identity Resolution. +If you're using one of Segment's [Swift](https://github.com/segmentio/analytics-swift){:target="_blank”}, [Kotlin](https://github.com/segmentio/analytics-kotlin){:target="_blank”}, or [React Native](https://segment-docs.netlify.app/docs/connections/sources/catalog/libraries/mobile/react-native/){:target="_blank”} libraries, you will need to include the [desitnation plugin](https://segment-docs.netlify.app/docs/connections/sources/catalog/libraries/mobile/react-native/destination-plugins/amplitude-react-native/) to enable session tracking. + You can read more about Amplitude's [tracking sessions](https://help.amplitude.com/hc/en-us/articles/115002323627-Track-sessions){:target="_blank”} feature in Amplitude's documentation. ### Device ID Mappings From 251d790541a49a3078648ba4ca9f858b28be930c Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Tue, 20 Feb 2024 13:02:19 -0500 Subject: [PATCH 4/4] Apply suggestions from code review --- .../destinations/catalog/actions-amplitude/index.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/connections/destinations/catalog/actions-amplitude/index.md b/src/connections/destinations/catalog/actions-amplitude/index.md index eb1a6078f2..eed70ad6c8 100644 --- a/src/connections/destinations/catalog/actions-amplitude/index.md +++ b/src/connections/destinations/catalog/actions-amplitude/index.md @@ -51,15 +51,15 @@ 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. Most previous deployments of the Amplitude Segment destination required the device-mode connection to use the `session_id` tracking feature. However, the Amplitude (Actions) destination now includes session ID tracking by default when you use Segment's ([Analytics.js 2.0](/docs/connections/sources/catalog/libraries/website/javascript/){:target="_blank”} libaray. +The Amplitude (Actions) destination does not offer a device-mode connection mode. Previous deployments of the Amplitude Segment destination required the device-mode connection to use the `session_id` tracking feature. However, the Amplitude (Actions) destination now includes session ID tracking by default when you use Segment's ([Analytics.js 2.0](/docs/connections/sources/catalog/libraries/website/javascript/) library. ### Track sessions -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”}. +Session tracking is available with Segment's new libraries: [Analytics.js 2.0](/docs/connections/sources/catalog/libraries/website/javascript/), [Swift](/docs/connections/sources/catalog/libraries/mobile/apple/) or [Kotlin](/docs/connections/sources/catalog/libraries/mobile/kotlin-android/). -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 for data going to Amplitude, such as Protocols filtering and transformations, and Profiles Identity Resolution. +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 or write any code to run on the user's device, and can use more of the Segment platform features for data going to Amplitude, like [Protocols filtering and transformations](/docs/protocols/) and [Unify Identity Resolution](/unify/identity-resolution/). -If you're using one of Segment's [Swift](https://github.com/segmentio/analytics-swift){:target="_blank”}, [Kotlin](https://github.com/segmentio/analytics-kotlin){:target="_blank”}, or [React Native](https://segment-docs.netlify.app/docs/connections/sources/catalog/libraries/mobile/react-native/){:target="_blank”} libraries, you will need to include the [desitnation plugin](https://segment-docs.netlify.app/docs/connections/sources/catalog/libraries/mobile/react-native/destination-plugins/amplitude-react-native/) to enable session tracking. +If you're using one of Segment's [Swift]((/docs/connections/sources/catalog/libraries/mobile/apple/), [Kotlin](/docs/connections/sources/catalog/libraries/mobile/kotlin-android/), or [React Native](/docs/connections/sources/catalog/libraries/mobile/react-native/) libraries, you will need to include the Amplitude destination plugin to enable session tracking. You can read more about Amplitude's [tracking sessions](https://help.amplitude.com/hc/en-us/articles/115002323627-Track-sessions){:target="_blank”} feature in Amplitude's documentation.