From f8d7080463ceeb342771e2e0ad8dc192820be318 Mon Sep 17 00:00:00 2001 From: Brandon Caudillo <52050659+bcaudillo@users.noreply.github.com> Date: Tue, 12 Sep 2023 14:07:37 -0600 Subject: [PATCH 1/3] Update documentation to reflect Analytics.js limitation --- src/connections/destinations/catalog/appcues/index.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/src/connections/destinations/catalog/appcues/index.md b/src/connections/destinations/catalog/appcues/index.md index 16c9880a3c..442f5d0e3a 100644 --- a/src/connections/destinations/catalog/appcues/index.md +++ b/src/connections/destinations/catalog/appcues/index.md @@ -15,14 +15,16 @@ id: 554926390a20f4e22f0fb38a ### Server -As an alternative to a traditional JavaScript implementation, Appcues offers a server-side destination with Segment. +As an alternative to a traditional JavaScript implementation, Appcues offers a server-side destination with Segment. Please note, as a default, Analytics.js connects in device-mode. For all other sources the default connection is cloud-mode. -You may find the server-side destination useful if you'd like to send user profile or event data to Appcues from another Segment partner service. You can use the server-side destination alongside the JavaScript destination, which you may find preferable to routing all data through the JavaScript destination. +You may find the server-side destination useful if you'd like to send user profile or event data to Appcues from another Segment partner service. You can use the server-side destination alongside the JavaScript destination, which you may find preferable to routing all data through the JavaScript destination. As with the JavaScript destination, you can segment and target user profile and event data received through the Appcues server-side Segment destination. For example, using the server-side destination, you can direct customer profile and event data from a CRM tool into Appcues. You can then use the directed data for content targeting and user segmentation in the Appcues content editor, alongside data from Segment's `analytics.js` destination. + + ## Page Refer to the Segment Spec for information about the [Page method](/docs/connections/spec/page/). The following represents an example `page` call: From e664ed3f0cf6e1f517def5a377ee90322d0955da Mon Sep 17 00:00:00 2001 From: Brandon Caudillo <52050659+bcaudillo@users.noreply.github.com> Date: Fri, 15 Sep 2023 16:38:55 -0600 Subject: [PATCH 2/3] Updated Sever section of Appcues --- src/connections/destinations/catalog/appcues/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/connections/destinations/catalog/appcues/index.md b/src/connections/destinations/catalog/appcues/index.md index 442f5d0e3a..28ceccfccb 100644 --- a/src/connections/destinations/catalog/appcues/index.md +++ b/src/connections/destinations/catalog/appcues/index.md @@ -15,7 +15,7 @@ id: 554926390a20f4e22f0fb38a ### Server -As an alternative to a traditional JavaScript implementation, Appcues offers a server-side destination with Segment. Please note, as a default, Analytics.js connects in device-mode. For all other sources the default connection is cloud-mode. +As an alternative to a traditional JavaScript implementation, Appcues offers a server-side destination with Segment. You may find the server-side destination useful if you'd like to send user profile or event data to Appcues from another Segment partner service. You can use the server-side destination alongside the JavaScript destination, which you may find preferable to routing all data through the JavaScript destination. @@ -23,7 +23,7 @@ As with the JavaScript destination, you can segment and target user profile and For example, using the server-side destination, you can direct customer profile and event data from a CRM tool into Appcues. You can then use the directed data for content targeting and user segmentation in the Appcues content editor, alongside data from Segment's `analytics.js` destination. - +Please note, server side implementations can only be used with server or mobile sources. Analytics.js sources will default to a device-mode connection. ## Page From 50d2db21dce5207916ae9498817c680816cfcf0f Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Thu, 21 Sep 2023 19:22:27 -0400 Subject: [PATCH 3/3] Update src/connections/destinations/catalog/appcues/index.md --- src/connections/destinations/catalog/appcues/index.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/connections/destinations/catalog/appcues/index.md b/src/connections/destinations/catalog/appcues/index.md index 28ceccfccb..2a583e1bfa 100644 --- a/src/connections/destinations/catalog/appcues/index.md +++ b/src/connections/destinations/catalog/appcues/index.md @@ -23,7 +23,8 @@ As with the JavaScript destination, you can segment and target user profile and For example, using the server-side destination, you can direct customer profile and event data from a CRM tool into Appcues. You can then use the directed data for content targeting and user segmentation in the Appcues content editor, alongside data from Segment's `analytics.js` destination. -Please note, server side implementations can only be used with server or mobile sources. Analytics.js sources will default to a device-mode connection. +> info "Implementations can only be used with server or mobile sources" +> Analytics.js sources will default to a device-mode connection. ## Page