You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/appcues/index.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,15 +15,15 @@ id: 554926390a20f4e22f0fb38a
15
15
16
16
###Server
17
17
18
-
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.
18
+
As an alternative to a traditional JavaScript implementation, Appcues offers a server-side destination with Segment.
19
19
20
20
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.
21
21
22
22
As with the JavaScript destination, you can segment and target user profile and event data received through the Appcues server-side Segment destination.
23
23
24
24
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.
25
25
26
-
26
+
Please note, server side implementations can only be used with server or mobile sources. Analytics.js sources will default to a device-mode connection.