Merge pull request #2090 from segmentio/develop

Release 21.44.1

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

@@ -46,7 +46,7 @@ sections:
   - path: /connections/destinations/catalog/firebase
     title: Google Firebase (mobile analytics) destination
   - path: /connections/destinations/catalog/google-analytics
-    title: Google Analytics destination
+    title: Google Universal Analytics destination
   - path: /connections/destinations/catalog/google-analytics/ga4-plans
     title: Google Analytics 4 destination
   - path: /connections/destinations/catalog/google-tag-manager

src/_data/sidenav/strat.yml

@@ -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

@@ -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

@@ -4,7 +4,7 @@ hide-personas-partial: true
 cmode-override: true 
 ---
 
-When you enable the Iterable destination from the Segment app, your data starts flowing into Iterable, where it can trigger workflows and make data available for analytics. You can find your Iterable API key by going to Destinations → API Keys inside the Iterable app.
+When you enable the Iterable destination from the Segment app, your data starts flowing into Iterable, where it can trigger workflows and make data available for analytics. You can find or generate your Iterable API key by going to Integrations → API keys inside the Iterable app.
 
 <!-- LR 8/7/2020 these are all 404ing, commenting out until we can figure out if they're gone or just moved
 **Use Cases**

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

@@ -17,7 +17,7 @@ To upgrade a source to Analytics.js 2.0:
 6. Open the Debugger to ensure that events are flowing as expected.
 
 > info ""
-> If you set `'Segment.io:' false' in the integrations object, Analytics.js 2.0 drops the event before it reaches the Source Debugger. 
+> If you set `'Segment.io:' false` in the integrations object, Analytics.js 2.0 drops the event before it reaches the Source Debugger. 
 
 ## Automatic migration
 
@@ -34,7 +34,7 @@ Analytics.js sources will upgrade to Analytics.js 2.0 on the date below, accordi
 
 ## Revert to Analytics.js Classic
 
-Once a source moves to Analytics.js 2.0, you can follow the steps above in [Manual migration](#manual-migration) back to roll back to Analytics.js Classic.
+Once a source moves to Analytics.js 2.0, you can follow the steps above in [Manual migration](#manual-migration) to roll back to Analytics.js Classic.
 
 ## Cases that require additional intervention