Merge pull request #1517 from segmentio/kdaswani-patch-2

Add note about pageName screen setting.md

Author: markzegarelli

src/connections/destinations/catalog/adobe-analytics/index.md

@@ -105,7 +105,7 @@ Segment's server-side integration is not open-source. Let's explore what happens
 
    For `.page()` events, this XML tag is set as the `category` of the page call, which is sent by providing both `category` and `name` (ie. `.page('Some Category', 'Some Name');`)
 
-3. For `.track()` events, Segment sets `<pageName>` as `properties.pageName`, `properties.page`, `context.page.title`, `context.screen.name` or `'None'` (in order of precedence).
+3. For `.track()` events, Segment sets `<pageName>` as `properties.pageName`, `properties.page`, `context.page.title`, or `context.screen.name` (in order of precedence). If none of these fields are available and **Page Name Fallback to Screen** is enabled, Segment sets `properties.screen` to `<pageName>`.  Otherwise, Segment falls back to `'None'`.
    For `.page()` calls, Segment sets the tag as the `name`. This can be sent by providing the first parameter: `.page('Some Name');`
 
 4. Since Adobe Analytics does not [support sending timestamped hits a `<visitorID>`](https://marketing.adobe.com/resources/help/en_US/sc/implement/timestamps-overview.html), if you have set your Report to **Timestamp Disabled**, Segment sets `<visitorID>` as these values in order of precedence: