Merge branch 'develop' into validating-consent-object

Author: forstisabella

src/_data/catalog/destination_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination categories last updated 2023-10-12 
+# destination categories last updated 2023-10-17 
 items:
 - display_name: A/B Testing
   slug: a-b-testing

src/_data/catalog/destinations.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2023-10-12 
+# destination data last updated 2023-10-17 
 items:
 - id: 637e8d185e2dec264895ea89
   display_name: 1Flow
@@ -40972,7 +40972,7 @@ items:
       Enable this option if you would like Segment to load the HubSpot SDK for
       EU data residency.
     required: true
-    label: Enable the European Data Center SDK
+    label: Enable the European Data Center SDK.
   - name: flushIdentifyImmediately
     type: boolean
     defaultValue: false
@@ -41013,7 +41013,7 @@ items:
     hidden: false
     defaultTrigger: type = "identify"
     fields:
-    - id: pRYSj58E6zYZLCn1G5Eu4T
+    - id: TESKoFRMLw4xpNKrVfEwc
       sortOrder: 0
       fieldKey: email
       label: Email Address
@@ -41029,7 +41029,7 @@ items:
       choices: null
       dynamic: false
       allowNull: false
-    - id: 9Ffw3F9EAavT459MtKg9dZ
+    - id: 46D142iC6ebDADuP1A4h72
       sortOrder: 1
       fieldKey: id
       label: External ID
@@ -41043,7 +41043,7 @@ items:
       choices: null
       dynamic: false
       allowNull: false
-    - id: cZYCgE9JQ7M4hXemParPMi
+    - id: bg4eKEuk14oM4HiJfopSDJ
       sortOrder: 2
       fieldKey: custom_properties
       label: Custom Properties
@@ -41061,7 +41061,7 @@ items:
       choices: null
       dynamic: false
       allowNull: false
-    - id: s3PFjuYmmNR43JmB12fFb7
+    - id: uPDWHGUH4TeexZJLdXHSYh
       sortOrder: 3
       fieldKey: company
       label: Company Name
@@ -41075,7 +41075,7 @@ items:
       choices: null
       dynamic: false
       allowNull: false
-    - id: aAAb2D1KFNtcmiyvcK4EqL
+    - id: tbeSoTRJgL9bnD4a7agYB1
       sortOrder: 4
       fieldKey: country
       label: Country
@@ -41089,7 +41089,7 @@ items:
       choices: null
       dynamic: false
       allowNull: false
-    - id: xfuSoZXgHxjDujLQz5J2FA
+    - id: n8SFogR54DtecbEK7MPHd3
       sortOrder: 5
       fieldKey: state
       label: State
@@ -41103,7 +41103,7 @@ items:
       choices: null
       dynamic: false
       allowNull: false
-    - id: 2WQ6ZQc2nVSdGxTgqamLXs
+    - id: WVY4RsWRYZ4HL1671H9LR
       sortOrder: 6
       fieldKey: city
       label: City
@@ -41117,7 +41117,7 @@ items:
       choices: null
       dynamic: false
       allowNull: false
-    - id: aLcciXXZXZa4ZcPWMnY6yt
+    - id: mxRFBbuvgLafRkjTWBhmub
       sortOrder: 7
       fieldKey: address
       label: Street Address
@@ -41131,7 +41131,7 @@ items:
       choices: null
       dynamic: false
       allowNull: false
-    - id: itAVtPekt7t3QkX2RcoRXM
+    - id: oWeYAd2eA5TeyhVWQX9jGX
       sortOrder: 8
       fieldKey: zip
       label: Postal Code
@@ -41159,7 +41159,7 @@ items:
     hidden: false
     defaultTrigger: type = "track"
     fields:
-    - id: rQcrqyoAvJQdzTDTC51QdD
+    - id: kx157WWAPwwKNhUQRrrxiJ
       sortOrder: 0
       fieldKey: name
       label: Event Name
@@ -41177,7 +41177,7 @@ items:
       choices: null
       dynamic: false
       allowNull: false
-    - id: 4eAqrAGFGkF7TVBp38h8wN
+    - id: jg4wddnZkoEJc2ePx3g3dg
       sortOrder: 1
       fieldKey: properties
       label: Event Properties
@@ -41199,7 +41199,7 @@ items:
     hidden: false
     defaultTrigger: type = "page"
     fields:
-    - id: gukzTarLEP3qrWuLJR782r
+    - id: axZqvzyC5BgvwJqaPejkha
       sortOrder: 0
       fieldKey: path
       label: Path String
@@ -41214,18 +41214,6 @@ items:
       dynamic: false
       allowNull: false
   presets:
-  - actionId: rnaHv5Y8rWxCiG6s3D6ShH
-    name: Track Page View
-    fields: {}
-    trigger: type = "page"
-  - actionId: nQrUkFqLZ6Zv6JaZGYTBDd
-    name: Track Custom Behavioral Event
-    fields:
-      name:
-        '@path': $.event
-      properties:
-        '@path': $.properties
-    trigger: type = "track"
   - actionId: hSedKQQp1KxbB5FXsrofKB
     name: Upsert Contact
     fields:
@@ -41254,6 +41242,18 @@ items:
           else:
             '@path': $.traits.address.postal_code
     trigger: type = "identify"
+  - actionId: nQrUkFqLZ6Zv6JaZGYTBDd
+    name: Track Custom Behavioral Event
+    fields:
+      name:
+        '@path': $.event
+      properties:
+        '@path': $.properties
+    trigger: type = "track"
+  - actionId: rnaHv5Y8rWxCiG6s3D6ShH
+    name: Track Page View
+    fields: {}
+    trigger: type = "page"
 - id: 64b0e177091331e4a2a00c83
   display_name: Humanic AI
   name: Humanic AI
@@ -50691,7 +50691,7 @@ items:
   display_name: Loops (Actions)
   name: Loops (Actions)
   slug: loops-actions
-  hidden: false
+  hidden: true
   endpoints:
   - US
   regions:
@@ -50701,7 +50701,7 @@ items:
   previous_names:
   - Loops (Actions)
   website: https://loops.so
-  status: PUBLIC_BETA
+  status: PUBLIC
   categories:
   - Email Marketing
   - Marketing Automation

src/_data/catalog/destinations_private.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2023-10-12 
+# destination data last updated 2023-10-17 
 items:
   - id: 54521fd725e721e32a72eec6
     display_name: Intercom

src/_data/catalog/source_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# source categories last updated 2023-10-12 
+# source categories last updated 2023-10-17 
 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-10-12 
+# sources last updated 2023-10-17 
 items:
   - id: 8HWbgPTt3k
     display_name: .NET

src/connections/destinations/catalog/actions-intercom-web/index.md

@@ -42,6 +42,9 @@ Intercom Web (Actions) provides the following benefits over the classic Intercom
 > info "Regional Data Hosting in the EU and Australia"
 > For Regional Data Hosting in the EU and Australia, you'll need an Intercom plan that [supports regional data hosting](https://www.intercom.com/help/en/articles/5778275-additional-details-on-intercom-regional-data-hosting){:target="_blank"}.
 
+> info ""
+> Segment doesn't support the creation of **Leads** for Intercom Web. Segment recommends using [Intercom Cloud Mode](/docs/connections/destinations/catalog/actions-intercom-cloud/) to support leads creation.
+
 {% include components/actions-fields.html settings="true"%}
 
 ## Troubleshooting

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

@@ -0,0 +1,36 @@
+---
+title: CDP Resolution (Browser) Destination
+id: 650c69e7f47d84b86c120b4c
+beta: true
+---
+
+
+{% include content/plan-grid.md name="actions" %}
+
+[CDP Resolution](https://cdpresolution.com?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} helps customers instantly match visitor website traffic to full profiles. It turns your anonymous web traffic into full company and buyer profiles — complete with PII and firmographics data, and much more. You can find a [list of the different attributes](https://cdpresolution.com/theattributes?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} you can collect with CDP Resolution.
+
+This destination is maintained by CDP Resolution. For any issues with the destination, [contact the CDP Resolution support team](mailto:[email protected]).
+
+{% include content/ajs-upgrade.md %}
+
+How this works: A visitor lands on a digital property that has the segment.io analytics.js script connected to the CDP Resolution (Browser) Destination enabled.  For each session, the anonymous ID is sent to CDP Resolution to check if our cookie is present on the browser.  This allows CDP Resolution to resolve the cookie against our graph. If found, the profile and firmographics data are sent to segment.io against a source that is configured within CDP Resolution platform.
+
+## Getting started
+
+To set up the CDP Resolution destination:
+1.	Navigate to **Connections > Catalog** in the Segment app and select the **Destinations** tab of the catalog. 
+2.	Search for *CDP Resolution* and select it.
+3. Choose which of your sources to connect the destination to.
+4.	In the Settings, enter your CDP Resolution API key. You can find this in the CDP Connector Setting section of your [CDP Resolution Dashboard Connection Settings](https://app.cdpresolution.com/administration/cdp-connections/segment-io-f4241?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"}.
+5. Go to the CDP Resolution UI. 
+5. Go to the [CDP Resolution Connectors](https://app.cdpresolution.com/administration/cdp-connections?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} page and select the Segment IO connector.
+2.	Paste your CDP Resolution API key in Segment to generate your Write Key.
+3.	Paste your Write Key into CDP Resolution's connection configuration.
+4.	Click **Upload Key**.
+
+Further documentation can be found on the [CDP documentation site](https://docs.cdpresolution.com?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"}.
+
+If you have configured your CDP Resolution Destination correctly, and if you've also configured CDP Resolution to send user profile data to a Segment Source, you should start to see user profile data shown in the Segment Source debugger as identify() and group() calls.
+
+{% include components/actions-fields.html %}
+

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

@@ -7,12 +7,17 @@ cmode-override: true
 
 Once the Segment library is integrated, toggle CleverTap on in your Segment destinations, and add your CleverTap Account ID and CleverTap Account Token which you can find in the CleverTap Dashboard under Settings.
 
+CleverTap supports the Identify, Track, Page (server-side only), and Screen (iOS and server-side only) methods.
+
 You can integrate CleverTap using a server-side or mobile destination (iOS or Android). If you are interested in using CleverTap's push notifications or in-app notifications products, you should use the mobile destinations.
 
-All server-side destination requests require both the Segment `anonymousId` and `userId` in the payload. This is a requirement from CleverTap. CleverTap maintains the server-side integration. For any issues with the server-side integration, [contact the CleverTap Support team](https://help.clevertap.com/hc/en-us/requests/new){:target="_blank"}.
+For server-side destination requests, CleverTap requires both the Segment `anonymousId` and `userId` in the payload.  
 
-CleverTap supports the `identify`, `track`, `page` (server-side only), and `screen` (iOS and server-side only) methods.
+CleverTap maintains the server-side and mobile integrations:
+- [Android](https://github.com/CleverTap/clevertap-segment-android){:target="_blank"}
+- [iOS](https://github.com/CleverTap/clevertap-segment-ios){:target="_blank"}
 
+For any issues with the server-side and mobile integrations, [contact the CleverTap Support team](https://help.clevertap.com/hc/en-us/requests/new){:target="_blank"}.
 
 ## Identify
 

src/connections/sources/catalog/libraries/mobile/kotlin-android/kotlin-android-plugin-architecture.md

@@ -27,9 +27,8 @@ For example, if you want to add something to the context object of any event pay
 ```java
 class SomePlugin: Plugin {
     override val type = Plugin.Type.Enrichment
-    override val name = "SomePlugin"
 
-    override var lateinit analytics: Analytics
+    override lateinit var analytics: Analytics
 
     override fun execute(event: BaseEvent): BaseEvent? {
         event.putInContext("foo", "bar")
@@ -96,9 +95,8 @@ analytics.add(amplitudePlugin) // add amplitudePlugin to the analytics client
 
 val amplitudeEnrichment = object: Plugin {
     override val type = Plugin.Type.Enrichment
-    override val name = "SomePlugin"
 
-    override var lateinit analytics: Analytics
+    override lateinit var analytics: Analytics
 
     override fun execute(event: BaseEvent): BaseEvent? {
         event.putInContext("foo", "bar")
@@ -124,9 +122,8 @@ Here's an example of adding a plugin to the context object of any event payload
 ```java
 class SomePlugin: Plugin {
     override val type = Plugin.Type.Enrichment
-    override val name = "SomePlugin"
 
-    override var lateinit analytics: Analytics
+    override lateinit var analytics: Analytics
 
     override fun execute(event: BaseEvent): BaseEvent? {
         event.putInContext("foo", "bar")

src/connections/sources/catalog/libraries/website/javascript/index.md

@@ -919,6 +919,38 @@ Bundle the destinations you want loaded from [npm](https://www.npmjs.com/package
   }),
   ```
 
+## Segment Inspector
+The Segment Inspector is a Chrome web extension that enables you to debug your Segment integration on web applications instrumented with Analytics.js 2.0. Analytics.js sends data to the extension so that you can see how events change before they're sent to your destinations and so that you can verify that the event details are correct. The Segment Inspector also lets you analyze and confirm that API calls made from your website arrive to your Analytics.js 2.0 source. 
+
+> info ""
+> For the Segment inspector to work, you must enable the Analytics.js 2.0 source.
+
+To add the Segment Inspector as a Chrome extension:
+1. Go to the [Chrome web store](https://chrome.google.com/webstore/category/extensions){:target="_blank”}.
+2. Search for **Segment Inspector**.
+3. Click **Add to Chrome**.
+4. Click **Add Extension** in the pop-up window.  
+
+Once installed, use the Inspect Elements developer tool in Chrome to use the Segment Inspector. To access the Inspector, go to the top menu bar of Chrome and navigate to **View > Developer > Developer Tools** and go to the **Segment** tab. On the Segment tab, you can:
+- Filter the different calls by type
+- Search based off of the content in the calls
+- Identify users  
+
+### Components of the Segment Inspector 
+The Segment Inspector is composed of these three components:
+1. The **Diagnostics** tab 
+   - This tab shows the library versions and the list of active integrations that are running. 
+   - When you select an integration, you can see the options that passed while the integration loads. If you made any local overrides within the integration or on the page itself, they appear highlighted in the code. 
+2. The **Events** tab 
+   - This tab enables you to select an event and see the specific details of the event. You can view the time the event occurred, the status of the event (whether it sent or failed), what plugins were added, and how the context object changed. Any changes made to the payload appear highlighted. 
+   - Select the double-checked icon to see the payload at the delivery stage.
+   - Select the *fx* icon to see the payloads after plugins ran.
+   - Select the single-checked icon to see the payload as it was when the event triggered.
+3. The **Identity** tab 
+   - This tab enables you to see the information of a user if you're using the `identify` feature. You can associate the data to an individual and measure their activity across multiple sessions and devices. This tab only shows the user's traits that are on the client. 
+   - If you're not using the `identify` feature, the user remains anonymous. 
+
+
 ## Open source libraries
 
 Analytics.js 2.0 includes the following open source components: