Release 23.20.1 (#4743)

* Tracking Plan implememneted

* Update faq.md

* Add info about properties with the "\" character

* Fix typo

* Add navattic source doc

* minor tweaks from inkit

* Open Navattic site in new tab

Co-authored-by: stayseesong <[email protected]>

* Specify support team as Navattic

Co-authored-by: stayseesong <[email protected]>

* Delete quote block that was supposed to be deleted

Co-authored-by: stayseesong <[email protected]>

* Describe steps to Add source

Instead of using hyperlink

Co-authored-by: stayseesong <[email protected]>

* Apply wording suggestion

Co-authored-by: stayseesong <[email protected]>

* Apply wording suggestion

Co-authored-by: stayseesong <[email protected]>

* Apply wording suggestion

Co-authored-by: stayseesong <[email protected]>

* Apply wording suggestion

Co-authored-by: stayseesong <[email protected]>

* Apply wording suggestion

Co-authored-by: stayseesong <[email protected]>

* Use markdown table

Co-authored-by: stayseesong <[email protected]>

* Apply wording suggestion

Co-authored-by: stayseesong <[email protected]>

* Apply wording suggestion

* Remove HTML table

Co-authored-by: stayseesong <[email protected]>

* Use markdown table for property name/description

Co-authored-by: stayseesong <[email protected]>

* Remove HTML table for properties

Co-authored-by: stayseesong <[email protected]>

* Apply syntax suggestion

Co-authored-by: stayseesong <[email protected]>

* Update faq.md

* Mixpanel Cohorts update

* Add Selective Sync

* Update intro and other edits

* Update debugger.md

Added information that the source should not be disabled also.

Original sentence:
This automatically generated source cannot be deleted even when the destination is removed, in order for Segment to function as designed. The source will be reused by Segment as needed.

Added "and should not be disabled" and modified to:
This automatically generated source cannot be deleted and should not be disabled even when the destination is removed, in order for Segment to function as designed. The source will be reused by Segment as needed.

* Fixed Typo

* [netlify-build]

* 1

* update name per partner request

* article edits and casing fixes

* Update src/connections/destinations/catalog/userpilot/index.md

* Update index.md

* Update index.md

* edits

* Engineer feedback

* Update src/unify/profiles-sync/index.md

Co-authored-by: pwseg <[email protected]>

* Remove grammatical error

* Note to add destinations in Engage (#4661)

* Note to add destinations in Engage

Many clients are confused when adding this Engage destination as they add them through connections instead of inside the Engage space

* Update src/connections/destinations/catalog/personas-facebook-custom-audiences/index.md

---------

Co-authored-by: markzegarelli <[email protected]>

* go GA with @segment/analytics-node (#4675)

* go GA with @segment/analytics-node

* Update src/connections/sources/catalog/libraries/server/node/classic.md

Co-authored-by: forstisabella <[email protected]>

---------

Co-authored-by: markzegarelli <[email protected]>
Co-authored-by: forstisabella <[email protected]>

* Add `List Members` collection to public docs (#4692)

* Add List Members Collection to docs - Update index.md

Added the list members collection to the docs, as success eng is able to manually sync this collection for customer.

Relevant JIRA: https://segment.atlassian.net/browse/SRC-364

* Update index.md

edit list members collection

* Revert "go GA with @segment/analytics-node (#4675)" (#4695)

This reverts commit e7e06de.

* Update and rename persistence.md to cookie validity update.md

* Update Object API FAQ to point to Reverse ETL

* Fix Stream Page Typos

* Update email and sms subscription field.md

These fields need double underscores instead of just 1.

* Update cookie validity update.md

* Fix Broken Link #4691

* Update src/connections/sources/catalog/cloud-apps/mixpanel-cohorts/index.md

Co-authored-by: markzegarelli <[email protected]>

* Apply suggestions from code review

Co-authored-by: pwseg <[email protected]>

* Usermaven Deploy branch (#4656)

* feat: usermaven destination docs

* feat: usermaven destination docs

* feat: updated usermaven doc

* Add id and metadata

* Apply suggestions from code review

Co-authored-by: forstisabella <[email protected]>

---------

Co-authored-by: seeratawan01 <[email protected]>
Co-authored-by: forstisabella <[email protected]>

* add `>` to render code snippet correctly

* Update src/protocols/faq.md

* Update src/connections/sources/catalog/cloud-apps/navattic/index.md

Co-authored-by: pwseg <[email protected]>

* catalog update (#4702)

* Add info about Event Names (#4688)

* Add info about Event Names 

Add clarification on the dropdown selector given to customers when they search for event names in the Transformations page.

* Update src/protocols/transform/index.md

Co-authored-by: forstisabella <[email protected]>

---------

Co-authored-by: markzegarelli <[email protected]>
Co-authored-by: forstisabella <[email protected]>

* Updating Mixpanel Public Doc Link 

link for Identity Merge Feature was broken. Updated with new link confirmed by Mixpanel team

* Add Link Shortening content

* [braze-cohorts] update instructions for multi mapping setup

* Adding  CleverTap to the list of supported plugin

* PM feedback

* apply suggestions from code review

* Add fetch-retry dependency

* moved to be in alphabetical order

* Update cookie validity update.md

* Change code to stop reference array being cleared

Changing code to avoid bad behavior

* Update cookie validity update.md

Commented out "7 days"

* feat: add "Spec: Alias" to navbar

* small edit

* fix: remove trailing whitespaces

* change via to through

* catalog update

* Updated AWS S3 language

* Update index.md (#4218)

* GA4 handling null/object/array types event parameters (#4075)

Update from engineers on how GA4 & Segment handles null/object/array types event parameters
in Slack : #integrations-actions-collab (https://twilio.slack.com/archives/C01RWN725QW/p1674000598496369)

Co-authored-by: markzegarelli <[email protected]>

* change name to remove IO

* add test message content

* [netlify-build]

* Update SMS campaigns

* Update src/connections/sources/catalog/libraries/website/javascript/cookie validity update.md

* edits

* Add redirect for name update

* Add callout for ROW UI update

* rephrase as per review comment

* fix: typo

* Update source name

* Add note about Marketo's Lead Activity Type IDs field (#4730)

* Add note about Marketo's Lead Activity Type IDs field

* Update src/connections/sources/catalog/cloud-apps/marketo/index.md

Co-authored-by: forstisabella <[email protected]>

---------

Co-authored-by: forstisabella <[email protected]>

* Add note about Talon.One rate limit (#4729)

* Add note that Help Scout OAuth supports one destination per user (#4728)

* Removed outdated info (#4741)

* add new events for braze (#4727)

* add new events for braze

* add consistent punctuation

* Catalog update

* Add PM feedback

---------

Co-authored-by: Jazma Foskin <[email protected]>
Co-authored-by: Sarah Rudy <[email protected]>
Co-authored-by: Albert Yu <[email protected]>
Co-authored-by: Thomas Gilbert <[email protected]>
Co-authored-by: Albert Yu <[email protected]>
Co-authored-by: stayseesong <[email protected]>
Co-authored-by: rchinn-segment <[email protected]>
Co-authored-by: tanjinhong72 <[email protected]>
Co-authored-by: rchinn-segment <[email protected]>
Co-authored-by: stayseesong <[email protected]>
Co-authored-by: pwseg <[email protected]>
Co-authored-by: Esteban Gonzalez Corti <[email protected]>
Co-authored-by: Seth Silesky <[email protected]>
Co-authored-by: forstisabella <[email protected]>
Co-authored-by: Charity Holt <[email protected]>
Co-authored-by: vanand17 <[email protected]>
Co-authored-by: pwseg <[email protected]>
Co-authored-by: seeratawan01 <[email protected]>
Co-authored-by: prigiattiperrut <[email protected]>
Co-authored-by: Sena Diaz <[email protected]>
Co-authored-by: Varadarajan V <[email protected]>
Co-authored-by: Niall Brennan <[email protected]>
Co-authored-by: Gustavo Carvalho <[email protected]>
Co-authored-by: bobbyatsegment <[email protected]>
Co-authored-by: Liz Kane <[email protected]>
Co-authored-by: Varadarajan V <[email protected]>
Co-authored-by: Sayan Das <[email protected]>
Co-authored-by: Thomas Gilbert <[email protected]>

Author: 24 people

src/_data/catalog/destinations.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2023-05-11 
+# destination data last updated 2023-05-16 
 items:
 - id: 637e8d185e2dec264895ea89
   display_name: 1Flow
@@ -7366,7 +7366,7 @@ items:
   logo:
     url: https://cdn.filepicker.io/api/file/RO2CSvXiRZyZWIoUuh6A
   mark:
-    url: https://cdn.filepicker.io/api/file/lDwvVrfTG6yHeZnaV2QX
+    url: https://cdn.filepicker.io/api/file/d5US10rDRAm3rBJDHqDh
   methods:
     track: true
     identify: true
@@ -7435,7 +7435,7 @@ items:
   logo:
     url: https://cdn.filepicker.io/api/file/IBwccHUASduVLs7bXegV
   mark:
-    url: https://cdn.filepicker.io/api/file/0tjr8XfET0OWi2NbCskz
+    url: https://cdn.filepicker.io/api/file/ocZ7wHLeQBOd77n6zcoQ
   methods:
     track: true
     identify: true
@@ -16907,23 +16907,26 @@ items:
   actions: []
   presets: []
 - id: 5c6ef3322a6fb40001a71bf7
-  display_name: Dreamdata IO
-  name: Dreamdata IO
-  slug: dreamdata-io
+  display_name: Dreamdata
+  name: Dreamdata
+  slug: dreamdata
   hidden: false
   endpoints:
   - US
   regions:
   - us-west-2
   - eu-west-1
-  url: connections/destinations/catalog/dreamdata-io
+  url: connections/destinations/catalog/dreamdata
   previous_names:
   - Dreamdata IO
+  - Dreamdata
   website: https://dreamdata.io
   status: PUBLIC
   categories:
   - Analytics
   - Attribution
+  - Marketing Automation
+  - Enrichment
   logo:
     url: https://cdn.filepicker.io/api/file/Z2uDA7FHQ5CwYnWt19q6
   mark:
@@ -37733,6 +37736,8 @@ items:
   status: PUBLIC
   categories:
   - Analytics
+  - Customer Success
+  - CRM
   logo:
     url: https://cdn.filepicker.io/api/file/Q5TSybewRSzQzcZDfPA3
   mark:
@@ -37789,6 +37794,7 @@ items:
   categories:
   - Analytics
   - Customer Success
+  - CRM
   logo:
     url: https://cdn.filepicker.io/api/file/TB0L1UOTomfISjZcOi2I
   mark:

src/_data/catalog/destinations_private.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2023-05-11 
+# destination data last updated 2023-05-16 
 items:
   - id: 54521fd725e721e32a72eec1
     display_name: HubSpot

src/_data/catalog/regional-supported.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED LIST OF CONNECTIONS THAT SUPPORT REGIONAL
-# Last updated 2023-05-11 
+# Last updated 2023-05-16 
 warehouses:
   - id: WcjBCzUGff
     display_name: Azure SQL Data Warehouse
@@ -449,6 +449,15 @@ sources:
     endpoints:
       - us
       - eu
+  - id: 4Ko9e8X8zx
+    display_name: HubSpot Workflows
+    hidden: true
+    slug: hubspot-workflows
+    url: connections/sources/catalog/cloud-apps/hubspot-workflows
+    regions:
+      - us
+    endpoints:
+      - us
   - id: 7ha80pBFEj
     display_name: Hubspot X
     hidden: true
@@ -871,6 +880,15 @@ sources:
       - us
     endpoints:
       - us
+  - id: 6qp2MXy9jT
+    display_name: RandomMMTest
+    hidden: true
+    slug: randommmtest
+    url: connections/sources/catalog/cloud-apps/randommmtest
+    regions:
+      - us
+    endpoints:
+      - us
   - id: B0X0QmvMny
     display_name: React Native
     hidden: false
@@ -953,6 +971,15 @@ sources:
     endpoints:
       - us
       - eu
+  - id: MBIRC3BQdd
+    display_name: santhosh - test segment source
+    hidden: true
+    slug: santhosh---test-segment-source
+    url: connections/sources/catalog/cloud-apps/santhosh---test-segment-source
+    regions:
+      - us
+    endpoints:
+      - us
   - id: xn9YEaDaNS
     display_name: Selligent Marketing Cloud
     hidden: false

src/_data/catalog/source_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# source cateogries last updated 2023-05-11 
+# source cateogries last updated 2023-05-16 
 items:
   - display_name: A/B Testing
     slug: a-b-testing

src/_data/catalog/sources.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# sources last updated 2023-05-11 
+# sources last updated 2023-05-16 
 items:
   - id: 8HWbgPTt3k
     display_name: .NET
@@ -177,7 +177,7 @@ items:
     isCloudEventSource: true
     slug: attacker_source
     url: connections/sources/catalog/cloud-apps/attacker_source
-    hidden: false
+    hidden: true
     regions:
       - us
     endpoints:
@@ -356,7 +356,7 @@ items:
     isCloudEventSource: true
     slug: clevertapx
     url: connections/sources/catalog/cloud-apps/clevertapx
-    hidden: false
+    hidden: true
     regions:
       - us
     endpoints:
@@ -764,12 +764,29 @@ items:
       url: https://cdn.filepicker.io/api/file/618XEphQoWXwBKQGOWNw
     categories:
       - CRM
+  - id: 4Ko9e8X8zx
+    display_name: HubSpot Workflows
+    isCloudEventSource: true
+    slug: hubspot-workflows
+    url: connections/sources/catalog/cloud-apps/hubspot-workflows
+    hidden: false
+    regions:
+      - us
+    endpoints:
+      - us
+    source_type: cloud-app
+    description: DRAFT
+    logo:
+      url: https://cdn.filepicker.io/api/file/EdNAHfThTeaDbYg0Qnso
+    categories:
+      - CRM
+      - Marketing Automation
   - id: 7ha80pBFEj
     display_name: Hubspot X
     isCloudEventSource: true
     slug: hubspot-x
     url: connections/sources/catalog/cloud-apps/hubspot-x
-    hidden: false
+    hidden: true
     regions:
       - us
     endpoints:
@@ -1325,7 +1342,7 @@ items:
       demos. Our integration pushes demo engagement data to Segment, enabling
       teams to export this data wherever they'd like.
     logo:
-      url: https://cdn.filepicker.io/api/file/lLFv8CrkTuitKRt0s596
+      url: https://cdn.filepicker.io/api/file/v9Gsx9JyQMGNv9F35EN3
     categories:
       - Analytics
   - id: U9mT0bPcI6
@@ -1613,6 +1630,22 @@ items:
       url: https://cdn.filepicker.io/api/file/uuJxztQ2QjuSQEyrCNfj
     categories:
       - Enrichment
+  - id: 6qp2MXy9jT
+    display_name: RandomMMTest
+    isCloudEventSource: true
+    slug: randommmtest
+    url: connections/sources/catalog/cloud-apps/randommmtest
+    hidden: false
+    regions:
+      - us
+    endpoints:
+      - us
+    source_type: cloud-app
+    description: mailmodo.com
+    logo:
+      url: https://cdn.filepicker.io/api/file/kMFheN8oS7iF0RHpAZIv
+    categories:
+      - Email Marketing
   - id: B0X0QmvMny
     display_name: React Native
     isCloudEventSource: false
@@ -1772,6 +1805,22 @@ items:
         https://d3hotuclm6if1r.cloudfront.net/logos/salesforce-marketing-cloud-default.svg
     categories:
       - Email Marketing
+  - id: MBIRC3BQdd
+    display_name: santhosh - test segment source
+    isCloudEventSource: true
+    slug: santhosh---test-segment-source
+    url: connections/sources/catalog/cloud-apps/santhosh---test-segment-source
+    hidden: false
+    regions:
+      - us
+    endpoints:
+      - us
+    source_type: cloud-app
+    description: mailmodo.com
+    logo:
+      url: https://cdn.filepicker.io/api/file/0dM7y9OoSKKLMLm93kC5
+    categories:
+      - Email Marketing
   - id: xn9YEaDaNS
     display_name: Selligent Marketing Cloud
     isCloudEventSource: true
@@ -1853,7 +1902,7 @@ items:
     isCloudEventSource: true
     slug: source_b2
     url: connections/sources/catalog/cloud-apps/source_b2
-    hidden: false
+    hidden: true
     regions:
       - us
     endpoints:

src/connections/destinations/catalog/actions-braze-cohorts/index.md

@@ -46,6 +46,8 @@ The setup is complete and the Audience will start syncing to Braze Cohorts. Segm
 
 To sync additional Audiences from your Engage space, create a separate mapping in the Braze Cohorts destination. Navigate to **Connections > Destinations**, search and select the Braze Cohorts destination, and follow Steps 9-11 above.
 
+If you are creating multiple mappings in one Braze Cohorts destination, Segment recommends clearing the default subscription for all your mappings from `Event Name is Audience Entered or Event Name is Audience Exited` to `Event Property audience_key is <your_audience_key>`, replacing `<your_audience_key>` with the Audience Key copied as per step 2 above.
+
 > info ""
 > A user can only be added to a cohort if the user already exists in Braze. This means that the Braze Cohorts destination should be used in parallel with the [Braze Cloud Mode (Actions) destination](/docs/connections/destinations/catalog/braze-cloud-mode-actions/) or the [Braze Web Mode (Actions) destination](/docs/connections/destinations/catalog/braze-web-device-mode-actions/), both of which can create users in Braze.
 

src/connections/destinations/catalog/actions-salesforce/index.md

@@ -81,7 +81,6 @@ If you have more than one Salesforce instance connected to Segment, repeat these
 
 Keep the following in mind as you begin to use Salesforce (Actions):
 - Salesforce (Actions) supports batching. The workspace owner can edit the enabled-batching field manually for any of the mappings. This setting is disabled by default.
-- Salesforce (Actions) doesn’t support Delete CRUD operations on Custom Object. Custom Objects with CRUD the operation set to `delete` are not migrated.
 - Sending Identify events to Salesforce (Classic) results in a create or update operation for Leads, and maps properties from `event.traits` Salesforce (Actions) does not support this behavior. By default, the automatic migration maps only a subset of the most used Lead properties as mentioned below. The workspace owner must map any additional Salesforce properties or Custom properties manually.
 
 Review the tables below to see how settings from Salesforce (Classic) were migrated to Salesforce (Actions).

src/connections/destinations/catalog/dreamdata-io/index.md

@@ -1,11 +1,11 @@
 ---
-title: Dreamdata IO Destination
+title: Dreamdata Destination
 rewrite: true
 id: 5c6ef3322a6fb40001a71bf7
 ---
-[Dreamdata IO](https://dreamdata.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) uses your Segment data to deliver multitouch, per account attribution. This enables B2B companies to understand the impact on revenue of every touch in their customer journey.
+[Dreamdata](https://dreamdata.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) uses your Segment data to deliver multitouch, per account attribution. This enables B2B companies to understand the impact on revenue of every touch in their customer journey.
 
-This destination is maintained by Dreamdata IO. For any issues with the destination, [contact the Dreamdata Support team](mailto:[email protected]).
+This destination is maintained by Dreamdata. For any issues with the destination, [contact the Dreamdata Support team](mailto:[email protected]).
 
 {% include content/beta-note.md %}
 
@@ -14,9 +14,9 @@ This destination is maintained by Dreamdata IO. For any issues with the destinat
 {% include content/connection-modes.md %}
 
 1. From the Segment web app, click **Catalog**.
-2. Search for "Dreamdata IO" in the Catalog, select it, and choose which of your sources to connect the destination to.
-3. Enter the "API Key" into your Segment Settings UI which you can find from your [Dreamdata IO settings](https://app.dreamdata.io/settings).
-4. You will be able to verify that data is flowing into Dreamdata IO from your [Dreamdata IO settings](https://app.dreamdata.io/settings).
+2. Search for "Dreamdata" in the Catalog, select it, and choose which of your sources to connect the destination to.
+3. Enter the "API Key" into your Segment Settings UI which you can find from your [Dreamdata settings](https://app.dreamdata.io/settings).
+4. You will be able to verify that data is flowing into Dreamdata from your [Dreamdata settings](https://app.dreamdata.io/settings).
 
 
 ## Page
@@ -27,7 +27,7 @@ If you're not familiar with the Segment Specs, take a look to understand what th
 analytics.page()
 ```
 
-Page calls will be sent to [Dreamdata IO](https://dreamdata.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) as a `pageview`.
+Page calls will be sent to [Dreamdata](https://dreamdata.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) as a `pageview`.
 
 
 ## Screen
@@ -38,7 +38,7 @@ If you're not familiar with the Segment Specs, take a look to understand what th
 [[SEGAnalytics sharedAnalytics] screen:@"Home"];
 ```
 
-Screen calls will be sent to [Dreamdata IO](https://dreamdata.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) as a `screenview`.
+Screen calls will be sent to [Dreamdata](https://dreamdata.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) as a `screenview`.
 
 
 ## Identify
@@ -51,7 +51,7 @@ analytics.identify('userId123', {
 });
 ```
 
-Identify calls will be sent to [Dreamdata IO](https://dreamdata.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) as an `identify` event.
+Identify calls will be sent to [Dreamdata](https://dreamdata.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) as an `identify` event.
 
 
 ## Track
@@ -62,7 +62,7 @@ If you're not familiar with the Segment Specs, take a look to understand what th
 analytics.track('Clicked Login Button')
 ```
 
-Track calls will be sent to [Dreamdata IO](https://dreamdata.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) as a `track` event.
+Track calls will be sent to [Dreamdata](https://dreamdata.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) as a `track` event.
 
 
 ## Group
@@ -78,6 +78,6 @@ analytics.group("userId123", {
 });
 ```
 
-Group calls will be sent to [Dreamdata IO](https://dreamdata.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) as a `group` event where it is used to join users to accounts.
+Group calls will be sent to [Dreamdata](https://dreamdata.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) as a `group` event where it is used to join users to accounts.
 
-By default, [Dreamdata IO](https://dreamdata.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) uses user emails and your CRM data to map user activites to accounts and attribute the value correctly. Adding Group calls using Segment will give a more precise attribution and ensure that all activities are attributed to the right account.
+By default, [Dreamdata](https://dreamdata.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) uses user emails and your CRM data to map user activites to accounts and attribute the value correctly. Adding Group calls using Segment will give a more precise attribution and ensure that all activities are attributed to the right account.

src/connections/destinations/catalog/dreamdata/index.md

@@ -0,0 +1,6 @@
+---
+title: 'Dreamdata Destination'
+hidden: true
+id: 5c6ef3322a6fb40001a71bf7
+published: false
+---

src/connections/destinations/catalog/help-scout/index.md

@@ -8,25 +8,27 @@ id: 54521fd725e721e32a72eebf
 
 ## Getting Started
 
-{% include content/connection-modes.md %}
-
 1. From the Segment web app, click **Catalog**.
 2. Search for Help Scout in the Catalog, select it, and choose which of your sources to connect the destination to.
 3. Click "Connect to Help Scout" to start the Help Scout authentication process. Help Scout provides a secure token that Segment uses to send data to Help Scout. If you need to change accounts, click **Disconnect**, then connect to a new Help Scout account.
 4. Enable the Destination.
-5. Start sending events!
+
+> warning "Help Scout OAuth supports one destination per user"
+> Help Scout's OAuth connection to Segment supports one destination per user. If you try to create two destinations with the same user, you'll receive invalid token errors when you use the destination.
 
 ## Identify
 
 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 this:
 
-    analytics.identify({
-      userId: '019mr8mf4r',
-      traits: {
-        name: 'Kamala Khan',
-        email: '[email protected]',
-      }
-    });
+```js
+  analytics.identify({
+    userId: '019mr8mf4r',
+    traits: {
+      name: 'Kamala Khan',
+      email: '[email protected]',
+    }
+  });
+```
 
 You can use the Identify call to create or update customers in your Help Scout account.