Merge branch 'develop' into link-check-action

Author: markzegarelli

.github/release.yml

@@ -4,6 +4,7 @@ changelog:
       - automated-reposync-pr
       - autoupdate
       - back-end
+      - release
     authors:
       - bot-docsteam
   categories:

lychee-out.txt

@@ -44,6 +44,8 @@ items:
   - Google AdWords New
 - slug: klaviyo
   display_name: Klaviyo
+  previous_names:
+  - Klaviyo
   components:
   - code: 'https://github.com/segment-integrations/analytics.js-integration-klaviyo'
     type: browser

src/_data/catalog/overrides.yml

@@ -114,9 +114,9 @@ items:
     team: false
     business: true
     add-on: true
-- product_display_name: Data Residency
+- product_display_name: Regional Segment
   slug: data-residency
-  plan-note: "Data residency is available to customers on the Business Tier plan."
+  plan-note: "Regional Segment is available to customers on the Business Tier plan."
   plans:
     free: false
     team: false

src/_data/products.yml

@@ -227,8 +227,8 @@ sections:
     title: Integration Error Codes
   - path: /connections/rate-limits
     title: Rate Limits and SLA
-  - path: /connections/data-residency
-    title: Data Residency
+  - path: /connections/regional-segment
+    title: Regional Segment
 - section_title: Personas
   section:
   - path: /personas

src/_data/sidenav/main.yml

@@ -2,7 +2,7 @@
 {% codeexampletab Minified %}
 ```js
 <script>
-  !function(){var analytics=window.analytics=window.analytics||[];if(!analytics.initialize)if(analytics.invoked)window.console&&console.error&&console.error("Segment snippet included twice.");else{analytics.invoked=!0;analytics.methods=["trackSubmit","trackClick","trackLink","trackForm","pageview","identify","reset","group","track","ready","alias","debug","page","once","off","on","addSourceMiddleware","addIntegrationMiddleware","setAnonymousId","addDestinationMiddleware"];analytics.factory=function(e){return function(){var t=Array.prototype.slice.call(arguments);t.unshift(e);analytics.push(t);return analytics}};for(var e=0;e<analytics.methods.length;e++){var key=analytics.methods[e];analytics[key]=analytics.factory(key)}analytics.load=function(key,e){var t=document.createElement("script");t.type="text/javascript";t.async=!0;t.src="https://cdn.segment.com/analytics.js/v1/" + key + "/analytics.min.js";var n=document.getElementsByTagName("script")[0];n.parentNode.insertBefore(t,n);analytics._loadOptions=e};analytics._writeKey="YOUR_WRITE_KEY";analytics.SNIPPET_VERSION="4.13.2";
+  !function(){var analytics=window.analytics=window.analytics||[];if(!analytics.initialize)if(analytics.invoked)window.console&&console.error&&console.error("Segment snippet included twice.");else{analytics.invoked=!0;analytics.methods=["trackSubmit","trackClick","trackLink","trackForm","pageview","identify","reset","group","track","ready","alias","debug","page","once","off","on","addSourceMiddleware","addIntegrationMiddleware","setAnonymousId","addDestinationMiddleware"];analytics.factory=function(e){return function(){var t=Array.prototype.slice.call(arguments);t.unshift(e);analytics.push(t);return analytics}};for(var e=0;e<analytics.methods.length;e++){var key=analytics.methods[e];analytics[key]=analytics.factory(key)}analytics.load=function(key,e){var t=document.createElement("script");t.type="text/javascript";t.async=!0;t.src="https://cdn.segment.com/analytics.js/v1/" + key + "/analytics.min.js";var n=document.getElementsByTagName("script")[0];n.parentNode.insertBefore(t,n);analytics._loadOptions=e};analytics._writeKey="YOUR_WRITE_KEY";analytics.SNIPPET_VERSION="4.15.2";
   analytics.load("YOUR_WRITE_KEY");
   analytics.page();
   }}();
@@ -85,7 +85,7 @@
   };
   analytics._writeKey = 'YOUR_WRITE_KEY'
   // Add a version to keep track of what's in the wild.
-  analytics.SNIPPET_VERSION = '4.13.2';
+  analytics.SNIPPET_VERSION = '4.15.2';
   // Load Analytics.js with your key, which will automatically
   // load the tools you've enabled for your account. Boosh!
   analytics.load("YOUR_WRITE_KEY");

src/_includes/content/snippet-helper.md

@@ -122,7 +122,7 @@ You can add multiple instances of a destination using the Segment Config API. Se
 ### Multi-instance destinations and Device-mode
 
 - **You can connect a source to up to 25 instances of a destination if all of the instances use cloud-mode.** Destinations using cloud-mode receive data directly from the Segment servers.
-- **Mobile sources, and the legacy Project source, can connect to multiple instances of cloud-mode only destinations.** Mobile and Project sources cannot connect to multiple instances of cloud-mode and device-mode destinations.
+- **Mobile sources, and the legacy Project source, can connect to multiple instances of destinations that operate only in cloud-mode.** Mobile and Project sources cannot connect to multiple instances of destinations that operate in both cloud-mode and device-mode.
     - **Warning**: If you bundle one instance of a destination in a mobile source but have other instances of that destination connected to that source you might see unexpected and inconsistent data.
 - **Non-mobile sources can only connect to one *device-mode* instance of a destination, in addition to up to 25 cloud-mode instances.** A web browser sending to a destination in device-mode sends data directly from the user’s browser (instead of through the Segment servers), by bundling a copy of destination’s code with the Segment SDK. Segment can’t bundle multiple copies of the destination SDK and so it can’t send data to multiple instances of the destination from the browser.
 - **You cannot connect a source to more than one instance of a destination that operates in device-mode only**. These destinations can only accept data from code directly on the user’s device, and Segment cannot include duplicates of that code for a single source.

src/connections/destinations/add-destination.md

@@ -15,7 +15,7 @@ redirect_from:
 
 
 > success ""
-> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Braze Segment destination. There's also a page about the [non-Actions Customer.io destination](/docs/connections/destinations/catalog/customer-io/). Both of these destinations receives data _from_ Segment. There's also the [Customer.io source](/docs/connections/sources/catalog/cloud-apps/customer-io/), which sends data _to_ Segment!
+> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Customer.io Segment destination. There's also a page about the [non-Actions Customer.io destination](/docs/connections/destinations/catalog/customer-io/). Both of these destinations receives data _from_ Segment. There's also the [Customer.io source](/docs/connections/sources/catalog/cloud-apps/customer-io/), which sends data _to_ Segment!
 
 ## Benefits of Customer.io (Actions) vs Customer.io classic
 
@@ -54,4 +54,4 @@ Build your own subscription. Combine the supported [triggers](/docs/connections/
 ## Migration from Customer.io classic
 
 Keep the following in mind if you plan to move to Customer.io (Actions) from the classic Customer.io destination.
-{% include components/actions-map-table.html name="customer-io" %}
+{% include components/actions-map-table.html name="customer-io" %}

src/connections/destinations/catalog/actions-customer-io/index.md

@@ -8,6 +8,8 @@ Our Chameleon destination code is open-source on GitHub if you want to [check it
 
 When you enable the Segment direct destination on the [Chameleon dashboard](https://app.trychameleon.com/settings/integrations) we will immediately start receiving your app's user and event data collected by Segment.
 
+You may need to enable your website domain on the [Chameleon Domains Dashboard](https://app.trychameleon.com/settings/domains) to see User events and properties on Chameleon.
+
 ## Identify
 
 This helps you target product tours to specific (segments of) users. You can read more about how to segmentations work in [Chameleon's docs](https://help.trychameleon.com/en/articles/1500422-how-to-create-a-target-audience)

src/connections/destinations/catalog/chameleon/index.md

@@ -150,13 +150,13 @@ Unlike the device-mode destination which runs directly on the device, and which
 You can specify what the event action should be called in the Google Universal Analytics settings. If you don't specify a name, Segment uses a default of event **'User Enriched'**. Since an event category is also required, you can specify which `trait` you want Segment to set this value to. For example, if you send a trait such as `type`, Segment sets the value of `traits.type` as the event category if defined, and if it is not, sets it to the default value **'All'**.
 
 > info ""
-> **Note**: Segment marks enriched user trait events as a **Non Interaction** event. Non-interaction events are available if you're using Google Universal Analytics.
+> **Note**: Segment marks enriched user trait events as a **Non-interaction** event. Non-interaction events are available if you're using Google Universal Analytics.
 
 ### A/B Test Versions to Dimensions
 
 Segment makes it simple to save your A/B testing versions to custom dimensions in Google Universal Analytics by mapping an experiment to a custom dimension in the Google Universal Analytics destination settings.
 
-If you are using Cloud-mode or server-side Google Universal Analytics destinations, you can also send this data automatically using the `experiment_id`, `experiment_name`, `variation_id`, and `variation_name` properties. If both an experiment and variation are defined, then this is sent automatically. Segment uses the ids before using the names. If both an ID and a name exist, Segment sends the ID first. For example, if you an `experiment_id`, an `experiment_name`, and a `variation_name` in a call, only the `experiment_id` and `variation_name` are sent to Google Universal Analytics.
+If you are using cloud-mode or server-side Google Universal Analytics destinations, you can also send this data automatically using the `experiment_id`, `experiment_name`, `variation_id`, and `variation_name` properties. If both an experiment and variation are defined, then this is sent automatically. Segment uses the ids before using the names. If both an ID and a name exist, Segment sends the ID first. For example, if you an `experiment_id`, an `experiment_name`, and a `variation_name` in a call, only the `experiment_id` and `variation_name` are sent to Google Universal Analytics.
 
 When you have an active A/B test on a page, Segment either sets that experiment as a property or a user trait, depending on how you choose to send experiment data to other tools on your A/B testing tool's Segment settings page. The property or trait for A/B test experiments are labeled like the following examples:
 
@@ -254,7 +254,8 @@ Here's an example:
 }
 ```
 
-
+> info ""
+> Enhanced ecommerce events cannot be tagged with the `nonInteraction` flag or Advanced Options. Instead, in device-mode, Segment marks all enhanced ecommerce events as **Non-interaction** events. When you use cloud-mode or server-side, Segment marks the `Order Refunded`, `Promotion Viewed`, `Promotion Clicked`, `Product List Viewed`, and `Product List Filtered` enhanced ecommerce events as **Non-interaction** events. All other enhanced ecommerce events do not include a non-interaction flag.
 
 ## Enabling E-Commerce tracking
 
@@ -865,7 +866,7 @@ Using Segment won't affect your bounce rates in Google Universal Analytics.
 
 If you see your bounce rates drop after installing Segment make sure you don't have multiple copies of the snippet on your page. Also be sure you're not calling `page` more than once when the page loads.
 
-If you call `track` on page load make sure to set `nonInteraction` to `1`. You can also set all events to be non-interactive by default in `Advanced Options`. Read more in the [non-interaction events](#non-interaction-events) docs.
+If you call `track` on page load make sure to set `nonInteraction` to `1`. You can also set all events to be non-interactive by default in Advanced Options. Read more in the [non-interaction events](#non-interaction-events) docs.
 
 
 ### Traffic from Boardman or Segmentio Browser