Merge pull request #5660 from segmentio/develop

Release 23.45.1

Author: pwseg

src/_data/catalog/destination_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination categories last updated 2023-11-02 
+# destination categories last updated 2023-11-09 
 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-11-02 
+# destination data last updated 2023-11-09 
 items:
 - id: 637e8d185e2dec264895ea89
   display_name: 1Flow
@@ -46372,7 +46372,7 @@ items:
   previous_names:
   - Iterable (Actions)
   website: http://www.iterable.com
-  status: PUBLIC_BETA
+  status: PUBLIC
   categories:
   - Email Marketing
   - SMS & Push Notifications

src/_data/catalog/destinations_private.yml

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

src/_sass/components/_markdown.scss

@@ -246,6 +246,12 @@
     }
   }
 
+  table.horizontal-scroll {
+    display: block;
+    overflow-x: auto;
+    white-space: nowrap;
+  }
+
   table.settings {
     width: 100%;
     table-layout: fixed;

src/connections/destinations/catalog/actions-google-analytics-4-web/index.md

@@ -55,7 +55,7 @@ The automatically collected and enhanced measurement events include parameters b
 
 ### 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. 
+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 dashboard. 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"%}
 
@@ -85,6 +85,12 @@ In order for data to be sent downstream to Google Analytics, check your mappings
 
 The **setConfigurationFields** mapping is required in order for data to be sent downstream. If no other mappings are enabled, the destination does not send events.
 
+### Manually send `page_view` events
+
+If you prefer to the keep **Page Views** setting disabled and manually send a `page_view`, please see this Google Doc for more on [Manual Pageviews](https://developers.google.com/analytics/devguides/collection/ga4/views?client_type=gtag#manually_send_page_view_events).
+
+With Google Analytics 4 Web, you will need to configure a [Custom Event](/docs/connections/destinations/catalog/actions-google-analytics-4-web/#custom-event) mapping for manually sending `page_view` events. When mapping the events, please make sure to set the Event Name to `page_view`.
+
 ### Tracking UTM Parameters
 
 UTM Parameters are automatically tracked and sent to Google when they are present in the URL. For example, with the following URL:

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

@@ -68,5 +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 (PII type as `Email`). However, if your data already contains any hashed emails, please designate the PII type as `Hashed Email.`
+The Trade Desk recommends transmitting personally identifiable information (PII) in its original, non-hashed format. TTD's preference is to handle the hashing of any PII, like emails, on their end. However, if your data already contains any hashed emails, please ensure you are normalizing and hashing the emails by designating the PII type as `Hashed Email`, in line with TTD's [PII Normalization and Hash Encoding](https://api.thetradedesk.com/v3/portal/data/doc/DataPiiNormalization){:target="_blank”} documentation.
 

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

@@ -10,9 +10,6 @@ This destination is maintained by Autopilot.  See [Autopilot's documentation](ht
 Are you instead trying to set up Autopilot as a Source to get data from Autopilot into your data warehouse or other downstream tools? See our documentation on our [Autopilot source](/docs/connections/sources/catalog/cloud-apps/autopilothq/) instead.
 
 ## Getting Started
-
-
-
   1. From the Segment web app, click **Catalog**.
   2. Search for "Autopilot" in the Catalog, select it, and choose which of your sources to connect the destination to.
   3. In the destination settings, enter your "API Key" from [here](https://login.autopilothq.com/login#settings/app-connections/segment-sync){:target="_blank”} or go to Autopilot: Settings -> App Connections -> Segment and copy/paste the API key which is listed there.
@@ -29,6 +26,9 @@ analytics.identify('12091906-01011992', {
 });
 ```
 
+> info "Engage requires Identify calls from the Autopilot destination to include email or userId"
+> If neither are provided in the payload then the Autopilot destination's [Event Delivery](/docs/connections/event-delivery/) tab will show a 400 Bad Request error message : _"Missing unique identifier traits. Either `email` or `user_id` traits must be provided"_.
+
 ## 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:

src/connections/destinations/catalog/cdp-resolution/index.md

@@ -0,0 +1,7 @@
+---
+title: 'CDP Resolution Destination'
+hidden: true
+id: 650c69e7f47d84b86c120b4c
+published: false
+beta: true
+---