Merge branch 'develop' into DOCSPLAT-2991-small-fixes

forstisabella · web-flow · commit a0e391848765 · 2025-10-16T13:14:58.000-04:00
diff --git a/src/connections/destinations/catalog/chartbeat/index.md b/src/connections/destinations/catalog/chartbeat/index.md
@@ -4,14 +4,13 @@ id: 54521fd525e721e32a72ee9d
 ---
 Our Chartbeat destination code is open-source on GitHub if you want to [check it out](https://github.com/segment-integrations/analytics.js-integration-chartbeat){:target="_blank"}.
 
-## Getting Started
+## Getting started
 
 When you enable Chartbeat in the Segment web app, your changes appear in the Segment CDN in about 45 minutes, and then Analytics.js starts asynchronously loading `chartbeat.js` onto your page. This means you should remove Chartbeat's snippet from your page.
 + Your Chartbeat real-time dashboard will start showing live concurrent visitors.
 
 Chartbeat is only supported on the client-side.
 
-
 ## Page
 
 The [`page`](/docs/connections/spec/page/) method in Analytics.js will call Chartbeat's `virtualPage` function with either the Url you provide or the current window's pathname. Use the [`page`](/docs/connections/spec/page/) method if you have a one-page app that doesn't reload the browser page between views.
diff --git a/src/connections/destinations/catalog/clicky/index.md b/src/connections/destinations/catalog/clicky/index.md
@@ -8,15 +8,13 @@ id: 54521fd525e721e32a72eea2
 Our Clicky destination code is open-source on GitHub. You can check out the code [in the @segment-integrations/analytics.js-integration-clicky](https://github.com/segment-integrations/analytics.js-integration-clicky){:target="_blank"} repository.
 
 
-## Getting Started
+## Getting started
 
 1. From the Segment web app, click **Catalog**.
 2. Search for "Clicky" in the Catalog, select it, and choose which of your sources to connect the destination to.
 3. In the destination settings, enter your Site ID in the settings. You can find your Site ID under the Preferences of your account.
 4. Segment automatically initializes Clicky's script with your Site ID upon loading analytics.js.
 
-- - -
-
 ## Page
 
 If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like this:
@@ -63,8 +61,6 @@ analytics.track("My Custom Event", {
 
 When you use our [`track`](/docs/connections/spec/track/) method, a goal is created in Clicky. Only the event name and the revenue of the event (if it exists) will be included in the call. Clicky doesn't support any other event properties.
 
-- - -
-
 ## Troubleshooting
 
 ### My visits aren't showing up in Clicky
diff --git a/src/connections/destinations/catalog/clientsuccess/index.md b/src/connections/destinations/catalog/clientsuccess/index.md
@@ -5,7 +5,7 @@ id: 55677dfd0a20f4e22f0fb39a
 ---
 This destination is maintained by ClientSuccess.
 
-## Getting Started (for CSMs)
+## Getting started (for CSMs)
 
 If your engineers have already set up Segment, adding Segment data to ClientSuccess is straightforward. All you need to do is turn on the destination.
 
@@ -17,9 +17,8 @@ To turn on the destination, do the following:
 
 **Note:** Because ClientSuccess focuses on group level events, you must pass group information before your events will show up. If you turn on the ClientSuccess destination in Segment and don't see events in ClientSuccess after 24 hours, it may be that your engineers need to send group information to Segment using Segment's `group` call.
 
-- - -
 
-## Getting Started (for Developers)
+## Getting started (for developers)
 
 ClientSuccess supports the `identify`, `group`, `track`, and `page` methods of Segment.
 
diff --git a/src/connections/destinations/catalog/cubitic/index.md b/src/connections/destinations/catalog/cubitic/index.md
@@ -12,7 +12,6 @@ The Cubitic application key can be obtained by contacting signup@cubitic.io
 
 Cubitic supports the `identify` and `track` methods.
 
-- - -
 
 ## Identify
 
diff --git a/src/connections/destinations/catalog/cxense/index.md b/src/connections/destinations/catalog/cxense/index.md
@@ -17,7 +17,6 @@ To get started with Cxense and Segment, you'll need the following:
 
 Assuming these criteria are met, you can add Cxense as a destination for your desired source in your Segment account.
 
-- - -
 
 ## Page
 
diff --git a/src/connections/destinations/catalog/drip/index.md b/src/connections/destinations/catalog/drip/index.md
@@ -3,7 +3,7 @@ title: Drip Destination
 id: 54521fd525e721e32a72eeaa
 cmode-override: true
 ---
-The Drip destination code is all open-source on GitHub if you want to check it out: [JavaScript](https://github.com/segment-integrations/analytics.js-integration-drip){:target="_blank"},(iOS and Android work using the server destination).
+The Drip destination code is all open-source on GitHub if you want to check it out: [JavaScript](https://github.com/segment-integrations/analytics.js-integration-drip){:target="_blank"}, (iOS and Android work using the server destination).
 
 ## Getting Started
 
diff --git a/src/connections/destinations/catalog/eloqua/index.md b/src/connections/destinations/catalog/eloqua/index.md
@@ -44,7 +44,7 @@ Segment `identify` trait on the left to the Eloqua field on the right:
 | `title`                          | Title        |
 
 Follow the Segment spec to ensure proper mapping of these fields from Segment
-`identify` traits: /docs/connections/spec/identify/#traits.
+`identify` traits: [/docs/connections/spec/identify/#traits](/docs/connections/spec/identify/#traits).
 
 In addition, Segment supports mapping custom `identify` traits to Eloqua custom
 object fields. To do so, you can set up mappings in the settings for your
diff --git a/src/connections/destinations/catalog/evergage/index.md b/src/connections/destinations/catalog/evergage/index.md
@@ -18,7 +18,7 @@ analytics.identify('userId123', {
 });
 ```
 
-A `userId` is required on all `identify` calls sent to Evergage. When you call `identify` Segment will call both `setUser` and `setUserField` in the [Evergage library](https://doc.evergage.com/display/EKB/Send+Data+to+Evergage+via+JavaScript){:target="_blank"} to insert both the `userId` and corresponding user traits into {{ integration.name}}.
+A `userId` is required on all `identify` calls sent to Evergage. When you call `identify` Segment will call both `setUser` and `setUserField` in the [Evergage library](https://doc.evergage.com/display/EKB/Send+Data+to+Evergage+via+JavaScript){:target="_blank"} to insert both the `userId` and corresponding user traits into Evergage.
 
 ## Group
 If you're not familiar with the Segment Specs, take a look to understand what the [Group method](/docs/connections/spec/group/) does. An example call would look like:
@@ -29,7 +29,7 @@ analytics.group('companyId123', {
 });
 ```
 
-A `groupId` is required on all `group` calls sent to Evergage. When you call `group` Segment will call both `setCompany` and `setAccountField` in the [Evergage library](https://doc.evergage.com/display/EKB/Send+Data+to+Evergage+via+JavaScript){:target="_blank"} to insert both the `groupId` and corresponding group traits into {{ integration.name}}.
+A `groupId` is required on all `group` calls sent to Evergage. When you call `group` Segment will call both `setCompany` and `setAccountField` in the [Evergage library](https://doc.evergage.com/display/EKB/Send+Data+to+Evergage+via+JavaScript){:target="_blank"} to insert both the `groupId` and corresponding group traits into Evergage.
 
 ## Track
 If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like:
diff --git a/src/connections/destinations/catalog/firebase/index.md b/src/connections/destinations/catalog/firebase/index.md
@@ -44,7 +44,7 @@ buildscript {
 apply plugin: 'com.google.gms.google-services'
 ```
 
-> warning "Use the `aar` package when adding the Segment-Firebase SDK"
+> warning "Use the aar package when adding the Segment-Firebase SDK"
 > The Firebase SDK requires Android resources which are available on `aar` packages.
 
 
diff --git a/src/connections/destinations/catalog/framed-io/index.md b/src/connections/destinations/catalog/framed-io/index.md
@@ -8,7 +8,6 @@ Once your application is set up and instrumented with Segment, turn on Framed in
 
 Framed supports the `identify` and `track` methods.
 
-- - -
 
 ## Identify
 
diff --git a/src/connections/destinations/catalog/freshsales/index.md b/src/connections/destinations/catalog/freshsales/index.md
@@ -19,7 +19,7 @@ You can use `identify` to create a lead or a contact when a website visitor fill
 ### User ID
 `userId` is a mandatory field which is used to identify the lead or contact in Freshsales. If your user identifier is not email, then email has to be a part of traits.
 
-<pre>
+```json
 {
   "userId": "97980cfea0067",
   "traits": {
@@ -32,11 +32,11 @@ You can use `identify` to create a lead or a contact when a website visitor fill
     }
   }
 }
-</pre>
+```
 
 By default, every `identity` is created as a lead. If you'd like an identity to be a contact, you'd need to pass `fs_contact` as `true` as a part of traits.
 
-<pre>
+```json
 {
   "userId" : "97980cfea0067",
   "traits" : {
@@ -50,7 +50,7 @@ By default, every `identity` is created as a lead. If you'd like an identity to
     }
   }
 }
-</pre>
+```
 
 ### Traits
 `traits` are pieces of information you know about a user that are included in an `identify` method.
@@ -72,7 +72,7 @@ As part of traits, you can send custom fields created in Freshsales by using the
 ### Objects:
 Accounts and Deals associated to a contact or lead can also be updated in Freshsales. The objects company and deal in the identity correspond to the Accounts and Deals in Freshsales. You can pass the `traits` of the company or the deal along with the respective objects in the identity.
 
-```
+```json
 {
   "userId" : "97980cfea0067",
   "traits" : {
@@ -98,7 +98,7 @@ You can track activities of your website visitors. If a user is subscribing to a
 ### Track request payload
 
 
-```
+```json
 {
   "userId" : "john.doe@example.com",
   "event": "Email Bounced",
@@ -120,7 +120,7 @@ When you call a `page` event, we send a pageview to Freshsales. You can send ext
 
 ### Sample Page request payload
 
-```
+```json
 {
   "userId" : "john.doe@example.com",
   "name": "Page view",
diff --git a/src/connections/destinations/catalog/fullstory/index.md b/src/connections/destinations/catalog/fullstory/index.md
@@ -39,7 +39,7 @@ analytics.identify("userId");
 
 In addition, Segment will send over along any traits included in the `identify` call. The example call below would send over both `plan` and `logins`.
 
-```
+```js
 analytics.identify("userId123", {
   plan: "premium",
   logins: 5
@@ -50,7 +50,7 @@ analytics.identify("userId123", {
 
 Both `email` and `displayName` are special traits that will be passed to FullStory to be used in their interface as explained in [FullStory's docs](https://help.fullstory.com/hc/en-us/articles/360020828113){:target="_blank"}. These traits are optional.
 
-```
+```js
 analytics.identify("userId123", {
   email: "john.doe@example.com",
   displayName: "John Doe"
@@ -63,7 +63,7 @@ If you're not familiar with the Segment Specs, take a look to understand what th
 
 An example call would look like:
 
-```
+```js
 analytics.track('Product Purchased', {
     order_ID: '2969302398',
     category: 'boots',
diff --git a/src/connections/destinations/catalog/gauges/index.md b/src/connections/destinations/catalog/gauges/index.md
@@ -10,14 +10,12 @@ This means you should remove Gauges' snippet from your page.
 
 Gauges starts automatically collecting data on your site.
 
-- - -
 
 
 ## Page
 
 When you call [`page`](/docs/connections/spec/page/), we call Gauges' `track` method with no arguments.
 
-- - -
 
 
 ## Troubleshooting
diff --git a/src/connections/destinations/catalog/google-ads-gtag/index.md b/src/connections/destinations/catalog/google-ads-gtag/index.md
@@ -47,7 +47,7 @@ To enable consent mode for your Google Ads (Gtag) destination, you can choose fr
 * **Option 1:**
     1. Set the consent defaults by implementing the `ready()` method to set consent defaults.
 
-          ```
+          ```js
           analytics.ready(function() {
             window.gtag('consent', 'default', {
               'ad_storage': 'granted',
@@ -62,7 +62,7 @@ To enable consent mode for your Google Ads (Gtag) destination, you can choose fr
 
     3. Pass the information to Gtag.js by calling `gtag` inside the Segment `ready`() method. 
 
-          ```
+          ```js
           analytics.ready(function() {
             window.gtag('consent', 'update', {
               'ad_storage': 'denied',
diff --git a/src/connections/destinations/catalog/gosquared/index.md b/src/connections/destinations/catalog/gosquared/index.md
@@ -12,7 +12,6 @@ Your GoSquared Now dashboard will instantly start showing the number of visitors
 
 GoSquared supports mobile, webpage and server-side tracking.
 
-- - -
 
 ## Website Tracking
 
@@ -22,7 +21,6 @@ When you enter your GoSquared site token into Segment, website tracking will aut
 
 To track data using Segment's mobile and server-side sources, you will need to enter a GoSquared API Key, which can be created in your [GoSquared account](https://www.gosquared.com/settings/api){:target="_blank"}. The API Key must have "Write Tracking" access. All functionality is supported by mobile and server-side tracking.
 
-- - -
 
 ## Page
 
diff --git a/src/connections/destinations/catalog/gtag/index.md b/src/connections/destinations/catalog/gtag/index.md
@@ -130,6 +130,8 @@ analytics.track('Logged In');
 
 Segment sends these event attributes to Google Analytics:
 
+| Event Attributes   | Info      |
+| ------------------ | --------- |
 | **Event Category** | All       |
 | **Event Action**   | Logged In |
 
@@ -150,6 +152,8 @@ In this example, Segment sends all Google Analytics event parameters:
 
 Segment sends these event attributes to Google Analytics:
 
+| Event Attributes   | Info      |
+| ------------------ | --------- |
 | **Event Category** | Account   |
 | **Event Action**   | Logged In |
 | **Event Label**    | Premium   |
diff --git a/src/connections/destinations/catalog/hawkei/index.md b/src/connections/destinations/catalog/hawkei/index.md
@@ -70,6 +70,6 @@ You'll want to create events that are part of critical paths in your application
 
 ## Troubleshooting
 
-## AnonymousId
+### AnonymousId
 
 All requests to Hawkei require an `anonymousId` to be set. Segment sets this automatically on client-side libraries, but for server side libraries (php, Ruby etc) this needs to be explicitly set.
diff --git a/src/connections/destinations/catalog/hotjar/index.md b/src/connections/destinations/catalog/hotjar/index.md
@@ -34,19 +34,20 @@ Identify calls that do not have a User ID value will not be sent to Hotjar.
 
 Currently, the Hotjar Identify API **does not** support ingesting values passed as nested objects or lists over your identify Spec:
 
-```js
+```json
 "traits": {
-    "name": "Peter Gibbons",
-    "email": "peter@example.com",
-    "plan": "premium",
-    "logins": 5,
-    "address": {
-      "street": "6th St",
-      "city": "San Francisco",
-      "state": "CA",
-      "postalCode": "94103",
-      "country": "USA"
-    }
+  "name": "Peter Gibbons",
+  "email": "peter@example.com",
+  "plan": "premium",
+  "logins": 5,
+  "address": {
+    "street": "6th St",
+    "city": "San Francisco",
+    "state": "CA",
+    "postalCode": "94103",
+    "country": "USA"
+  }
+}
 ```
 
 In the example above, Hotjar rejects all the values in the `address` field.
@@ -62,8 +63,8 @@ Currently, the Hotjar Events API **does not** support ingesting event properties
 ```js
 analytics.track("Experiment Viewed", {
   experiment_id: "1234",
-  experiment_name: "new_upsell_UX"
-  variation_id: "1234b"
+  experiment_name: "new_upsell_UX",
+  variation_id: "1234b",
   variation_name: "variant"
 });
 ```
diff --git a/src/connections/destinations/catalog/hydra/index.md b/src/connections/destinations/catalog/hydra/index.md
@@ -23,7 +23,7 @@ If you would like to use `track` event data, create a `Segment Product Usage Sca
 
 If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like:
 
-```
+```js
 analytics.identify('userId123', {
   email: 'john.doe@example.com',
   firstName: 'John',
@@ -45,7 +45,7 @@ Identify calls will be sent to Hydra as an `identify` event. Upon receiving an I
 
 If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like:
 
-```
+```js
 analytics.track('Device deploy started',
   "properties": {
     "feature": "Device management",
diff --git a/src/connections/destinations/catalog/impact/index.md b/src/connections/destinations/catalog/impact/index.md
@@ -26,7 +26,6 @@ For tracking on Web, you will need your...
 4. Campaign ID
    Your campaign id will be displayed in the top right corner of your Impact dashboard. It will be the four numbers next to your campaign name.
 
-- - -
 
 ## Track
 
diff --git a/src/connections/destinations/catalog/infinario/index.md b/src/connections/destinations/catalog/infinario/index.md
@@ -40,6 +40,5 @@ The alias call can be used to merge two user identities and their data to one. T
 
 This call is currently only supported partially. Whenever a user is assigned to a group, the properties of this group and the group ID is added to the user's properties. This means there is no support for the user being in multiple groups.
 
-- - -
 
 Read the [Infinario guides](http://guides.infinario.com/){:target="_blank"} to see what can you do with the data you tracked.
diff --git a/src/connections/destinations/catalog/iterable/index.md b/src/connections/destinations/catalog/iterable/index.md
@@ -16,7 +16,6 @@ When you enable the Iterable destination from the Segment app, your data starts
 * [Automatically send a follow up email when your initial email goes unopened](https://segment.com/recipes/iterable-autoresponder-emails-when-unopened/)
 -->
 
-- - -
 
 ## Identify
 
diff --git a/src/connections/destinations/catalog/keen/index.md b/src/connections/destinations/catalog/keen/index.md
@@ -9,7 +9,6 @@ When you enable Keen in the Segment web app, your changes appear in the Segment
 
 Keen is supported on the client side and server side.
 
-- - -
 
 ## Identify
 
diff --git a/src/connections/destinations/catalog/librato/index.md b/src/connections/destinations/catalog/librato/index.md
@@ -9,7 +9,6 @@ When you enable Librato in the Segment web app, your changes appear in the Segme
 
 Librato supports the Segment `track` method for both client-side and server-side.
 
-- - -
 
 ## Track
 
diff --git a/src/connections/destinations/catalog/livechat/index.md b/src/connections/destinations/catalog/livechat/index.md
diff --git a/src/connections/destinations/catalog/marketo/index.md b/src/connections/destinations/catalog/marketo/index.md
diff --git a/src/connections/destinations/catalog/mixpanel/index.md b/src/connections/destinations/catalog/mixpanel/index.md
diff --git a/src/connections/destinations/catalog/olark/index.md b/src/connections/destinations/catalog/olark/index.md
diff --git a/src/connections/destinations/catalog/onesignal/index.md b/src/connections/destinations/catalog/onesignal/index.md
diff --git a/src/connections/destinations/catalog/planhat/index.md b/src/connections/destinations/catalog/planhat/index.md
diff --git a/src/connections/destinations/catalog/preact/index.md b/src/connections/destinations/catalog/preact/index.md
diff --git a/src/connections/destinations/catalog/sailthru/index.md b/src/connections/destinations/catalog/sailthru/index.md
diff --git a/src/connections/sources/catalog/cloud-apps/marketo/index.md b/src/connections/sources/catalog/cloud-apps/marketo/index.md
diff --git a/src/connections/sources/catalog/cloud-apps/zendesk/index.md b/src/connections/sources/catalog/cloud-apps/zendesk/index.md
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

Original file line number	Diff line number	Diff line change
`@@ -12,7 +12,6 @@ The Cubitic application key can be obtained by contacting signup@cubitic.io`
`12`	`12`
`13`	`13`	Cubitic supports the `identify` and `track` methods.
`14`	`14`
`15`		`-- - -`
`16`	`15`
`17`	`16`	`## Identify`
`18`	`17`
Original file line number	Diff line number	Diff line change
`@@ -17,7 +17,6 @@ To get started with Cxense and Segment, you'll need the following:`
`17`	`17`
`18`	`18`	`Assuming these criteria are met, you can add Cxense as a destination for your desired source in your Segment account.`
`19`	`19`
`20`		`-- - -`
`21`	`20`
`22`	`21`	`## Page`
`23`	`22`
Original file line number	Diff line number	Diff line change
`@@ -8,7 +8,6 @@ Once your application is set up and instrumented with Segment, turn on Framed in`
`8`	`8`
`9`	`9`	Framed supports the `identify` and `track` methods.
`10`	`10`
`11`		`-- - -`
`12`	`11`
`13`	`12`	`## Identify`
`14`	`13`