Merge pull request #8041 from carlota-moh/develop

rchinn1 · web-flow · commit 8f25616767d7 · 2025-10-14T12:20:22.000-07:00
chore: fixes for batch 7.1
diff --git a/src/connections/destinations/catalog/primer/index.md b/src/connections/destinations/catalog/primer/index.md
@@ -16,8 +16,6 @@ Since Primer needs to be initialized as early as possible, you need to supply th
 
 This will initialize the Primer SDK under the hood and begin collecting events and initializing the Primer Flow.
 
-- - -
-
 Primer supports the `identify` and `track` methods.
 
 ## Identify
diff --git a/src/connections/destinations/catalog/promoter-io/index.md b/src/connections/destinations/catalog/promoter-io/index.md
@@ -11,8 +11,6 @@ hide-dossier: true
 
 Once the Segment library is integrated with your service, add your Promoter API Key and enable Promoter in your Segment destinations page. You can find your API key in Promoter.io under **Accounts Settings > Segment Destination**.
 
-- - -
-
 Promoter supports the `identify` and `track` methods from Segment and will allow you to:
 
 - Add a contact to a list
diff --git a/src/connections/destinations/catalog/quora-conversion-pixel/index.md b/src/connections/destinations/catalog/quora-conversion-pixel/index.md
@@ -13,13 +13,13 @@ id: 5952698570a3e552b9575519
 2. Search for "Quora" in the Catalog, select it, and choose which of your sources to connect the destination to.
 3. Add your Quora Conversion Pixel Key to your Destination settings. To get this you will need to do the following:
 
-	i. Log into your [Quora Ads Manager Account](https://www.quora.com/ads/account){:target="_blank"}.
+   1. Log into your [Quora Ads Manager Account](https://www.quora.com/ads/account){:target="_blank"}.
 
-	ii. Navigate to the "Quora Pixel" tab in your Quora Dashboard.
+   2. Navigate to the "Quora Pixel" tab in your Quora Dashboard.
 
-	iii. Click the "Setup Pixel" button to open the installation popup modal.
+   3. Click the "Setup Pixel" button to open the installation popup modal.
 
-	iv. Under "Option A: Install a JavaScript Pixel," find your Quora Conversion Pixel Key in the Quora JavaScript Pixel - the key is embedded in a tag that looks like `qp('init', '7cc5a029c2604daa8365d15ff337146e')`. In the example below, the key is `7cc5a029c2604daa8365d15ff337146e`.
+   4. Under "Option A: Install a JavaScript Pixel," find your Quora Conversion Pixel Key in the Quora JavaScript Pixel - the key is embedded in a tag that looks like `qp('init', '7cc5a029c2604daa8365d15ff337146e')`. In the example below, the key is `7cc5a029c2604daa8365d15ff337146e`.
 
 
 ## Track
diff --git a/src/connections/destinations/catalog/ramen/index.md b/src/connections/destinations/catalog/ramen/index.md
@@ -2,19 +2,20 @@
 title: Ramen Destination
 id: 558c9d1a0a20f4e22f0fb3bb
 ---
+
 ## Getting Started
 
 When you enable Ramen in the Segment web app, your changes appear in the Segment CDN in about 45 minutes, and then Analytics.js starts asynchronously loading Ramen's JavaScript library onto your page. This means you should remove Ramen's snippet from your page if you already have it there.
-​
-+ As of March 2016, Ramen supports asking questions of anonymous website visitors in addition to logged-in users. Calling [`page`](#page), [`track`](#track), and [`group`](#group) will work without calling [`identify`](#identify). However, when you call [`identify`](#identify) you _must_ pass in an `id` or else the Ramen destination will ignore the call.
-​
-​
+
+- As of March 2016, Ramen supports asking questions of anonymous website visitors in addition to logged-in users. Calling [`page`](#page), [`track`](#track), and [`group`](#group) will work without calling [`identify`](#identify). However, when you call [`identify`](#identify) you _must_ pass in an `id` or else the Ramen destination will ignore the call.
+
 ## Identify
-​
+
 When you make an [Identify call](/docs/connections/spec/identify) on Analytics.js, it identifies the logged-in user to Ramen.
-​
+
 Here is a full example, which we will annotate below:
-​
+
+
 ```javascript
 analytics.identify('314159', {
   email: 'ryan@charturl.com',
@@ -25,26 +26,23 @@ analytics.identify('314159', {
   mrr: 149.99
 });
 ```
-​
+
 Here is a list of the attributes we process:
-​
+
 * `id` becomes the `id` of the user in Ramen.
 * `email` becomes the `email` of the user in Ramen.
 * `name` becomes the `name` of the user in Ramen.
 * `created_at` becomes the `customer_created_at` timestamp for the user in Ramen. It can be passed in as a `Date` or seconds since the epoch.
 * If `company` is an `Object` with an `id` attribute, we'll treat that information as if it was passed to [`group`](#group) and create a company in Ramen.
 * Attributes with names ending in `_at` will be parsed as times.
 * Attributes with names beginning with `is_` will be parsed as Booleans.
-​
-​
+
 **Note:** Ramen will ignore any calls to `identify` that do not contain `userId`.
-​
-​
-​
+
 ## Group
-​
+
 Segment supports Ramen Companies in Analytics.js through the [`group`](/docs/connections/spec/group) method. Users can be put into multiple groups, which will associate them to multiple companies in Ramen.
-​
+
 Here is a full example, which we will annotate below:
 ​
 ```javascript
@@ -57,49 +55,44 @@ analytics.group('314159', {
   mrr: 149.99
 });
 ```
-​
+
 Here is a list of the attributes we process:
-​
+
 * `id` becomes the `id` of the company in Ramen.
 * `url` becomes the `url` of the company in Ramen.
 * `name` becomes the `name` of the company in Ramen.
 * `created_at` becomes the `company_created_at` timestamp for the company in Ramen. It can be passed in as a `Date` or seconds since the epoch.
 * Other attributes can be passed in as well, and will parsed according to the same rules as denoted in the [`identify`](#identify) section.
-​
-​
+
 ## Page
-​
+
 When you call [`page`](/docs/connections/spec/page) on Analytics.js, it registers a new pageview in Ramen and checks to see if any questions should be asked.
-​
+
 Ramen does not support passing in any attributes to `page`. You can call `page({ title: "Our page" })` but the attributes (ie. `title` in this example) will be ignored.
-​
-​
+
 ## Track
-​
+
 When you call [`track`](/docs/connections/spec/track) on Analytics.js, it registers a new event in Ramen and checks to see if any questions should be asked.
-​
+
 Ramen does not support passing in any attributes to `track` beyond the event name. You can call `track('Subscribed', { plan: "Startup" })` but the attributes (ie. `plan` in this example) will be ignored.
-​
-​
-- - -
-​
+
+
 ## Features
-​
-​
+
 ### Secure Mode
-​
+
 If you want to enable Ramen [secure mode](http://docs.ramen.is/#secure-mode){:target="_blank"} for analytics.js, you can pass in the `timestamp` and `auth_hash` variables by rendering it in your server-side templates.
-​
+
 The `timestamp` should be a Unix timestamp (epoch seconds). The `auth_hash` is a SHA256 has of several attributes. The hash is not based on the email, it is based on:
-​
-+ user.email - If you do not store emails for your customers, use an empty string
-+ user.id
-+ user.name - If you do not have a name for your customers, use their email address or an empty string
-+ timestamp
-+ Ramen API Secret
-​
+
+- user.email - If you do not store emails for your customers, use an empty string
+- user.id
+- user.name - If you do not have a name for your customers, use their email address or an empty string
+- timestamp
+- Ramen API Secret
+
 Here's an example of a Ruby web server rendering an identify call with secure mode:
-​
+
 ```ruby
 analytics.identify('<%= current_user.id %>', {
     email   : '<%= current_user.email %>',
@@ -113,31 +106,26 @@ analytics.identify('<%= current_user.id %>', {
     }
 });
 ```
-​
+
 `RAMEN_ORGANIZATION_SECRET_KEY` is found in Ramen's RamenJS documentation.
-​
-​
-- - -
-​
-​
+
 ## Troubleshooting
-​
-​
+
 ### I'm seeing a `404` error
-​
+
 Check to make sure your Ramen `ORGANIZATION_ID` is correct.
-​
+
 ### I'm seeing a `401` error
-​
+
 The request you are sending is not valid. Several things can cause this:
-​
-+ An invalid `user.email`. It can be blank, but it cannot be an invalid email address.
-+ A missing `user.id`.
-+ Not including `timestamp` and `auth_hash` once Secure Mode has been enabled. You can see if Secure Mode is enabled by visiting your RamenJS settings page in Ramen.
-​
+
+- An invalid `user.email`. It can be blank, but it cannot be an invalid email address.
+- A missing `user.id`.
+- Not including `timestamp` and `auth_hash` once Secure Mode has been enabled. You can see if Secure Mode is enabled by visiting your RamenJS settings page in Ramen.
+
 If the above all look correct, and you are sending `timestamp` and `auth_hash`, check the following:
-​
-+ `timestamp` is being dynamically generated (ie. it is not accidentally hard-coded).
-+ `auth_hash` is being calculated correctly
-​
+
+- `timestamp` is being dynamically generated (ie. it is not accidentally hard-coded).
+- `auth_hash` is being calculated correctly
+
 If you are still having trouble, you can email [Ramen support](mailto:support@ramen.is).
diff --git a/src/connections/destinations/catalog/recombee-ai/index.md b/src/connections/destinations/catalog/recombee-ai/index.md
@@ -18,7 +18,6 @@ This destination is maintained by Recombee. For any issues with the destination,
 
 > info ""
 > The Recombee Destination is currently in beta, which means that the Recombee team is still actively developing the destination. If you have any feedback to help improve the Recombee Destination and its documentation, [contact the Recombee support team](mailto:support@recombee.com).
->>>>>>> Stashed changes
 
 Use this Segment destination to send your interaction data, like views, purchases, or plays, to Recombee.
 
diff --git a/src/connections/destinations/catalog/relay/index.md b/src/connections/destinations/catalog/relay/index.md
@@ -7,7 +7,6 @@ title: Relay Destination
 Once the Segment library is integrated with your server, toggle Relay on in your Segment destinations.
 
 Relay supports the `identify` and `track` methods.
-- - -
 
 ## Identify
 
diff --git a/src/connections/destinations/catalog/retina/index.md b/src/connections/destinations/catalog/retina/index.md
@@ -8,7 +8,7 @@ id: 5f287bfa332cce0b1ed18331
 
 Retina AI maintains this destination. For any issues with the destination, contact the [Retina AI Support Team](mailto:info@retina.ai).
 
-> info " "
+> info ""
 > The Retina AI Destination is in beta, which means that they are still actively developing the destination. To join the beta program, or if you have any feedback to help improve the Retina AI Destination and its documentation, contact the [Retina AI Support Team](mailto:info@retina.ai).
 
 
diff --git a/src/connections/destinations/catalog/rollbar/index.md b/src/connections/destinations/catalog/rollbar/index.md
@@ -20,12 +20,12 @@ This feature makes use of JavaScript Source Maps to translate the minified code
 
 2. Provide your source map. There are two ways you can do this:
 
-  a. Automatic download: place a comment like the following at the bottom of your minified JavaScript files:
+   1. Automatic download: place a comment like the following at the bottom of your minified JavaScript files:
 
-  ```
-  //# sourceMappingURL=URL_TO_SOURCE_MAP
-  ```
+   ```
+   //# sourceMappingURL=URL_TO_SOURCE_MAP
+   ```
 
-  b. Upload pre-deploy: at the beginning of your deploy script, upload a source map package using Rollbar's API.
+   2. Upload pre-deploy: at the beginning of your deploy script, upload a source map package using Rollbar's API.
 
   For more detail on providing your source map, checkout [Rollbar's documentation here](https://rollbar.com/docs/source-maps/#step-2-provide-your-source-map){:target="_blank"}.
diff --git a/src/connections/destinations/catalog/route/index.md b/src/connections/destinations/catalog/route/index.md
@@ -10,8 +10,6 @@ Once the Segment library is integrated with your server, toggle Route `on` in yo
 
 Route supports the `identify` and `track` methods.
 
----
-
 ## Identify
 
 When you `identify` a contact, we'll pass that contact's information to Route with `email` as Route's Contact ID. The traits recognized as Route's contact profile fields are:
diff --git a/src/connections/destinations/catalog/salesforce-dmp/index.md b/src/connections/destinations/catalog/salesforce-dmp/index.md
@@ -28,17 +28,17 @@ Next, configure the Destination in the Segment web app:
 
 ### Setting up a Client-Side Web Implementation
 
-3. Get your **Config ID** from your SFDMP console. Log into the
+4. Get your **Config ID** from your SFDMP console. Log into the
    console and go to **Manage** > **Capture** > **Sites**.
    If you don't see this option, contact your SFDMP representative.
 
-4. In the **Sites** tab, locate the site you want to use as the SFDMP destination.
+5. In the **Sites** tab, locate the site you want to use as the SFDMP destination.
    If you haven't created any sites yet, click **Create Site** and go through the options to create a new site.
 
    ![A screenshot of the Manage tab in Salesforce DMP, with the Sites item selected.](images/salesforce-dmp-setup1.png)
 
-5. In the dropdown, find the site tag for the site you want to use. The string you need is under "Config" and will look something like `r0u08k4tz`.
-6. Go back to the Segment App, and navigate to the Salesforce DMP destination you're setting up. Locate the ConfigID setting, and paste the value you found in that field.
+6. In the dropdown, find the site tag for the site you want to use. The string you need is under "Config" and will look something like `r0u08k4tz`.
+7. Go back to the Segment App, and navigate to the Salesforce DMP destination you're setting up. Locate the ConfigID setting, and paste the value you found in that field.
 
 To send client-side events to SFDMP, you must include a SFDMP Config ID and
 SFDMP Namespace in your Segment settings. Segment's UI enforces inclusion of a
@@ -49,14 +49,14 @@ If you don't provide a `namespace` Segment can't pass events downstream to SFDMP
 
 ### Setting up for a Server-Side Implementation
 
-6. To set up SFDMP for a server-side connection, enter your SFDMP `Server-side
+8. To set up SFDMP for a server-side connection, enter your SFDMP `Server-side
    Publisher UUID`. To locate this, Segment recommends that you contact your SFDMP representative. Helpful documentation can be found
    [in the Salesforce Audience Studio Help Center](https://konsole.zendesk.com/hc/en-us/articles/219493027-Mobile-HTTP-API){:target="_blank"}.
-7. Once you've retrieved your `Server-side Publisher UUID`, follow the
+9. Once you've retrieved your `Server-side Publisher UUID`, follow the
    instructions in the Segment SFDMP settings to enter your `Pixel.gif Domain`,
    `Pixel.gif Site` and, optionally, your `Pixel.gif Section` in the correct
    fields.
-8. If you instead want to send your `track` events to SFDMP's
+10. If you instead want to send your `track` events to SFDMP's
    Event.gif endpoint instead of their Pixel.gif endpoint, first disable the
    `Send Server-Side Track Calls to the Pixel.gif Endpoint` (it defaults to on)
    setting in the Segment UI.
@@ -217,7 +217,8 @@ If you see page attributes automatically appended to outbound Pixel.gif calls
 and you're not sure where the attributes came from, then you or someone on
 your team has likely set up page scraping in SFDMP.
 
-Warning: If you decide to rely on SFDMP's page scraping to transmit attributes
+> warning ""
+> If you decide to rely on SFDMP's page scraping to transmit attributes
 to SFDMP rather than adding them as properties to Segment events, you won't
 see these properties in other Segment connections, including in a raw data
 warehouse.
@@ -401,4 +402,4 @@ The value of field `msg.event`.
 
 | Value Passed to Segment | Value Sent to SFDMP |
 |-|-|
-| Any String value (for example, 'Account Created') | event_id: <`id mapped in Event ID Map UI setting`> |
+| Any String value (for example, 'Account Created') | event_id: `<id mapped in Event ID Map UI setting>` |
diff --git a/src/connections/destinations/catalog/salesforce-marketing-cloud/index.md b/src/connections/destinations/catalog/salesforce-marketing-cloud/index.md
@@ -11,8 +11,10 @@ versions:
 Salesforce Marketing Cloud (SFMC) provides digital marketing automation and analytics software and services. Marketers can use this software to create sophisticated multi-channel campaigns using the SFMC [Journey Builder](https://help.salesforce.com/articleView?id=mc_jb_journey_builder.htm&type=5){:target="_blank"}. This is a campaign planning tool that helps you design and automate campaigns that guide customers through their journey with your brand, such as [Weekly Product Summary Emails](https://segment.com/recipes/product-summary-emails-salesforce/){:target="_blank"} that you can enable with Segment.
 
 
-### SFMC details
+## SFMC details
 
+| Feature | Details |
+| ------- | ------- |
 | **Support for Engage**               | Yes                                                                  |
 | **Rate Limits**                        | 20 requests per second                                               |
 | **Identifiers Required**               | `userId` or `email`                                                |
@@ -33,9 +35,9 @@ Segment sends data to SFMC using [Data Extensions](https://help.salesforce.com/a
 
 Before you start working with SFMC, work through the following sections to confirm that the destination will work as you expect, and set up any authentication requirements.
 
-### Confirm that Salesforce Marketing Cloud supports your source type and connection mode
-
+### Confirm support 
 
+Make sure that Salesforce Marketing Cloud supports your source type and connection mode.
 
 ### Grant Segment API access to Salesforce Marketing Cloud
 
@@ -98,7 +100,7 @@ You must create a Data Extension in SFMC to store the Identify calls coming from
     If you send a trait `"nonexistent": "xyz"` with your data, but there's no matching `nonexistent` column in SFMC's table, that trait is ignored.
 - You do not need to create attributes for _all_ of the traits in an Identify call. If you don't need a specific trait in SFMC, don't create an attribute for it, and Segment ignores the trait when it sends data to SFMC.
 - All attributes you create in the Data Extension must be in **Title Case**, regardless of the casing used in your Segment Identify calls. When Segment sends Identify calls to SFMC it first transforms the data to use Title Case, but you still need to set the attributes up in SFMC in the correct format.
-- Set up a Primary Key in the Identify Data Extension called `**Contact Key**`. Segment uses this to link users to SFMC's built-in Contact Key property. This field is populated with `userId`  by default in Identify calls. If no  `userId` exists, Segment uses the `email` instead.
+- Set up a Primary Key in the Identify Data Extension called **`Contact Key`**. Segment uses this to link users to SFMC's built-in Contact Key property. This field is populated with `userId`  by default in Identify calls. If no  `userId` exists, Segment uses the `email` instead.
 - If you want to use this data to send emails or push notifications, check the **Is Sendable** box. (If you need to do this later, the box will be called "Used for Sending".)
 - If you will be using this data to send emails, set up any **Email** attributes so they are of the "EmailAddress" type.
 
diff --git a/src/connections/destinations/catalog/salesforce/index.md b/src/connections/destinations/catalog/salesforce/index.md
@@ -11,11 +11,10 @@ private: true
 > Settings will be migrated automatically, but you must take additional action to ensure the destination is properly enabled.For more information, see [Migrating from Salesforce Classic](/docs/connections/destinations/catalog/actions-salesforce/#migrate-from-salesforce-classic)
 >
 > For questions or issues, or to opt out of the automatic upgrade, contact [friends@segment.com](mailto:friends@segment.com). For more information about Salesforce's deprecation, see their [deprecation notice](https://help.salesforce.com/s/articleView?id=000389618&type=1){:target="_blank"}
-Segment's Salesforce destination allows you to create and store leads and records for other objects in Salesforce Sales Cloud.
-
 
+Segment's Salesforce destination allows you to create and store leads and records for other objects in Salesforce Sales Cloud.
 
-### API Access
+## API Access
 
 Segment uses the Salesforce SOAP API to connect. This API requires the following credentials of a registered Salesforce user:
 - email
diff --git a/src/connections/destinations/catalog/salesmachine/index.md b/src/connections/destinations/catalog/salesmachine/index.md
@@ -19,11 +19,11 @@ _You must add `account_uid` in event parameters to automatically link this pagev
 ## Identify
 
 When you `identify` a user, we'll pass that user's information to Salesmachine.io. For a better experience with Salesmachine.io we encourage you to add at least `name` and `email` traits.
-_You must add `account_uid` in traits to automatically link this user to a Salesmachine.io account.
-_
+_You must add `account_uid` in traits to automatically link this user to a Salesmachine.io account._
+
 ## Track
 
-When you `track` an event, we will send that event to Salesmachine.io.(include details about how that event is sent).
+When you `track` an event, we will send that event to Salesmachine.io. (include details about how that event is sent).
 _You must add `account_uid` in event parameters to automatically link this event to an account. However, if the contact that performed the event has only one account, Salesmachine.io will automatically link the event to his account._
 
 ## Group
diff --git a/src/connections/destinations/catalog/satismeter/index.md b/src/connections/destinations/catalog/satismeter/index.md
diff --git a/src/connections/destinations/catalog/scuba-analytics/index.md b/src/connections/destinations/catalog/scuba-analytics/index.md
diff --git a/src/connections/destinations/catalog/selligent-marketing-cloud/index.md b/src/connections/destinations/catalog/selligent-marketing-cloud/index.md
diff --git a/src/connections/destinations/catalog/selligent/index.md b/src/connections/destinations/catalog/selligent/index.md
