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
82
82
83
83
You can update those fields using this identify call:
20
20
21
21
## Analytics.js - Device Mode
22
22
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.
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.
24
24
25
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.
26
26
@@ -65,4 +65,4 @@ If **No Fallbacks for Visitor ID** is enabled, and you're setting a `marketingCl
65
65
66
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.
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/adobe-analytics/index.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -45,7 +45,7 @@ To set up Adobe Analytics as a destination for your Segment data, Segment needs
45
45
46
46
- If you're using Device-mode data collection with Analytics.js, or using a server-side library, you need your Adobe Report Suite ID, and your Tracking Server URL. You'll add this information in the Destination settings in the Segment app UI so that Segment can send information to Adobe. An example tracking server is `jimsbrims.sc.omtrdc.net`. You do not need to include the hypertext transfer protocol (ie. `http://`). For more information on how to identify your analytics tracking server and report suites see Adobe's [documentation here](https://docs.adobe.com/content/help/en/analytics-learn/tutorials/implementation/implementation-basics/how-to-identify-your-analytics-tracking-server-and-report-suites.html).
47
47
48
-
48
+
49
49
50
50
- If you're collecting data from mobile devices, you can download the `ADBMobileConfig.json` file instead of specifying these settings in the UI which contains that information. Follow the instructions in Adobe's documentation, [here for iOS](https://marketing.adobe.com/resources/help/en_US/mobile/ios/dev_qs.html), and [here for Android](https://marketing.adobe.com/resources/help/en_US/mobile/android/dev_qs.html).
51
51
@@ -84,7 +84,7 @@ Segment's Analytics.js destination loads the Adobe `visitorAPI.js` library, but
84
84
85
85
To use Adobe's Marketing Cloud Visitor ID Service, enter your **Marketing Cloud Organization ID** in the **Identity Resolution** settings tab in the Segment app.
86
86
87
-
87
+
79
81
80
82
## Sending Custom Properties
81
83
82
84
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.
217
+
218
+
217
219
218
220
Using the sample settings in the image above, if you make the Track call example below:
219
221
@@ -296,11 +298,11 @@ When you make a `page` call, here's what Segment does from the browser when you
296
298
297
299
6. Checks if any of the page call's properties are mapped to any custom Adobe Analytics variables such as `eVar`, `props`, and `hVar`.
304
+
305
+
304
306
305
307
If you make the following page call:
306
308
@@ -329,7 +331,7 @@ Custom Conversion variables, also known as eVars, are how Adobe segments convers
329
331
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
332
331
333
An example eVar mapping in the Segment Destination settings UI should look like this:
333
335
334
336
## Merchandising events
335
337
@@ -353,7 +355,7 @@ The Segment Adobe Analytics Merchandising setting runs as follows:
357
359
358
360
The configuration in the example image above configures an `Order Completed` Segment event which sends Adobe Analytics:
359
361
-`event1` in `s.events` with the value passed from `properties.increment`.
@@ -446,11 +448,11 @@ analytics.page({
446
448
447
449
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.
450
452
451
453
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.
454
456
455
457
## List Variables - lVars
456
458
@@ -465,7 +467,7 @@ For list variables and props you can either send the property value as a comma d
465
467
**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
468
467
469
The example below shows how to configure the Segment custom delimiter mapping for a List Variable.
469
471
470
472
When you send an event:
471
473
```javascript
@@ -486,7 +488,7 @@ Hierarchy variables mirror how customers can track “breadcrumbs” or “bread
486
488
487
489
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.
490
492
491
493
## Context Data Variables
492
494
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.
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/adroll/index.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ id: 54521fd525e721e32a72ee8e
13
13
2. Search for "Adroll" in the Catalog, select it, and choose which of your sources to connect the destination to.
14
14
3. Locate both your AdRoll Advertiser ID and Pixel ID in AdRoll's "Audience" tab, "AdRoll Pixel" section. Click on "View Pixel". Your Advertiser ID will be listed beside `adroll_adv_id` and your AdRoll Pixel will be listed beside `adroll_pix_id`.
15
15
16
-
16
+
17
17
18
18
4. Add both your Advertiser ID and Pixel ID to your Segment Destination Settings.
19
19
@@ -44,17 +44,17 @@ analytics.track('Sign-up Form Completed');
44
44
```
45
45
In order to send your `track` calls to AdRoll for segmenting your users, get started by creating a new "segment" in their interface, copying the "Segment ID", and pasting that following a `+` into the URL rule field.
46
46
47
-
47
+
48
48
49
49
Map your client-side Analytics.js event names to the corresponding AdRoll "Segment ID" in the Segment Settings UI.
50
50
51
-
51
+
52
52
53
53
We'll fire the correct pixel accordingly to put the user into that "segment" whenever they trigger the event you've chosen. Note that you will still need to map semantic events like `Viewed Product`, `Added Product`, and `Order Completed`.
54
54
55
55
Then, inside AdRoll you can create a "segment" of all users doing any of those events by adding a `+` to the segment name and adding it in the URL field, like this:
56
56
57
-
57
+
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/adwords-remarketing-lists/index.md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -88,7 +88,7 @@ Before you start, make sure you have administrative access to the Google Ads acc
88
88
2. Give your audience a name, some event and trait criteria, then click **Preview**.
89
89
3. Select “Google Ads Remarketing Lists” as a destination for your audience.
90
90
4. Select either email or mobile ID to use as a custom matcher.
91
-
91
+
92
92
93
93
5. Give your audience a name, and click **Create**.
94
94
@@ -99,7 +99,7 @@ Before you start, make sure you have administrative access to the Google Ads acc
99
99
100
100
In Google Ads, go to **Tools & Settings** > **Shared Library** > **Audience manager** > **Audience lists**.
101
101
102
-
102
+
103
103
104
104
> info ""
105
105
> **Note**: Google Ads can take 24+ hours to fully process initial audience uploads before they can be used for a campaign. If the audience is still processing, the list status appears as “Populating”.
@@ -111,7 +111,7 @@ In Google Ads, go to **Tools & Settings** > **Shared Library** > **Audience mana
111
111
- Make sure you authorized Google Ads and selected the correct account.
112
112
- Make sure you have administrator access for your Google Ads account. You can check that your credentials are correct by navigating to the Google Ads Remarketing Lists destination in **Engage Settings** > **Destinations**, and viewing the settings.
113
113
114
-
114
+
0 commit comments