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
This explains how your destination settings (for Identity Resolution and Timestamps) change how user session data (the `userId` and `visitorId`) are sent to Adobe Analytics. You should get familiar with the destination settings in the Segment app before continuing.
9
-
6
+
This page explains how your destination settings (for Identity Resolution and Timestamps) change how user session data (the `userId` and `visitorId`) are sent to Adobe Analytics. You should get familiar with the destination settings in the Segment app before continuing.
10
7
11
8
The Identity Resolution destination settings are:
12
9
-**Marketing Cloud ID**
13
10
-**Drop VisitorID**, and **No Fallbacks for VisitorID:Server-Side Only** destination settings.
If you're using Analytics.js in device-mode, Segment "wraps" the Adobe libraries. In this configuration, Segment sends Events directly from the client using the Adobe Analytics [`Appmeasurement.js` library](https://docs.adobe.com/content/help/en/analytics/implementation/js/overview.html). For more information on choosing a connection mode see our section on [Choosing between Device-mode and Cloud-mode](index/#choosing-between-device-mode-and-cloud-mode). In this section we will discuss how identity resolution is handled if you are using Analytics.js in device-mode.
23
+
If you're using Analytics.js in device-mode, Segment "wraps" the Adobe libraries. In this configuration, Segment sends Events directly from the client using the Adobe Analytics [`Appmeasurement.js` library](https://docs.adobe.com/content/help/en/analytics/implementation/js/overview.html). For more information on choosing a connection mode see our section on [Choosing between Device-mode and Cloud-mode](/docs/connections/destinations/catalog/adobe-analytics/#choosing-between-device-mode-and-cloud-mode). In this section we will discuss how identity resolution is handled if you are using Analytics.js in device-mode.
27
24
28
25
You can enable **Drop Visitor ID** from the Segment app to prevent Adobe from creating a new user profile when you set `window.s.visitorID` with a custom value. However if you're only using Analytics.js to send data to Adobe, this can make it difficult to combine anonymous and identified users inside your reports.
Once you `identify` your user, Segment sets the `visitorId` variable to your `userId`. This effectively creates a new user, which *does* have unique user implications. However, based on a thorough reading of the Adobe documentation and discussion with many customers, we believe this is the best practice because it allows you to seamlessly track logged-in users across devices.
37
34
38
-
###Cloud Mode - Server Side
35
+
## Cloud Mode - Server Side
39
36
40
-
In Cloud Mode, you can send data through the Segment servers where it is then mapped and sent on to Adobe Analytics. "Cloud-mode" data is data sent _without_ bundling the Segment-Adobe-Analytics SDK. You enable Cloud-mode from the Adobe Analytics source settings in the Segment app. It can be sent using mobile libraries, Analytics.js, and other server-based sources. Cloud mode data is sent to Adobe using Adobe's data insertion API in XML format. For more information on choosing a connection mode see our section on [Choosing between Device-mode and Cloud-mode](index/#choosing-between-device-mode-and-cloud-mode). In this section we will discuss how identity resolution is handled if you are using a Cloud Mode connection.
37
+
In Cloud Mode, you can send data through the Segment servers where it is then mapped and sent on to Adobe Analytics. "Cloud-mode" data is data sent _without_ bundling the Segment-Adobe-Analytics SDK. You enable Cloud-mode from the Adobe Analytics source settings in the Segment app. It can be sent using mobile libraries, Analytics.js, and other server-based sources. Cloud mode data is sent to Adobe using Adobe's data insertion API in XML format. For more information on choosing a connection mode see our section on [Choosing between Device-mode and Cloud-mode](/docs/connections/destinations/catalog/adobe-analytics/#choosing-between-device-mode-and-cloud-mode). In this section we will discuss how identity resolution is handled if you are using a Cloud Mode connection.
41
38
42
39
There are several options for tracking your users on the server. If you only track logged-in users, you can send their `userId` in your events to ensures that the events are attributed to the correct user. If you're tracking anonymous users, Segment sends the `s_vi` cookie from Adobe if you pass it under `context['Adobe Analytics'].visitorId` as the `visitorId`. If you do not pass as `visitorID`, Segment uses the `userId` if present, or as a last resort uses the Segment `anonymousId`. The Segment `anonymousId` is different from the anonymous `s_vi` value that Adobe Analytics auto-generates and uses on the client as an anonymous ID.
43
40
@@ -53,7 +50,7 @@ If you're using the Experience Cloud ID, you should accept this and use the Segm
53
50
We know this is daunting territory, so don't hesitate to [contact us directly for guidance](https://segment.com/help/contact/).
54
51
55
52
56
-
####No Fallbacks for VisitorId Setting - Cloud Mode Only
53
+
## No Fallbacks for VisitorId Setting - Cloud Mode Only
57
54
58
55
Segment introduced a new **No Fallbacks for Visitor ID** setting to help with the transition from using the Adobe Analytics `visitorID` to using the Experience Cloud ID (ECID). If a `visitorId` is not explicitly sent in the integration specific object in your payload (ie. `context["Adobe Analytics"].visitorId`), Segment will fallback to setting the `<visitorID>` tag to `userId` (or `anonymousId`, if the call is anonymous). You can use this setting to indicate that you only want the `<visitorId>` tag to be set with the `visitorId` value sent in your integration specific object. Enabling this will help to reduce inflated user counts that are set with a Segment `userId`.
59
56
@@ -68,4 +65,4 @@ If **No Fallbacks for Visitor ID** is enabled, and you're setting a `marketingCl
68
65
69
66
This decision tree is a visual representation of how Segment's Adobe Analytics destination settings and payload data interact with Segment to determine when to send a `visitorId` to Adobe.
You can use the `Context Data Variables` settings to map Segment `properties` to any context data variable defined in your Adobe Analytics Mobile Services dashboard. This includes both Adobe `props` and `eVars`. You can see a list of the Adobe variable types in your Adobe Mobile Services dashboard.
@@ -329,7 +329,7 @@ Custom Conversion variables, also known as eVars, are how Adobe segments convers
329
329
You must configure an eVar mapping in your Segment destination settings to send eVars to Adobe on Track and Page calls. When configuring the mapping, the list of eVars must be defined in the Adobe Analytics UI. Map your Adobe Analytics eVar names to the Segment property names you’re using in your Segment events. Enter a Segment property name on the left and an Adobe Analytics eVar number on the right. You can view your Segment events and properties in your Schema.
330
330
331
331
An example eVar mapping in the Segment Destination settings UI should look like this:
The configuration in the example image above configures an `Order Completed` Segment event which sends Adobe Analytics:
359
359
-`event1` in `s.events` with the value passed from `properties.increment`.
@@ -446,11 +446,11 @@ analytics.page({
446
446
447
447
Custom Traffic Variables, also known as props, allow you to correlate custom data with specific traffic-related events in Adobe. To learn more about props and how to configure them in the Adobe UI, see the documentation [here](https://docs.adobe.com/content/help/en/analytics/admin/admin-tools/traffic-variables/traffic-var.html). You can map your Segment properties in your destination settings to any of your Adobe props.
You can either send the property value as a string (ie. `'brady'`) or as an array (`['brady', 'edelman', 'blount']`). If you choose to send them as an array, Segment defaults to join it so that it is a pipe (`|`) delimited string before sending to Adobe (ie. `'brady|edelman|blount'`). See the [documentation on setting a custom delimiter](#custom-delimiter) to learn more.
@@ -465,7 +465,7 @@ For list variables and props you can either send the property value as a comma d
465
465
**Note:** You must configure the custom delimiter in _both_ the Adobe Analytics dashboard, and in the Segment Adobe Analytics destination settings, for each list variable and prop. Do this in the Adobe Analytics dashboard before setting up this mapping in the Segment destination settings.
466
466
467
467
The example below shows how to configure the Segment custom delimiter mapping for a List Variable.
@@ -486,7 +486,7 @@ Hierarchy variables mirror how customers can track “breadcrumbs” or “bread
486
486
487
487
Map your Adobe Analytics hVars to the property names you use in your Segment Page calls. Enter a Segment property name on the left, and an Adobe Analytics hVar number on the right. You can view your Segment page calls and properties in your Schema.
Context data variables let you define custom variables on each page that processing rules can read. See the Adobe documentation to learn more about [how to use Adobe Analytics `contextData` and use processing rules](https://docs.adobe.com/content/help/en/analytics/implementation/vars/page-vars/contextdata.html) to populate analytics variables from that data.
0 commit comments