Merge pull request #8017 from lopenchi/develop

forstisabella · web-flow · commit c9e5cf14676a · 2025-10-08T10:43:29.000-04:00
Small fixes - Batch 2.4
diff --git a/src/connections/sources/catalog/cloud-apps/wootric/index.md b/src/connections/sources/catalog/cloud-apps/wootric/index.md
@@ -24,7 +24,7 @@ Below is a table of events that InMoment sends to Segment. These events will sho
 
 
 | Event Name                      | Description                             |
-| ------------------------------- | --------------------------------------- |  |
+| ------------------------------- | --------------------------------------- |
 | Wootric survey response created | A survey response was created           |
 | Wootric survey response updated | An existing survey response was updated |
 
@@ -33,7 +33,7 @@ Below is a table of events that InMoment sends to Segment. These events will sho
 Below are tables outlining the properties included in the events listed above.
 
 | Property Name | Description                                                           |
-| ------------- | --------------------------------------------------------------------- |  |
+| ------------- | --------------------------------------------------------------------- |
 | channel       | The channel from which the survey was responded like ‘web' or ‘email' |
 | created_at    | The timestamp of when the response was created                        |
 | metric_type   | The mode of the survey like "NPS" or “CSAT”                           |
diff --git a/src/connections/sources/catalog/libraries/mobile/amp/index.md b/src/connections/sources/catalog/libraries/mobile/amp/index.md
@@ -17,14 +17,14 @@ If you're new to [AMP](https://www.ampproject.org){:target="_blank"}, go through
 ### Step 1: Include AMP component
 Before the closing `</head>` tag, include the [`amp-analytics` component](https://www.ampproject.org/docs/reference/components/amp-analytics){:target="_blank"}:
 
-  ```js
+```js
  <script async custom-element="amp-analytics" src="https://cdn.ampproject.org/v0/amp-analytics-0.1.js"></script>
-  ```
+```
 
 ### Step 2: Include Segment analytics
 Within your `<body>` tags, include the following Segment analytics snippet:
 
-  ```html
+```html
 <body>
 <amp-analytics type="segment">
 <script type="application/json">
@@ -37,12 +37,12 @@ Within your `<body>` tags, include the following Segment analytics snippet:
 </script>
 </amp-analytics>
 </body>
-  ```
+```
 Replace `WRITE_KEY` with the write key you obtain from the AMP Source you've set up within the Segment UI.
 
 For sources in [EU workspaces](/docs/guides/regional-segment/), use the following snippet:
 
-  ```html
+```html
 <amp-analytics type="segment">
     <script type="application/json">
     {
@@ -55,7 +55,7 @@ For sources in [EU workspaces](/docs/guides/regional-segment/), use the followin
     }
     </script>
 </amp-analytics>
-  ```
+```
 
 By default, the snippet will automatically fire a page event which you can read more about [in the Page section of this documentation](/docs/connections/sources/catalog/libraries/mobile/amp/#page).
 
@@ -66,7 +66,7 @@ The Page method lets you record page views on your website, along with your choi
 
 A `page` call is included by default when you include Segment Analytics into your code with the ability to customize the `name` of your page:
 
-  ```html
+```html
 <amp-analytics type="segment">
 <script type="application/json">
   {
@@ -77,15 +77,15 @@ A `page` call is included by default when you include Segment Analytics into you
   }
 </script>
 </amp-analytics>
-  ```
+```
 
 ## Track
 
 The Track method (referred to as `click` in AMP) lets you record any actions your users perform.
 
 In order to track these `click` events simply add a trigger with a `selector`, which behaves the same way as [CSS Selectors](https://www.w3schools.com/cssref/css_selectors.asp){:target="_blank"}, which will send that event once the user clicks:
 
-  ```html
+```html
 <body>
 <amp-analytics type="segment">
 <script type="application/json">
@@ -109,15 +109,15 @@ In order to track these `click` events simply add a trigger with a `selector`, w
 </amp-analytics>
 <button class="read-more-button">Read More</button>
 </body>
-  ```
+```
 
 ## Properties
 
 ### Default properties
 
 A few properties are automatically collected with each page view and track call:
 
-  ```json
+```json
 {
   "anonymousId": "amp-<unique-id>",
   "context.locale": "en-US",
@@ -128,13 +128,13 @@ A few properties are automatically collected with each page view and track call:
   "context.screen.width": 600,
   "context.screen.height": 800
 }
-  ```
+```
 
 ### Custom properties
 
 If you would like to collect additional, custom properties, include an `extraUrlParams` object. All properties you'd like to include must follow the format of `properties.<property_name>`:
 
-  ```html
+```html
 <amp-analytics type="segment">
 <script type="application/json">
   {
@@ -152,7 +152,7 @@ If you would like to collect additional, custom properties, include an `extraUrl
   }
 </script>
 </amp-analytics>
-  ```
+```
 
 ### UTM parameters
 
@@ -226,4 +226,3 @@ For further details refer to the various `Client ID` scenarios in relation to AM
 <!-- TODO: the product linked above was deprecated, need to find a replacement or hide this page --->
 
 See a live <a href="https://segment-amp.firebaseapp.com">AMP with Segment analytics</a>
-<link rel="amphtml" href="https://segment-amp.firebaseapp.com">
diff --git a/src/connections/sources/catalog/libraries/mobile/android/wear.md b/src/connections/sources/catalog/libraries/mobile/android/wear.md
@@ -82,12 +82,21 @@ analytics.track("Purchased Item", new Properties().putValue("sku", "13d31").putR
 ```
 
 <table class="api-table">
+  <thead>
+    <tr>
+      <td>Field</td>
+      <td>Type</td>
+      <td>Description</td>
+    </tr>
+  </thead>
   <tr>
-    <td>`name` _String,required_</td>
+    <td>`name`</td>
+    <td>_String,required_</td>
     <td>A name for the tracked action.</td>
   </tr>
   <tr>
-    <td>`properties` _Properties,optional_</td>
+    <td>`properties`</td>
+    <td>_Properties,optional_</td>
     <td>A map of properties for this action, e.g. revenue if the action was a purchase.</td>
   </tr>
 </table>
@@ -106,16 +115,26 @@ analytics.screen("Purchase Screen", "Smartwatches", new Properties().putValue("s
 ```
 
 <table class="api-table">
+  <thead>
+    <tr>
+      <td>Field</td>
+      <td>Type</td>
+      <td>Description</td>
+    </tr>
+  </thead>
   <tr>
-    <td>`name` _String,optional*_</td>
+    <td>`name`</td>
+    <td>_String,optional*_</td>
     <td>A name for the screen. Optional if category is provided.</td>
   </tr>
   <tr>
-    <td>`category` _String,optional*_</td>
+    <td>`category`</td>
+    <td>_String,optional*_</td>
     <td>A category for the screen. Optional if name is provided.</td>
   </tr>
   <tr>
-    <td>`properties` _Properties,optional_</td>
+    <td>`properties`</td>
+    <td>_Properties,optional_</td>
     <td>A map of properties for this screen.</td>
   </tr>
 </table>
diff --git a/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/1flow-swift.md b/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/1flow-swift.md
@@ -30,7 +30,7 @@ You'll then have the option to pin to a version, or specific branch, as well as
 
 Open your Package.swift file and add the following to the `dependencies` section:
 
-```
+```swift
 .package(
             name: "Segment",
             url: "https://github.com/1Flow-Inc/segment-1flow-ios.git",
@@ -42,14 +42,14 @@ Open your Package.swift file and add the following to the `dependencies` section
 
 Open the file where you set up and configure the Analytics-Swift library.  Add this plugin to the list of imports.
 
-```
+```swift
 import Segment
 import SegmentOneFlow // <-- Add this line
 ```
 
 Just under your Analytics-Swift library setup, call `analytics.add(plugin: ...)` to add an instance of the plugin to the Analytics timeline.
 
-```
+```swift
 let analytics = Analytics(configuration: Configuration(writeKey: "<YOUR WRITE KEY>")
                     .flushAt(3)
                     .trackApplicationLifecycleEvents(true))
diff --git a/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/adjust-swift.md b/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/adjust-swift.md
@@ -30,7 +30,7 @@ You'll then have the option to pin to a version, or specific branch, as well as
 
 Open your Package.swift file and add the following do your the `dependencies` section:
 
-```
+```swift
 .package(
             name: "Segment",
             url: "https://github.com/segment-integrations/analytics-swift-integration-adjust.git",
@@ -41,14 +41,14 @@ Open your Package.swift file and add the following do your the `dependencies` se
 
 Open the file where you setup and configure the Analytics-Swift library.  Add this plugin to the list of imports.
 
-```
+```swift
 import Segment
 import SegmentAdjust // <-- Add this line
 ```
 
 Just under your Analytics-Swift library setup, call `analytics.add(plugin: ...)` to add an instance of the plugin to the Analytics timeline.
 
-```
+```swift
 let analytics = Analytics(configuration: Configuration(writeKey: "<YOUR WRITE KEY>")
                     .flushAt(3)
                     .trackApplicationLifecycleEvents(true))
@@ -133,4 +133,4 @@ The destination automatically forwards push notification tokens through to Adjus
 
 ### Event buffering
 
-By default, our destination enables event buffering for Adjust. This saves your customers' battery life. However, you can disable this in the options on the Adjust destination settings on Segment.
+By default, our destination enables event buffering for Adjust. This saves your customers' battery life. However, you can disable this in the options on the Adjust destination settings on Segment.
diff --git a/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/adobe-swift.md b/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/adobe-swift.md
@@ -12,7 +12,7 @@ Adobe Analytics uses a slightly different approach to tracking than Segment, and
 
 For example, if one of your end users dismissed a welcome dialog in your app, Segment would generate a `Welcome Dialog Dismissed` event with properties that contain the user ID (`user123`) and the dialog name (`welcome-dialog`), while Adobe Analytics would model the same action as a pageView with variables that represent the dialog name, visitorID, and the event name, and an eVar ("dismissed").
 
-Both Segment and Adobe Analytics have recommended standard data for tracking events. Segment has [the Spec](/docs/connections/spec/), and Adobe uses predefined events. Segment automatically maps incoming event data and some product level properties to Adobe's predefined events, when the event data is in the correct Segment Ecommerce Spec](/docs/connections/spec/ecommerce/v2/) format. Video calls using the format described in [this document](/docs/connections/spec/video) are also automatically mapped. If you're using the Mobile SDKs, mobile lifecycle events are also automatically mapped. If you need to create Page and Track events that are outside the scope of the Ecommerce Spec, you need to map those in your Segment destinations settings UI.
+Both Segment and Adobe Analytics have recommended standard data for tracking events. Segment has [the Spec](/docs/connections/spec/), and Adobe uses predefined events. Segment automatically maps incoming event data and some product level properties to Adobe's predefined events, when the event data is in the correct [Segment Ecommerce Spec](/docs/connections/spec/ecommerce/v2/) format. Video calls using the format described in [this document](/docs/connections/spec/video) are also automatically mapped. If you're using the Mobile SDKs, mobile lifecycle events are also automatically mapped. If you need to create Page and Track events that are outside the scope of the Ecommerce Spec, you need to map those in your Segment destinations settings UI.
 
 Segment strongly recommends that you create a [Tracking Plan](/docs/protocols) for both your Segment and Adobe Analytics events before you send any events or properties to Adobe. This helps you map your Segment events to Adobe `events` and Segment properties to Adobe variables. If you decide to set up Adobe Analytics for mobile, you must set up this mapping in both the Segment settings and the Adobe Mobile Services dashboard, so it's good to stay consistent.
 
@@ -44,7 +44,7 @@ You then have the option to pin to a version or specific branch and select which
 
 Open your Package.swift file and add the following to the `dependencies` section:
 
-```
+```swift
 .package(
             name: "Segment",
             url: "https://github.com/segment-integrations/analytics-swift-adobe-analytics.git",
@@ -56,14 +56,14 @@ Open your Package.swift file and add the following to the `dependencies` section
 
 Open the file where you set up and configured the Analytics-Swift library.  Add this plugin to the list of imports.
 
-```
+```swift
 import Segment
 import SegmentAdobe // <-- Add this line
 ```
 
 Just under your Analytics-Swift library setup, call `analytics.add(plugin: ...)` to add an instance of the plugin to the Analytics timeline.
 
-```
+```swift
 let analytics = Analytics(configuration: Configuration(writeKey: "<YOUR WRITE KEY>")
                     .flushAt(3)
                     .trackApplicationLifecycleEvents(true))
diff --git a/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/mixpanel-swift.md b/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/mixpanel-swift.md
@@ -82,9 +82,13 @@ The first thing you'll want to do is to identify your users so Mixpanel knows wh
 
 As soon as you have a `userId` for a visitor that was previously anonymous you'll need to [`alias`](/docs/connections/spec/alias/) their old anonymous `id` to the new `userId`. In Mixpanel only **one** anonymous user history can be merged to **one** identified user. For that reason you should only call `alias` once, right after a user registered, but before the first `identify`.
 
- When you call the Identify method from the client in either a browser using Analytics.js or one a mobile SDKs, several things occur: Segment recognizes and translates the [special traits](/docs/connections/spec/identify/#traits) so that they fit the expectations of Mixpanel's API. The table below shows the mappings. Pass the key on the left and Segment transforms it to the key on the right before sending to Mixpanel.
+When you call the Identify method from the client in either a browser using Analytics.js or one a mobile SDKs, several things occur: Segment recognizes and translates the [special traits](/docs/connections/spec/identify/#traits) so that they fit the expectations of Mixpanel's API. The table below shows the mappings. Pass the key on the left and Segment transforms it to the key on the right before sending to Mixpanel.
 
 <table>
+  <tr>
+    <td>Key</td>
+    <td>Segment transformation</td>
+  </tr>
   <tr>
     <td>`created`</td>
     <td>`$created`</td>
diff --git a/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/nielsen-dtvr-swift.md b/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/nielsen-dtvr-swift.md
@@ -15,7 +15,7 @@ To get started with Nielsen-DTVR and retrieve an `appid` to configure this integ
 - Reach out to your Segment customer service representative to enable the Nielsen-DTVR plugin, as this destination is in private beta.
 
 
-### Adding the dependency
+## Adding the dependency
 
 ### via Xcode
 In the Xcode `File` menu, click `Add Packages`.  You'll see a dialog where you can search for Swift packages.  In the search field, enter the URL to this repo.
