segmentio
diff --git a/‎src/_data/sidenav/strat.yml
Lines changed: 8 additions & 5 deletions b/‎src/_data/sidenav/strat.yml
Lines changed: 8 additions & 5 deletions
diff --git a/‎src/connections/destinations/catalog/adobe-analytics/best-practices.md
Lines changed: 33 additions & 46 deletions b/‎src/connections/destinations/catalog/adobe-analytics/best-practices.md
Lines changed: 33 additions & 46 deletions
@@ -1,18 +1,21 @@
 ---
 sections:
 - slug: adobe
-  section_title: Adobe Integrations
+  section_title: Adobe Analytics
   section:
   - path: /connections/destinations/catalog/adobe-analytics
     title: Adobe Analytics destination
+  - path: /connections/destinations/catalog/adobe-analytics/settings
+    title: Mapping Segment to Adobe Analytics
+  - path: /connections/destinations/catalog/adobe-analytics/identity
+    title: Identity Resolution in Segment Adobe Analytics
   - path: /connections/destinations/catalog/adobe-analytics/mobile
-    title: Set up Adobe Analytics for mobile
+    title: Adobe Analytics for mobile
   - path: /connections/destinations/catalog/adobe-analytics/heartbeat
-    title: Set up Adobe Analytics Heartbeat
+    title: Adobe Analytics Heartbeat
   - path: /connections/destinations/catalog/adobe-analytics/best-practices
     title: Adobe Analytics Best Practices
-  - path: /connections/destinations/catalog/adobe-target
-    title: Adobe Target destination
+
 
 
 - slug: facebook
 
@@ -3,7 +3,17 @@ title: Adobe Analytics Best Practices
 strat: adobe
 ---
 
-There are a few common questions that we've heard over time that are worth mentioning.
+This page contains best practices and tips for setting up and testing Adobe Analytics with Segment.
+
+## Validating by Data by Component
+
+The following list contains tools you can use to validate data coming from Segment and going to each different Adobe Analytics component
+
+- **Analytics.js** - [Adobe Experience Cloud Debugger](https://chrome.google.com/webstore/detail/adobe-experience-cloud-de/ocdmogmohccmeicdhlhhgepeaijenapj) and Chrome Developer Tools
+- **Other Segment server libraries** - Segment's in-app [Event Tester Tool](/docs/connections/test-connections/)
+- **iOS Device mode** - Charles Proxy, DEBUG mode
+- **Android Device Mode** - Charles Proxy, VERBOSE logging
+
 
 ## Reducing API calls by sending events on page or screen
 
@@ -19,7 +29,7 @@ For example, instead of sending the Product Viewed event as a `track` to AA, you
     }
 ```
 
-When the integration option `events` is passed in, we map the events and send them using the `<events>` tag. In the example above, we would build `<events>event35, scAdd</events>`.
+When the integration option `events` is passed in, Segment maps the events and sends them using the `<events>` tag. In the example above, the output would be `<events>event35, scAdd</events>`.
 
 _Considerations_
 
@@ -33,19 +43,20 @@ _Considerations_
 ```
 
 ## Setting custom linkTypes, linkNames and linkUrls
-If you are setting up the Adobe Analytics destination in cloud-mode, you can pass in custom linkTypes, linkNames and linkURLs.
 
-**Note**: If you pass in the `visitorId` in a destination specific `integration` object within your Segment `page` or `track` events, then the `visitorId` passed will persist on page or track calls that occur after an identify call. This will effectively supersede Segment setting the `visitorId` variable to your `userId` after an `identify` call.
+If you are setting up the Adobe Analytics destination in cloud-mode, you can pass in custom `linkTypes`, `linkNames` and `linkURLs`.
+
+**Note**: If you pass in the `visitorId` in a destination-specific `integration` object in your Segment Page or Track events, the `visitorId` passed persists on Page or Track calls that occur after an Identify call. This effectively supersedes the `visitorId` variable Segment would set to your `userId` after an Identify call.
 
-We know this is daunting territory, so don't hesitate to contact us directly for guidance!
+We know this is daunting territory, so don't hesitate to [contact us directly for guidance](https://segment.com/help/contact/)!
 
-**Setting the event linkType**
+### Setting the event linkType
 
-By default, Segment's integration with Adobe Analytics automatically sets an events linkType as a custom link or 'o' for 'other' within the s.tl() call. If you want to set the linkType of an event as download or exit links, you can pass in the following values within the `integrations.adobe analytics` object of your Segment event payload.
+By default, Segment's integration with Adobe Analytics automatically sets an events `linkType` as a custom link `o` for 'other' within the `s.tl()` call. To set the `linkType` of an event as download or exit link, you can pass in a different value in the `integrations.adobe analytics` object of your Segment event payload.
 
-A value of `d` or `D` will map to download links and a value of `e` or `E` will map to exit links
+A value of `d` or `D` maps to "download" links, and a value of `e` or `E` maps to "exit" links
 
-Below is a sample snippet of how you would set a Segment event as a download link type:
+The example below shows of how you would set a Segment event as a download link type:
 
 ```javascript
 "integrations": {
@@ -55,64 +66,40 @@ Below is a sample snippet of how you would set a Segment event as a download lin
 }
 ```
 
-If you pass in Segment events with a download (d or D) linkType, it will populate the Download link report in your Adobe Analytics reporting suite. If you pass in Segment events with a exit (e or E) linkType, it will populate the Exit link report in your Adobe Analytics reporting suite. Finally, if you pass in Segment event with either no linkType or a value of "o" or "O" in the integration.Adobe Analytics object, it will populate the custom link report in your Adobe Analytics reporting suite.
+If you pass in Segment events with a download (d or D) linkType, they appear the Download link report in your Adobe Analytics reporting suite. If you pass in Segment events with an "exit" (e or E) linkType, they appear in the Exit link report in your Adobe Analytics reporting suite. Finally, if you pass in Segment events with a value of `o` or `O`, or _no_ linkType in the `integration.Adobe Analytics` object, they appear in the custom link report in your Adobe Analytics reporting suite.
 
-**Setting the event linkName**
+### Setting the event linkName
 
-If you want to pass in a custom LinkName to Adobe Analytics, you can now define it by passing it as a string within the `integrations.Adobe Anlaytics`object of your Segment event. An example would be like the one below:
+To pass in a custom LinkName to Adobe Analytics, pass it as a string in the `integrations.Adobe Analytics` object of your Segment event. The example below sets the custom linkname to "Click me".
 
 ```javascript
 "integrations": {
         "Adobe Analytics": {
-          "linkName": "some link name"
+          "linkName": "Click me"
         }
     }
 ```
 
-If a custom linkName is not specified in the integration specific object in the payload, Segment will default to mapping `linkName` to the value from `(context.page.url)`. If there is no URL present Segment will set `linkName`  to `No linkName provided`.
+If you don't specify a custom linkName in the integration specific object in the payload, Segment defaults to mapping `linkName` to the value from `(context.page.url)`. If no URL is present, Segment sets `linkName` to `No linkName provided`.
 
-NOTE: The `useLegacyLinkName` setting in the UI will be respected if you have the setting enabled and you send a custom `linkName` in the integration specific object.
+> note ""
+> **Note**: If you enable the `useLegacyLinkName` setting in the UI, Segment prepends `Link Name -` to the value you specified in the integration-specific object.
 
-**Setting the event LinkURL**
+### Setting the event LinkURL
 
-If you want to pass in a custom LinkUrl to Adobe Analytics, you can do this by passing it as a string within the `integrations.Adobe Anlaytics`object of your Segment event. An example would be like the one below:
+To pass a custom LinkUrl to Adobe Analytics, pass it as a string in the `integrations.Adobe Analytics` object of your Segment event. The example below sets the custom linkURLs to "example.com/example".
 
 ```javascript
 "integrations": {
         "Adobe Analytics": {
-          "linkUrl": "some link url"
+          "linkUrl": "example.com/example"
         }
     }
 ```
 
-If a custom linkUrl is not specified in the integration specific object in the payload, Segment will default to mapping `linkUrl` to the `(context.page.url)`. If there is no URL present Segment will set `linkUrl`  to `No linkUrl provided`.
-
-
-## Best practices for userId and sessioning
-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, this can break the links between anonymous and identified users inside your reports, if you're only using Analytics.js to send data to Adobe.
-
-Adobe Analytics unfortunately counts every "effective" visitor ID as a *unique* visitor. There is no ability for Segment to alias, implicitly or explicitly, two effective IDs on your behalf.
-
-Key to understanding the implications of this fact is an understanding of what Adobe Analytics means by **"effective" visitor ID**. To do so, we recommend reading [this section of their documentation](https://marketing.adobe.com/resources/help/en_US/sc/implement/xdevice_visid.html).
-
-With analytics.js, we use the default auto-generated Adobe Analytics [`s_vi` cookie value](https://marketing.adobe.com/developer/documentation/data-insertion/c-visitor-id) as effective visitor ID until you `identify` your users. If you provide your Marketing Cloud ID Service Organization ID, then we'll set the MCVID and use that instead.
-
-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 their documentation and discussion with many customers, we believe this is the best practice because now you can seamlessly track this user across devices whenever they are logged in.
-
-So if you'd like to track your users on the server as well, you have a few options. If you're only tracking logged-in users, sending their `userId` in your events ensures that the events are attributed to the proper user. If you're tracking anonymous users too, Segment sends the `s_vi` cookie from Adobe if you pass it under `context['Adobe Analytics'].visitorId` as the `visitorId`. Then we fallback on the `userId` and lastly the Segment `anonymousId`, which you'll notice is a different ID from the anonymous `s_vi` value used on the client (Adobe Analytics' auto-generated effective ID for anonymous users).
-
-If you don't mind slightly inflated unique user counts, this may be acceptable, as all events in that anonymous user's session are still attributable to a single user ID. If you really do want to tie the anonymous event from the client side with your server side events, you could grab the `s_vi` cookie value from the client and pass it to your server. We respect any value passed in `context["Adobe Analytics"].visitorId` and pass that as the `visitorID` if provided. But keep in mind that if you go this route, you would probably need to manage the `s_vi` cookies for all your users since you always need to pass it with all your server side calls. Note that you can only parse the `s_vi` cookie if you have **1st party cookie** enabled in you reporting suite.
-
-Thus our recommendation is to take the slightly inflated user count, and just use the Segment `userId` as the `visitorId`. Yes, you'll have two user profiles if you have any anonymous client side events, but you can always set up custom eVars to connect the few anonymous events to the right user.
-
-If you're using the `marketingCloudVisitorID`, we recommend doing this and including it in `context["Adobe Analytics"].marketingCloudVisitorId`. Segment sends both the `userId` (or `anonymousId`, if the call is anonymous) in the `<visitorId>` tag and the MCVID in the `<marketingCloudVisitorID>` tag, and Adobe handles it from there.
-
-**Note**: If you pass in the `visitorId` in a destination specific `integration` object within your Segment `page` or `track` events, then the `visitorId` persists on page or track calls that occur after an identify call. This effectively supersedes Segment setting the `visitorId` variable to your `userId` after an `identify` call.
-
-<!-- TODO if you manually pass the visitorID in the Segment page or track call, then it sticks around after identify is called, and it prevents it from breaking - whatever you pass in the integrations object overrides what segment's adobe integration code logic does-->
-
-We know this is daunting territory, so don't hesitate to contact us directly for guidance!
+If you don't specify a custom linkUrl in the integration specific object in the payload, Segment defaults to mapping `linkUrl` to the `(context.page.url)`. If no is URL present, Segment sets `linkUrl`  to `No linkUrl provided`.
 
 ## Populating Custom Links report with server side data
 
-Since we cannot automatically track page data for **server side** calls, if you want to populate the **Custom Links** report in Adobe Analytics, you must manually pass `context.page.url`.
+Since Segment cannot automatically track page data for **server side** calls, you must manually pass `context.page.url` if you want to populate the **Custom Links** report in Adobe Analytics.
+<!-- TODO this is a lot to parse. can we explain when you might do this? -->