Merge branch 'master' into DOC-151_Redshift-update

markzegarelli · web-flow · commit 99bb0fd960e5 · 2021-04-15T14:21:15.000-07:00
diff --git a/.buildkite/pipeline.yml b/.buildkite/pipeline.yml
diff --git a/src/_includes/components/signpost.html b/src/_includes/components/signpost.html
@@ -13,6 +13,7 @@
         title=category.name
         description=category.description
         variant="related"
+        newtab="false"
       %}
     </div>
   {% endfor %}
diff --git a/src/_release_notes/2020-09-08-data-lakes.md b/src/_release_notes/2020-09-08-data-lakes.md
@@ -16,7 +16,7 @@ doc_links:
     url: "/docs/connections/storage/data-lakes/"
   - 
     title: Set Up Segment Data Lakes
-    url: "docs/connections/storage/catalog/data-lakes"
+    url: "/docs/connections/storage/catalog/data-lakes"
 # images:
 #   -
 #     path: images/release-notes/identity-onboarding-1.png
diff --git a/src/_sass/components/_search.scss b/src/_sass/components/_search.scss
@@ -14,7 +14,6 @@
   line-height: 1.5;
   font-size: 12px;
   font-family: "SF Pro Text", BlinkMacSystemFont, -apple-system, "Segoe UI", "Roboto", "Oxygen", "Ubuntu", "Cantarell", "Fira Sans", "Droid Sans", "Helvetica Neue", "Helvetica", "Arial", sans-serif;
-  border: 1px solid #d8dae5;
   background-color: #ffffff;
   color: #474d66;
   border-radius: 4px;
@@ -23,9 +22,11 @@
   width: 100%;
 }
 
-.aa-Input:focus{
+.aa-Form:focus-within{
   box-shadow: 0 0 5px #2952cc;
   transition: all 0.30s ease-in-out;
+  outline: none;
+  border: 1px solid rgba(128,126,163,.8);
 }
 
 .aa-dataset-article {
diff --git a/src/connections/destinations/catalog/adobe-analytics/index.md b/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:
diff --git a/src/connections/destinations/catalog/facebook-pixel-server-side/index.md b/src/connections/destinations/catalog/facebook-pixel-server-side/index.md
@@ -78,7 +78,7 @@ This approach provides a redundancy that ensures maximum signal reliability. Eve
 For this option to work best, you must pass the same `external_id` from both the browser and the server sources.
 To do this, go to your Facebook Pixel destination settings in Segment, and enable **Use UserId or Anonymous Id as External Id**. By default the Facebook Conversions API destination uses the `userId` (or `anonymousId` if not present) to set the External Id, so when you set up Facebook Pixel to use the same settings, Facebook can then match the users.
 
-You can also increase the match rate for events from a server source by sending [user traits in the context object of the track events](/#default-mappings-to-facebook-properties). You can also collect other fields from the browser, such as `userAgent`, `ip` address, and [Facebook's parameters (fbp, fbc)](https://developers.facebook.com/docs/marketing-api/conversions-api/parameters/fbp-and-fbc) and pass them to the server, and manually add them to the events.
+You can also increase the match rate for events from a server source by sending [user traits in the context object of the track events](#default-mappings-to-facebook-properties). You can also collect other fields from the browser, such as `userAgent`, `ip` address, and [Facebook's parameters (fbp, fbc)](https://developers.facebook.com/docs/marketing-api/conversions-api/parameters/fbp-and-fbc) and pass them to the server, and manually add them to the events.
 
 #### Deduplication considerations
 
@@ -92,7 +92,7 @@ Use this approach if you want to separate tracking events completed on a user's
 
 For this option to work best, the same `external_id` needs to be passed from the browser and from the server. To easily achieve this go to your Segment destination settings for Facebook Pixel and toggle on the setting called **Use UserId or Anonymous Id as External Id**. The Facebook Conversions API destination uses the userId (or anonymousId if not present) to set the External Id by default. Therefore enabling this on Facebook Pixel will allow Facebook to match the users.
 
-You can also increase the match rate for events from a server source by sending [user traits in the context object of the track events](/#default-mappings-to-facebook-properties). You can also collect other fields from the browser, such as `userAgent`, `ip` address, and [Facebook's parameters (fbp, fbc)](https://developers.facebook.com/docs/marketing-api/conversions-api/parameters/fbp-and-fbc) and pass them to the server, and manually add them to the events.
+You can also increase the match rate for events from a server source by sending [user traits in the context object of the track events](#default-mappings-to-facebook-properties). You can also collect other fields from the browser, such as `userAgent`, `ip` address, and [Facebook's parameters (fbp, fbc)](https://developers.facebook.com/docs/marketing-api/conversions-api/parameters/fbp-and-fbc) and pass them to the server, and manually add them to the events.
 
 #### Deduplication considerations
 
@@ -106,7 +106,7 @@ Use this approach if you don't want to track users from the browser with Faceboo
 
 If you use Facebook Conversions API as a stand-alone without certain data fields collected from the browser, the match rate might not be as high as if you included them.
 
-You can also increase the match rate for events from a server source by sending [user traits in the context object of the track events](/#default-mappings-to-facebook-properties). You can also collect other fields from the browser, such as `userAgent`, `ip` address, and [Facebook's parameters (fbp, fbc)](https://developers.facebook.com/docs/marketing-api/conversions-api/parameters/fbp-and-fbc) and pass them to the server, and manually add them to the events.
+You can also increase the match rate for events from a server source by sending [user traits in the context object of the track events](#default-mappings-to-facebook-properties). You can also collect other fields from the browser, such as `userAgent`, `ip` address, and [Facebook's parameters (fbp, fbc)](https://developers.facebook.com/docs/marketing-api/conversions-api/parameters/fbp-and-fbc) and pass them to the server, and manually add them to the events.
 
 
 #### Deduplication considerations
diff --git a/src/connections/destinations/catalog/google-analytics/index.md b/src/connections/destinations/catalog/google-analytics/index.md
@@ -22,7 +22,7 @@ Different Measurement IDs begin with different prefixes, which indicate which Go
 | UA     | Your global site tag is controlled by Google Analytics. The ID is your Google Analytics Measurement ID. To find the property associated with this ID, use the [account search feature](https://support.google.com/analytics/answer/6100731) in Google Analytics. If the property does not appear, you probably do not have access to it. | [Google Analytics](/docs/connections/destinations/catalog/google-analytics/): Configure ID > Measurement ID           |
 | G      | Your global site tag is controlled by Google Analytics 4 (GA4). The ID is your Google Analytics Measurement ID.       | [Google Analytics](/docs/connections/destinations/catalog/google-analytics/): Configure ID > App + Web Measurement ID |
 | AW     | Your global site tag is controlled by Google Ads. The numeric string following the AW prefix is your Google Ads Conversion ID.        | [Google Ads](/docs/connections/destinations/catalog/google-ads-gtag/): Configure ID > Conversion ID                  |
-| DC     | Your global site tag is controlled by a Floodlight tag. The numeric string following DC is your Advertiser ID.       | [Floodlight](docs/connections/destinations/catalog/doubleclick-floodlight/): Configure ID > App + Web Measurement ID       |
+| DC     | Your global site tag is controlled by a Floodlight tag. The numeric string following DC is your Advertiser ID.       | [Floodlight](/docs/connections/destinations/catalog/doubleclick-floodlight/): Configure ID > App + Web Measurement ID       |
 | other  | Your global site tag is controlled by a different Google product or may be implemented incorrectly. Use the [Tag Assistant extension](https://support.google.com/tagassistant/answer/2947093) for Google Chrome to verify.      | n/a      |
 
 
diff --git a/src/connections/destinations/category-compare.md b/src/connections/destinations/category-compare.md
@@ -9,24 +9,29 @@ This page collates information about each destination, organized by category for
 ## {{ category.display_name }}
 
 <table>
+<tr>
+  <th>  </th>
+  <th colspan=3 style="border-left: 1px solid gray;">Accepts data from these library types in cloud-mode </th>
+  <th colspan=2 style="border-left: 1px solid gray;">Can use these in device-mode</th>
+</tr>
 <tr>
   <th> Destination </th>
-  <th> Cloud - Web </th>
-  <th> Cloud - Mobile </th>
-  <th> Device - Web </th>
-  <th> Device - Mobile </th>
+  <th style="border-left: 1px solid gray;"> Web </th>
+  <th> Mobile </th>
   <th> Server</th>
+  <th style="border-left: 1px solid gray;"> Web </th>
+  <th> Mobile </th>
 </tr>
 {% for destination in site.data.catalog.destinations.items %}
 {% if destination.categories contains category.display_name %}
-{% unless destination.connection_modes.cloud.web == false and destination.connection_modes.cloud.mobile == false and destination.connection_modes.device.web == false and destination.connection_modes.device.mobile == false and destination.connection_modes.cloud.server == false %}
+{% unless destination.connection_modes.cloud.web == false and destination.connection_modes.cloud.mobile == false and destination.connection_modes.cloud.server == false and destination.connection_modes.device.web == false and destination.connection_modes.device.mobile == false  %}
 <tr>
   <td>**[{{ destination.display_name }}](/docs/{{ destination.url }})**</td>
-  <td>{% if destination.connection_modes.cloud.web %}✅{% else %}⬜️{% endif %} </td>
+  <td style="border-left: 1px solid gray;">{% if destination.connection_modes.cloud.web %}✅{% else %}⬜️{% endif %} </td>
   <td>{% if destination.connection_modes.cloud.mobile %}✅{% else %}⬜️{% endif %} </td>
-  <td>{% if destination.connection_modes.device.web %}✅{% else %}⬜️{% endif %} </td>
-  <td>{% if destination.connection_modes.device.mobile %}✅{% else %}⬜️{% endif %} </td>
   <td>{% if destination.connection_modes.cloud.server %}✅{% else %}⬜️{% endif %} </td>
+  <td style="border-left: 1px solid gray;">{% if destination.connection_modes.device.web %}✅{% else %}⬜️{% endif %} </td>
+  <td>{% if destination.connection_modes.device.mobile %}✅{% else %}⬜️{% endif %} </td>
 </tr>
 {% endunless %}
 {% endif %}
diff --git a/src/connections/destinations/cmodes-compare.md b/src/connections/destinations/cmodes-compare.md
@@ -9,31 +9,36 @@ title: Destinations Connection Modes comparison
 > Comparison shopping? Check out the [destination connection modes by category](/docs/connections/destinations/category-compare/).
 
 <table>
+<tr>
+  <th>  </th>
+  <th colspan=3 style="border-left: 1px solid gray;">Accepts data from these library types in cloud-mode </th>
+  <th colspan=2 style="border-left: 1px solid gray;">Can use these in device-mode</th>
+</tr>
 <tr>
   <th> Destination </th>
-  <th> Cloud - Web </th>
-  <th> Cloud - Mobile </th>
-  <th> Device - Web </th>
-  <th> Device - Mobile </th>
+  <th style="border-left: 1px solid gray;"> Web </th>
+  <th> Mobile </th>
   <th> Server</th>
+  <th style="border-left: 1px solid gray;"> Web </th>
+  <th> Mobile </th>
 </tr>
 {% for destination in site.data.catalog.destinations.items %}
 {% unless destination.connection_modes.cloud.web == false and destination.connection_modes.cloud.mobile == false and destination.connection_modes.device.web == false and destination.connection_modes.device.mobile == false and destination.connection_modes.cloud.server == false %}
 <tr>
-  <td>{% if destination.status == "PUBLIC_BETA" %}ℹ️ {% endif %}[{{ destination.display_name }}](/docs/{{ destination.url }})</td>
-  <td>{% if destination.connection_modes.cloud.web %}✅{% else %}⬜️{% endif %} </td>
+  <td>[{{ destination.display_name }}](/docs/{{ destination.url }}){% if destination.status == "PUBLIC_BETA" %}&nbsp;ℹ️{% endif %}</td>
+  <td style="border-left: 1px solid gray;">{% if destination.connection_modes.cloud.web %}✅{% else %}⬜️{% endif %} </td>
   <td>{% if destination.connection_modes.cloud.mobile %}✅{% else %}⬜️{% endif %} </td>
-  <td>{% if destination.connection_modes.device.web %}✅{% else %}⬜️{% endif %} </td>
-  <td>{% if destination.connection_modes.device.mobile %}✅{% else %}⬜️{% endif %} </td>
   <td>{% if destination.connection_modes.cloud.server %}✅{% else %}⬜️{% endif %} </td>
+  <td style="border-left: 1px solid gray;">{% if destination.connection_modes.device.web %}✅{% else %}⬜️{% endif %} </td>
+  <td>{% if destination.connection_modes.device.mobile %}✅{% else %}⬜️{% endif %} </td>
 </tr>
 {% endunless %}
 {% endfor %}
 </table>
 
-The following destinations have no connection mode information available:
+##### The following destinations have no connection mode information available:
 {% for destination in site.data.catalog.destinations.items %}
 {% if destination.connection_modes.cloud.web == false and destination.connection_modes.cloud.mobile == false and destination.connection_modes.device.web == false and destination.connection_modes.device.mobile == false and destination.connection_modes.cloud.server == false %}
-- [{{ destination.display_name }}](/docs/{{ destination.url }}){% if destination.status == "PUBLIC_BETA" %} (beta) {% endif %}
+- [{{ destination.display_name }}](/docs/{{ destination.url }}){% if destination.status == "PUBLIC_BETA" %}&nbsp;ℹ️{% endif %}
 {% endif %}
 {% endfor %}
diff --git a/src/connections/functions/destination-functions.md b/src/connections/functions/destination-functions.md
@@ -194,7 +194,7 @@ If your function fails, you can check the error details and logs in the **Output
 > warning ""
 > Batch handling for Functions is currently available as an early access beta release. By enabling batch handlers for your function, you acknowledge that your use of batch handlers is subject to [Segment’s Beta Terms and Conditions](https://segment.com/legal/first-access-beta-preview), or the applicable terms governing Beta Releases found in your subscription agreement with Segment.
 >
-> If you notice any bugs or have any general feedback on this new feature, contact [beta@segment.com](beta@segment.com).
+> If you notice any bugs or have any general feedback on this new feature, contact [beta@segment.com](mailto:beta@segment.com).
 
 Batch handlers are an extension of destination functions. When you define an `onBatch` handler alongside the handler functions for single events (for example: `onTrack` or `onIdentity`), you're telling Segment that the destination function can accept and handle batches of events.
 
diff --git a/src/connections/sources/catalog/libraries/mobile/android/index.md b/src/connections/sources/catalog/libraries/mobile/android/index.md
@@ -612,7 +612,7 @@ There are two ways to send data to your analytics services through this library:
 
 #### Cloud-Mode in Android
 
-When a destination is enabled for your Android source from the Segment web app, but you haven't packaged its SDK with your app, requests go through the Segment REST API, and are routed to the destination service's API as [described here](/docs/connections/destinations/#connection-modes). Most, but not all destinations offer a cloud-based connection mode, so it's a good idea to [check for destinations that you might _need_ to package](/docs/util/cmodes-compare/).
+When a destination is enabled for your Android source from the Segment web app, but you haven't packaged its SDK with your app, requests go through the Segment REST API, and are routed to the destination service's API as [described here](/docs/connections/destinations/#connection-modes). Most, but not all destinations offer a cloud-based connection mode, so it's a good idea to [check for destinations that you might _need_ to package](/docs/connections/destinations/cmodes-compare).
 
 #### Packaging device-mode destination SDKs
 
diff --git a/src/connections/sources/catalog/libraries/mobile/android/troubleshooting.md b/src/connections/sources/catalog/libraries/mobile/android/troubleshooting.md
@@ -18,8 +18,8 @@ strat: android
 1. Check that the destination is actually enabled in the Segment app.
 2. Check that you entered your credentials for the destination correctly in the Segment app, and that you added them for the correct Source in the correct Workspace.
 3. Make sure the destination can accept the data that you're sending:
-   - Does the [destination support device-mode or cloud-mode support](/docs/utils/cmodes-compare/)? Confirm you are sending using the correct connection mode.
-   - Does the destination [accept the type of call you are sending](/docs/utils/methods-compare/)? Not all destinations accept all calls: page, track, etc.
+   - Does the [destination support device-mode or cloud-mode support](/docs/connections/destinations/cmodes-compare/)? Confirm you are sending using the correct connection mode.
+   - Does the destination [accept the type of call you are sending](/docs/connections/destinations/methods-compare/)? Not all destinations accept all calls: page, track, etc.
 
 
 If you still don't see data getting to your destination, continue debugging based on the type of connection mode, using the sections below.
diff --git a/src/connections/sources/catalog/libraries/website/shopify-littledata/index.md b/src/connections/sources/catalog/libraries/website/shopify-littledata/index.md
@@ -19,7 +19,7 @@ Here's an architecture diagram that shows how the Littledata app mediates data f
 ![](images/littledata_arch.png)
 
 > warning "Note"
-> This integration is maintained by Littledata _and is not supported by Segment directly_. The Littledata app has been reviewed by the Segment team for conformance with Segment's [E-Commerce Spec](/docs/connections/spec/e-commerce/v2/), and is the recommended way of using Segment with Shopify. However, it does require a paid subscription with Littledata, who mediates the connection between Shopify and Segment. [Contact the Littledata Support team](mailto:support@littledata.io) with any questions.
+> This integration is maintained by Littledata _and is not supported by Segment directly_. The Littledata app has been reviewed by the Segment team for conformance with Segment's [E-Commerce Spec](/docs/connections/spec/ecommerce/v2/), and is the recommended way of using Segment with Shopify. However, it does require a paid subscription with Littledata, who mediates the connection between Shopify and Segment. [Contact the Littledata Support team](mailto:support@littledata.io) with any questions.
 
 ## Getting Started
 
diff --git a/src/connections/spec/best-practices-identify.md b/src/connections/spec/best-practices-identify.md
diff --git a/src/segment-app/iam/membership.md b/src/segment-app/iam/membership.md
diff --git a/src/segment-app/iam/roles.md b/src/segment-app/iam/roles.md

Original file line number	Diff line number	Diff line change
`@@ -16,7 +16,7 @@ doc_links:`
`16`	`16`	`url: "/docs/connections/storage/data-lakes/"`
`17`	`17`	`-`
`18`	`18`	`title: Set Up Segment Data Lakes`
`19`		`- url: "docs/connections/storage/catalog/data-lakes"`
	`19`	`+ url: "/docs/connections/storage/catalog/data-lakes"`
`20`	`20`	`# images:`
`21`	`21`	`# -`
`22`	`22`	`# path: images/release-notes/identity-onboarding-1.png`
Original file line number	Diff line number	Diff line change
`@@ -194,7 +194,7 @@ If your function fails, you can check the error details and logs in the **Output`
`194`	`194`	`> warning ""`
`195`	`195`	`> Batch handling for Functions is currently available as an early access beta release. By enabling batch handlers for your function, you acknowledge that your use of batch handlers is subject to [Segment’s Beta Terms and Conditions](https://segment.com/legal/first-access-beta-preview), or the applicable terms governing Beta Releases found in your subscription agreement with Segment.`
`196`	`196`	`>`
`197`		`-> If you notice any bugs or have any general feedback on this new feature, contact [[email protected]]([email protected]).`
	`197`	`+> If you notice any bugs or have any general feedback on this new feature, contact [[email protected]](mailto:[email protected]).`
`198`	`198`
`199`	`199`	Batch handlers are an extension of destination functions. When you define an `onBatch` handler alongside the handler functions for single events (for example: `onTrack` or `onIdentity`), you're telling Segment that the destination function can accept and handle batches of events.
`200`	`200`