Merge branch 'develop' of github.com:segmentio/segment-docs into develop

markzegarelli · markzegarelli · commit 3a571da0f05a · 2023-01-19T09:16:13.000-08:00
diff --git a/src/connections/destinations/catalog/actions-commandbar/index.md b/src/connections/destinations/catalog/actions-commandbar/index.md
@@ -2,8 +2,6 @@
 title: CommandBar Destination
 hide-boilerplate: true
 hide-dossier: true
-private: true
-hidden: true
 id: 638f843c4520d424f63c9e51
 ---
 
diff --git a/src/connections/destinations/catalog/actions-google-analytics-4/index.md b/src/connections/destinations/catalog/actions-google-analytics-4/index.md
@@ -128,6 +128,10 @@ For a complete map of Universal Analytics functionality to corresponding Google
 
 ## FAQ & Troubleshooting
 
+### Data not sending to Google
+
+Ensure that at least one mapping has been configured and enabled in the destination mappings for an event that you would like to reach Google. Without any mappings enabled to trigger on an event that has been ingested by the connected source, the destination will not send events downstream.
+
 ### Attribution Reporting
 
 Google doesn't currently support passing certain reserved fields to the Google Analytics 4 Measurement Protocol API. This includes attribution data, like UTM parameters. If you rely on attribution reporting, you can either send this data as [custom dimensions](/docs/connections/destinations/catalog/actions-google-analytics-4/#custom-dimensions-and-metrics) or implement a parallel client-side integration to collect this data with gtag.js.
diff --git a/src/connections/destinations/catalog/actions-intercom-cloud/index.md b/src/connections/destinations/catalog/actions-intercom-cloud/index.md
@@ -31,7 +31,7 @@ Intercom Cloud Mode (Actions) provides the following benefits over the classic I
 2. Search for **Intercom Cloud Mode (Actions)** in the Destinations Catalog, and select the destination.
 3. Click **Configure Intercom Cloud Mode (Actions)**.
 4. Select the source that will send data to Intercom Cloud Mode (Actions) and follow the steps to name your destination.
-5. On the **Settings** tab, authenticate with Intercom using OAuth.
+5. On the **Settings** tab, authenticate with Intercom using OAuth. If you have multiple Intercom workspaces, choose one workspace that you'll connect to Segment.
 6. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customize-mappings).
 7. Enable the destination and configured mappings.
 
diff --git a/src/connections/destinations/catalog/matomo/index.md b/src/connections/destinations/catalog/matomo/index.md
@@ -4,7 +4,10 @@ rewrite: true
 redirect_from: '/connections/destinations/catalog/piwik/'
 id: 54521fda25e721e32a72eee7
 ---
-[Matomo](https://matomo.org/), formerly Piwik, is the leading open source web analytics platform that gives you valuable insights into your website's visitors, your marketing campaigns and much more, so you can optimize your strategy and online experience of your visitors.
+[Matomo](https://matomo.org/), formerly Piwik, is the leading open source web analytics platform that gives you valuable insights into your website's visitors, your marketing campaigns and much more, so you can optimize your strategy and online experience of your visitors. 
+
+Segment’s Matomo destination code is open-source and can be viewed on GitHub:
+- [Javascript](https://github.com/segmentio/analytics.js-integrations/blob/master/integrations/piwik/lib/index.js){:target="_blank"}
 
 ## Getting Started
 
diff --git a/src/connections/destinations/catalog/youbora/index.md b/src/connections/destinations/catalog/youbora/index.md
@@ -11,89 +11,39 @@ Youbora automatically starts recording data.
 ## Tracking Video Events
 
 Segment can keep track of events occurring on any number of video players on your
-page. **You must include the `session_id` propert with every video event you want to send to the Youbora so Segment can keep track of which player to attribute the events to.**
+page. **You must include the `session_id` property with every video event you want to send to Youbora so Segment can keep track of which player to attribute the events to.**
 
 
 ### Video Playback Started
 
-When a user starts playback of a video, use the [Video Playback Started](/docs/connections/spec/video/#playback-events) event. Segment maps the properties
-from the Video Playback Started event to the following Youbora video metadata
-fields:
-
-<table>
-    <tr>
-      <td>**Youbora Parameter**</td>
-      <td>**Segment Property**</td>
-      <td>**Data Type**</td>
-    </tr>
-  <tr>
-    <td>'content.isLive'</td>
-    <td>`properties.livestream`</td>
-    <td>Boolean</td>
-  </tr>
-  <tr>
-    <td>Resource</td>
-    <td>`context.page.url`</td>
-    <td>String</td>
-  </tr>
-</table>
+When a user starts playback of a video, use the [Video Playback Started](/docs/connections/spec/video/#playback-events) event. Segment maps the properties from the Video Playback Started event to the following Youbora video metadata fields:
+
+| Youbora Parameter | Segment Property        | Data Type |
+| ----------------- | ----------------------- | --------- |
+| `content.isLive`  | `properties.livestream` | Boolean   |
+| Resource          | `context.page.url`      | String    |
+
 
 ### Video Content Started
 
-When the video content actually begins playing, use the [Video Content
-Started](/docs/connections/spec/video/#content-events) event. Segment maps the properties
-from the Video Playback Started event to the following Youbora video metadata
-fields:
-
-<table>
-    <tr>
-      <td>**Youbora Parameter**</td>
-      <td>**Segment Property**</td>
-      <td>**Data Type**</td>
-    </tr>
-  <tr>
-    <td>'content.title'</td>
-    <td>`properties.title`</td>
-    <td>String</td>
-  </tr>
-  <tr>
-    <td>'content.title2'</td>
-    <td>`properties.program`</td>
-    <td>String</td>
-  </tr>
-  <tr>
-    <td>'content.duration'</td>
-    <td>`properties.total_length`</td>
-    <td>Integer</td>
-  </tr>
-  <tr>
-    <td>'content.metadata.content_id'</td>
-    <td>`properties.asset_id`</td>
-    <td>String</td>
-  </tr>
-  <tr>
-    <td>'content.metadata.genre'</td>
-    <td>`properties.genre`</td>
-    <td>String</td>
-  </tr>
-  <tr>
-    <td>'content.metadata.owner'</td>
-    <td>`properties.publisher`</td>
-    <td>String</td>
-  </tr>
-</table>
-
-Using the difference in time between when `Video Playback Started` and `Video
-Content Started`, Youbora will calculate the join time for you.
+When the video content actually begins playing, use the [Video Content Started](/docs/connections/spec/video/#content-events) event. Segment maps the properties from the Video Playback Started event to the following Youbora video metadata fields:
+
+| Youbora Parameter             | Segment Property          | Data Type |
+|:----------------------------- |:------------------------- |:--------- |
+| `content.title`               | `properties.title`        | String    |
+| `content.title2`              | `properties.program`      | String    |
+| `content.duration`            | `properties.total_length` | Integer   |
+| `content.metadata.content_id` | `properties.asset_id`     | String    |
+| `content.metadata.genre`      | `properties.genre`        | String    |
+| `content.metadata.owner`      | `properties.publisher`    | String    |
+
+Youbora calculates the join time using the time difference between `Video Playback Started` and `Video Content Started`,
 
 ### Video Playback Paused/Resumed
 
-When a user pauses/resumes playback of a video, use the [Video
-Playback Paused](/docs/connections/spec/video/#playback-events) and [Video Playback
-Resumed](/docs/connections/spec/video/#playback-events) events.
+When a user pauses or resumes playback of a video, use the [Video Playback Paused](/docs/connections/spec/video/#playback-events) and [Video Playback Resumed](/docs/connections/spec/video/#playback-events) events.
 
-If the user pauses during an ad, be sure to fill the
-`properties.ad_asset_id` field from our spec for **both** calls, as we use its
+If the user pauses during an ad, fill the `properties.ad_asset_id` field from the spec for **both** calls, as Segment uses its
 presence to determine whether the pause is occurring during an ad or not.
 
 **Example**
@@ -112,11 +62,7 @@ analytics.track('Video Playback Resumed', {
 
 ### Video Playback Seek Started/Completed
 
-When the video content actually begins playing, use the [Video
-Playback Seek Started](/docs/connections/spec/video/#playback-events) and [Video Playback
-Seek Completed](/docs/connections/spec/video/#playback-events) events. Youbora internally
-calculates the duration of the seek but if you would prefer to provide this
-value yourself you can pass it as the integration-specific option `duration`.
+When the video content actually begins playing, use the [Video Playback Seek Started](/docs/connections/spec/video/#playback-events) and [Video Playback Seek Completed](/docs/connections/spec/video/#playback-events) events. Youbora internally calculates the duration of the seek but if you would prefer to provide this value yourself you can pass it as the integration-specific option `duration`.
 
 **Example**
 
@@ -133,10 +79,6 @@ Playback Buffer Started](/docs/connections/spec/video/#playback-events) and [Vid
 Buffer Completed](/docs/connections/spec/video/#playback-events) events. Segment maps the
 properties from these events to the following Youbora video metadata fields:
 
-If the buffer occurs during an ad, be sure to fill the
-`properties.ad_asset_id` field from our spec for **both** calls, as we use its
-presence to determine whether the buffer is occurring during an ad or not.
-
 **Example**
 
 ```js
@@ -145,14 +87,16 @@ analytics.track('Video Playback Buffer Started', { session_id: 1 });
 analytics.track('Video Playback Buffer Completed', { session_id: 1 });
 ```
 
+If the user pauses during an ad, fill the `properties.ad_asset_id` field from the spec for **both** calls, as Segment uses its
+presence to determine whether the pause is occurring during an ad or not.
+
 ### Video Playback Interrupted
 
 When playback of a video is interrupted, use the [Video Playback Interrupted](/docs/connections/spec/video/#playback-events) event.
 
 ### Video Playback Completed
 
-To track the completion of the video playback session, use our [Video
-Playback Completed](/docs/connections/spec/video/#playback-events) event.
+To track the completion of the video playback session, use the [Video Playback Completed](/docs/connections/spec/video/#playback-events) event.
 
 **Example**
 
@@ -165,18 +109,10 @@ analytics.track('Video Playback Completed', { session_id: 1 });
 When an ad begins to load, use the [Video Ad Started](/docs/connections/spec/video/#ad-events) event. Segment maps the properties from
 these events to the following Youbora video metadata fields:
 
-<table>
-    <tr>
-        <td>**Youbora Parameter**</td>
-        <td>**Segment Property**</td>
-        <td>**Data Type**</td>
-    </tr>
-    <tr>
-        <td>'ad.title'</td>
-        <td>`properties.title`</td>
-        <td>String</td>
-    </tr>
-</table>
+| Youbora Parameter | Segment Property   | Data Type |
+| ----------------- | ------------------ | --------- |
+| `ad.title`        | `properties.title` | String    |
+
 
 **Example**
 
@@ -186,8 +122,7 @@ analytics.track('Video Ad Started', { session_id: 1, title: 'Test Ad Title', ad_
 
 ### Video Ad Completed
 
-To track the completion of an ad, use our [Video Ad
-Completed](/docs/connections/spec/video/#ad-events) event.
+To track the completion of an ad, use the [Video Ad Completed](/docs/connections/spec/video/#ad-events) event.
 
 **Example**
 
@@ -214,13 +149,9 @@ Youbora supports automatic video tracking for the following video players:
 - ThePlatform
 - VideoJS
 
-However, note that relying solely on Youbora auto tracking will not send your
-video events to Segment downstream destinations, including a raw data warehouse.
-To track data to downstream tools, we recommend either manually implementing all
-video player events or manually implementing all events alongside Youbora. If
-you employ the latter method, you should indicate explicitly that your Segment
-events should not flow to Youbora (because they've already been auto-tracked by
-the Youbora library).
+However, relying solely on Youbora auto tracking will not send your video events to Segment downstream destinations, including a raw data warehouse. To track data to downstream tools, Segment recommends either manually implementing all video player events or manually implementing all events alongside Youbora.
+
+If you employ the latter method, you should indicate explicitly that your Segment events should not flow to Youbora (because they've already been auto-tracked by the Youbora library).
 
 ```javascript
 analytics.track('Video Playback Started', { // empty properties object
@@ -231,10 +162,9 @@ analytics.track('Video Playback Started', { // empty properties object
 });
 ```
 
-In order to track a player that falls in one of the above categories, follow the
-below steps:
+Use the following steps to track a player that falls in one of the previous categories:
 
-1. Ensure you have the latest snippet on your page (Updated 2/6/18).
+1. Ensure you have the latest snippet on your page.
 2. If your snippet is in the `head` of your page, move it to the very bottom of
    your `body`, right before the `</body>` tag.
 3. Replace the `load` method in your snippet with the following (you can delete
@@ -268,11 +198,9 @@ below steps:
 In the `player` field, pass the video player object, or the ID of the
 video player element in the case of HTML5.
 
-In the `options` field, you can pass options the same way you would pass them
-natively to Youbora as documented
-[here](http://developer.nicepeopleatwork.com/plugins/general/setting-youbora-options/).
+In the `options` field, you can pass options the same way you would [pass them natively to Youbora](http://developer.nicepeopleatwork.com/plugins/general/setting-youbora-options/){:target="_blank"}.
 
-See the below example for what a working implementation looks like:
+The following example shows a working implementation:
 
 ```js
   <script>
diff --git a/src/connections/sources/catalog/cloud-apps/facebook-lead-ads/index.md b/src/connections/sources/catalog/cloud-apps/facebook-lead-ads/index.md
@@ -139,6 +139,8 @@ Log into your downstream tools and check that your events are populating, and co
 
 ### No Data After Updating Credentials
 
-When a connected account changes or updates their credentials, the customer will have to create a new Facebook Lead Ads source. Reauthorization implies that a new token gets generated, but the token is not the sole link between Segment and Facebook. A Segment app is installed onto an FB Account and that will be the sprouting point from where tokens are generated. The reason we can't disconnect and reconnect the CRM on Facebook with reauthorization is because the creation of a new token will mean to invalidate the rest of the tokens attached to the same Facebook account. 
+When you update or change credentials on a connected account, you need to create a new Facebook Lead Ads source to reauthorize Facebook. Reauthorization implies that a new token is generated, but the token is not the only link between Segment and Facebook. 
 
-For example, let's imagine you have a Facebook Account with three accounts: Account A, Account B, and Account C. You connect Segment to all of them and then generate tokens respectively. Later on, you decide for whatever reason to reauthorize the "Account A" page, the other tokens will be invalidated, and the pages will stop working.
+When you connect the Facebook Leads Ads source, a Segment application is installed on the connected Facebook account. If you were to generate a new token on the same source, it would invalidate all other tokens attached to that Facebook account.
+
+For example, if you have a Facebook Account with three accounts: Account A, Account B, and Account C, you can connect Segment to all of them and then generate a token for each account. Later on, if you need to reauthorize the "Account A" page, the tokens for Account B and Account C are invalidated, and the pages stop working.
diff --git a/src/connections/sources/catalog/libraries/mobile/react-native/index.md b/src/connections/sources/catalog/libraries/mobile/react-native/index.md
@@ -72,6 +72,7 @@ To get started with the Analytics for React Native 2.0 library:
     `trackAppLifecycleEvents` | The default is set to `false`. <br> This enables you to automatically track app lifecycle events, such as application installed, opened, updated, backgrounded. Set to true to `true` to track.
     `trackDeepLinks` | The default is set to `false`. <br> This automatically tracks when the user opens the app via a deep link. Set to Enable automatic tracking for when the user opens the app via a deep link.
     `proxy` | The default is set to `undefined`. <br> This is a batch url to post to instead of the default batch endpoint.
+    `collectDeviceId` | The default is set to `fasle`. <br> This automatically adds a `device.Id` property to the context object from the DRM API on Android devices.
 
 ## Set up iOS Deep Link Tracking
 > warning ""
diff --git a/src/connections/sources/catalog/libraries/website/javascript/index.md b/src/connections/sources/catalog/libraries/website/javascript/index.md
@@ -758,6 +758,7 @@ Segment offers video player 'plugins' so you can quickly collect video events us
 
 Analytics.js tracks across subdomains out of the box; all Segment destinations fully support this feature.
 
+To track activity on your subdomains, include the Segment Analytics.js snippet on each subdomain. Segment sets users' `anonymousId` on the top-level domain, so users are tracked across any subdomains.
 
 ## Analytics.js performance
 
diff --git a/src/connections/sources/catalog/libraries/website/javascript/supported-browsers.md b/src/connections/sources/catalog/libraries/website/javascript/supported-browsers.md
@@ -15,10 +15,13 @@ The library is regularly tested and is functional with the following browsers:
 - Microsoft Edge
 - Brave
 
+
 ### Internet Explorer Support
 
 Segment guarantees support for Internet Explorer 11 and later for Analytics.js. Remember that different bundled (device-mode) destinations might have different compatibility guarantees for their own products. Refer to the vendor's documentation to confirm browser compatibility.
 
+> info ""
+> Classic destinations and Analytics.js support Internet Explorer 11, but some Actions destinations are not yet supported. 
 
 ## Tracking Protection (ITP, ETP)
 
diff --git a/src/connections/sources/index.md b/src/connections/sources/index.md
@@ -71,6 +71,12 @@ To create a source:
 4. Enter a name for your source as well as any information on the setup page.
 5. Click **Add Source**.
 
+> info "One source or multiple sources?"
+> Segment suggests that you create one source for each type of data you want to collect. For example, you might have one source for all of your website tracking and a different source for any mobile tracking. Creating one source per data type provides the following benefits:
+> - Debugger ease of use - mixing libraries/sources on a single API key means you’re heavily reliant on filtering to actually test events
+> - Flexibility sending data to different projects - if you want to have different warehouse schemas, analytics projects, etc, having multiple sources would create this separation
+> - More control - as your account grows with the number of destinations you enable, having separate sources allows you to have more control
+
 ## Website libraries
 
 [Analytics.js](/docs/connections/sources/catalog/libraries/website/javascript/), the JavaScript library, is the most powerful way to track customer data from your website. If you're just starting out, Segment recommends it over server-side libraries as the simplest installation for any website.
diff --git a/src/getting-started/02-simple-install.md b/src/getting-started/02-simple-install.md
@@ -76,6 +76,9 @@ That snippet loads Analytics.js onto the page _asynchronously_, so it won't affe
 > note ""
 > **Note:** If you only want the most basic Google Analytics setup you can stop reading right now. You're done! Just toggle on Google Analytics from the Segment App.
 
+> info ""
+> The Segment snippet version history available on [GitHub](https://github.com/segmentio/snippet/blob/master/History.md){:target="_blank"}. Segment recommends that you use the latest snippet version whenever possible.
+
 <br>
 ### Step 2: Identify Users
 <br>
diff --git a/src/profiles/faqs.md b/src/profiles/faqs.md
@@ -47,3 +47,6 @@ If two merged user profiles contain conflicting profile attributes, Segment sele
 ## What identifiers can the merged profile be queried/updated with?
 
 Any of the external IDs can be used to query a profile. When a profile is requested, Segment traverses the merge graph and resolves all merged profiles. The result is a single profile, with the latest state of all traits, events, and identifiers.
+
+### Can ExternalID's be changed or removed from the profiles?
+No. As the Identity Graph uses ExternalIDs, they remain for the lifetime of the user profile.

Original file line number	Diff line number	Diff line change
`@@ -758,6 +758,7 @@ Segment offers video player 'plugins' so you can quickly collect video events us`
`758`	`758`
`759`	`759`	`Analytics.js tracks across subdomains out of the box; all Segment destinations fully support this feature.`
`760`	`760`
	`761`	+To track activity on your subdomains, include the Segment Analytics.js snippet on each subdomain. Segment sets users' `anonymousId` on the top-level domain, so users are tracked across any subdomains.
`761`	`762`
`762`	`763`	`## Analytics.js performance`
`763`	`764`