Merge pull request #5546 from segmentio/develop

Release 23.42.1

Author: stayseesong

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-google-analytics-4-web/index.md

@@ -34,16 +34,6 @@ Some parameters automatically populate prebuilt [dimensions and metrics](https:/
 
 With custom parameters, you must create [custom dimensions and metrics](https://support.google.com/analytics/answer/10075209){:target="_blank"} so you can see the parameter values in Google Analytics. 
 
-### Understanding Event Parameters 
-
-Parameters provide additional information about the ways users interact with your website. For example, when someone views a product you sell, you can include parameters that describe the product they viewed, like `product_name`, `category`, and `price`.
-
-The automatically collected and enhanced measurement events include parameters by default. Google also provides a set of required and optional parameters to include with each recommended event. Additionally, you can add more event parameters when you need them.
-
-{% include components/actions-fields.html settings="true"%}
-
-## FAQ & Troubleshooting
-
 ### Custom Events
 
 Google Analytics 4 does not accept custom event names that include spaces. Segment replaces spaces in the Event Name in the Custom Event action with an underscore. As a result, you will see custom events snake cased in Google Analytics 4.
@@ -56,6 +46,20 @@ Keep in mind that custom events will not appear in Google's standard reports; yo
 
 With Google Analytics 4, you must create custom dimensions and metrics within the Google Analytics 4 interface to link event parameters to the corresponding custom dimensions or metrics. When creating the dimension or metric, you can either select a parameter from the list of already collected fields or enter the name of the parameter you plan to collect in the future. For more information, see [Google Analytics 4 Custom dimensions and metrics](https://support.google.com/analytics/answer/10075209?hl=en){:target="_blank"}.
 
+### Understanding Event Parameters 
+
+Parameters provide additional information about the ways users interact with your website. For example, when someone views a product you sell, you can include parameters that describe the product they viewed, like `product_name`, `category`, and `price`.
+
+The automatically collected and enhanced measurement events include parameters by default. Google also provides a set of required and optional parameters to include with each recommended event. Additionally, you can add more event parameters when you need them.
+
+### Conversion Events
+
+Some of Segment's prebuilt [Available Actions](https://segment-docs.netlify.app/docs/connections/destinations/catalog/actions-google-analytics-4-web/#available-actions) which map to Google's recommended events are automatically marked as a conversion in your Analytics dashborad. For example, when you add a "Order Completed" event, it will show up in your Analytics dashboard as "purchase" with the **Mark as conversion** toggle toggled on by default. However, for other events, such as "Add to Cart", you will need to manually toggle the **Mark as conversion** setting on in your Analytics dashboard. If you don't mark the event as a conversion, it will not show up as a conversion in your built-in reports. You can read more [about conversion events](https://support.google.com/analytics/answer/9267568?sjid=1275909514202748631-NA){:target="_blank"} in Google's docs. 
+
+{% include components/actions-fields.html settings="true"%}
+
+## FAQ & Troubleshooting
+
 ### Debug Mode
 
 The Google Analytics 4 [debug mode](https://support.google.com/analytics/answer/7201382?hl=en){:target="_blank"} is supported with the Google Analytics 4 Web destination. DebugView displays the events and user properties that Analytics collects from a user in real-time. This can be helpful in troubleshooting your implementation.

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/actions-launchdarkly-audiences/index.md

@@ -10,9 +10,7 @@ beta: true
 
 With LaunchDarkly, you can release features that target specific groups, such as beta users, and premium accounts, using segments. This destination allows you to sync Engage Audiences to LaunchDarkly segments, letting you concentrate more on deploying features and less on managing end users between platforms.
 
-LaunchDarkly maintains this destinatino. For any issues with the destination, [contact the LaunchDarkly Support team](mailto:[email protected]).
-
-{% include content/ajs-upgrade.md %}
+LaunchDarkly maintains this destination. For any issues with the destination, [contact the LaunchDarkly Support team](mailto:[email protected]).
 
 ## Getting started
 

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

@@ -2,8 +2,6 @@
 title: Loops (Actions) Destination
 hide-boilerplate: true
 hide-dossier: true
-beta: true
-private: true
 id: 63360a5fe290ca3fdfad4a68
 ---
 

src/connections/destinations/catalog/actions-the-trade-desk-crm/index.md

@@ -33,10 +33,10 @@ Before you begin, generate a [long-lived token](https://partner.thetradedesk.com
 6. Once authenticated, enter your Authentication Token and Advertiser ID from your [The Trade Desk's CRM Data Platform API](https://api.thetradedesk.com/v3/portal/data/doc/DataIntegrateCRMData){:target="_blank"} account. Enable the destination by toggling **Enable Destination** and click **Save Changes**.
 7. Navigate to the **Mappings** tab, click **New Mapping**, and choose **Sync Audience to CRM Data Segment**.
 8. In the **Select mappings** section, input the PII Type and maintain other defaults. Click **Save** and toggle to enable the mapping.
-   - If you see a field labeled "Segment Name," please input the same name as the audience you have connected the destination to. Ensure that there is no existing segment in TTD with the identical name.  Additionally, fill out the "Region" field with the geographical region of the CRM data segment, based on the origin of the PII.
-   - _**Create only one mapping for every instance.**_
-9. Return to **Engage > Audiences** and select the Audience from Step 1.
-10. Click **Add Destinations** and choose The Trade Desk CRM destination you just created. In the settings that appear in the side panel, enable the **Send Track** option and **do not** alter the Audience Entered/Audience Exited event names. If you missed providing the Segment Name and Region in step 8, please complete the Audience Settings, specifically the region field, with the geographical region of the CRM data segment based on the origin of the PII. Please note that the Public Beta only supports `US`. Click **Save Settings**.
+   - **Create only one mapping for every instance.**
+   - If any of the emails stored in your Engage audience are already in a hashed format, please specify the PII type as `Hashed Email.` Failure to do so results in The Trade Desk categorizing the hashed records as invalid during the ingestion process. 
+9. Return to **Engage > Audiences** and select the audience from Step 1.
+10. Click **Add Destinations** and choose The Trade Desk CRM destination you just created. In the settings that appear in the side panel, enable the **Send Track** option and **do not** alter the Audience Entered/Audience Exited event names. Fill out the audience settings, specifically the region field, with the geographical region of the CRM data segment based on the origin of the PII (US, EU, or APAC). Click **Save Settings**.
 
 Setup is now complete, and the audience starts syncing to The Trade Desk.
 
@@ -68,4 +68,5 @@ The CRM endpoint maps email addresses into UID2s. If it's a valid email address,
 
 #### What PII format should I send?
 
-The Trade Desk recommends transmitting personally identifiable information (PII) in its original, non-hashed format. TTD's preference is to handle the hashing of the data on their end.
+The Trade Desk recommends transmitting personally identifiable information (PII) in its original, non-hashed format. TTD's preference is to handle the hashing of the data on their end (PII type as `Email`). However, if your data already contains any hashed emails, please designate the PII type as `Hashed Email.`
+

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/rate-limits.md

@@ -9,7 +9,10 @@ Events ingested by Segment have a limit of **10,000** properties per individual
 
 ## Inbound data ingestion API rate limit
 
-If within a ten minute period a Customer's sources (in aggregate) send more than 60 million events (average of 100,000 events per second) without prior arrangement, Segment reserves the right to queue any additional events and process those at a rate that does not exceed 60 million events in any ten minute period.
+If any sources send more than 20,000 events per second without prior arrangement, Segment reserves the right to queue any additional events and process those at a rate that doesn't exceed this limit.
+
+> warning "Engage rate limit"
+> Engage has a limit of 1,000 events per second for inbound data. Visit the [Engage Default Limits documentation](/docs/engage/product-limits/) to learn more.
 
 ## Outbound downstream destination rate limits
 

src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/index.md

@@ -56,6 +56,12 @@ plugins:
       url: https://cdn.filepicker.io/api/file/fb5lNYEhQoWnABOjynZ6
     mark:
       url: https://cdn.filepicker.io/api/file/kWmScDJ3SvK1QBZTChGQ
+  - name: Survicate
+    url: connections/sources/catalog/libraries/mobile/apple/destination-plugins/survicate-swift/
+    logo:
+      url: https://cdn.filepicker.io/api/file/BUciQq3kSzqCn8EKMtBN
+    mark:
+      url: https://cdn.filepicker.io/api/file/0H2JyPoRT4K3CnBQcHPn
   - name: Quantcast
     url: connections/sources/catalog/libraries/mobile/apple/destination-plugins/quantcast-swift/
     logo: