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
+---

src/connections/destinations/catalog/facebook-pixel-server-side/index.md

@@ -96,7 +96,7 @@ Use this approach if you want to separate tracking events completed on a user's
 
 For this option to work best, the same `external_id` needs to be passed from the browser and the server. To achieve this, go to your Facebook Pixel destination settings in Segment and enable the **Enable Advanced Matching** and **Use User ID or Anonymous ID as External ID** settings. By default the Facebook Conversions API destination uses the `userId` (or `anonymousId` if not present) to set the `external_id`, so when you set up Facebook Pixel to use the same settings, Facebook can then match the users.
 
-You can also send [user traits in the context object of the track events](#default-mappings-to-facebook-properties)to increase the match rate for events from a server source. Collect other fields from the browser, like `userAgent`, `ip` address, and [Facebook's parameters (fbp, fbc)](https://developers.facebook.com/docs/marketing-api/conversions-api/parameters/fbp-and-fbc){:target="_blank"}, pass them to the server, and manually add them to the events.
+You can also send [user traits in the context object of the track events](#default-mappings-to-facebook-properties) to increase the match rate for events from a server source. Collect other fields from the browser, like `userAgent`, `ip` address, and [Facebook's parameters (fbp, fbc)](https://developers.facebook.com/docs/marketing-api/conversions-api/parameters/fbp-and-fbc){:target="_blank"}, pass them to the server, and manually add them to the events.
 
 #### Deduplication considerations
 

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

@@ -12,7 +12,7 @@ id: 54521fd725e721e32a72eebd
 1. From the Segment web app, click **Catalog**.
 2. Search for "Heap" in the Catalog, select it, and choose which of your sources to connect the destination to.
 3. In the destination settings, enter your Heap "App ID" into the connection settings.
-4. Remove Heap's snippet from your page if you're using Segment's client-side Analytics.js library to load Heap. With the Analytics.js library, Segment asynchronously loads Heap's JavaScript library onto your page. All native functionality of Heap, including auto-capturing of all events are available to you.  
+4. Remove Heap's snippet from your page if you're using Segment's client-side Analytics.js library to load Heap. With the Analytics.js library, Segment asynchronously loads Heap's JavaScript library onto your page. All native functionality of Heap, including auto-capturing of all events, is available to you.  
 
 ## Identify
 

src/connections/destinations/catalog/insider-audiences/index.md

@@ -0,0 +1,6 @@
+---
+title: 'Insider Audiences Destination'
+hidden: true
+id: 643698ffee21b544f6aa756a
+published: false
+---

src/connections/destinations/catalog/insider-cloud-mode-actions/index.md

@@ -0,0 +1,6 @@
+---
+title: 'Insider Cloud Mode (Actions) Destination'
+hidden: true
+id: 643697f531f98a978f414453
+published: false
+---

src/connections/destinations/catalog/launchdarkly-audiences/index.md

@@ -0,0 +1,7 @@
+---
+title: 'LaunchDarkly Audiences Destination'
+hidden: true
+id: 64e72a310da9ebedf99c8937
+published: false
+beta: true
+---

src/connections/destinations/catalog/linkedin-insight-tag/index.md

@@ -53,3 +53,7 @@ From there, click **Configure LinkedIn Insight Tag** and select the source for w
 ![A screenshot of the Settings page for the LinkedIn Insight Tag destination.](images/Nmad4zYvWy.png)
 
 Select that option and paste in the LinkedIn Data Partner ID that you copied earlier. Click **Save**, then click **Activate Destination**. Our servers build the latest CDN for that source, and the LinkedIn Insight Tag loads on the sites that use that source's Segment snippet!
+
+## Conversion tracking
+
+Segment's LinkedIn Insight Tag destination is fairly unique in that all Segment does is load the LinkedIn scripts onto your website for you so you can call methods directly without having to add the script tags yourself. Any special conversion tracking needs to be done within your LinkedIn workspace as you normally would if you were setting up LinkedIn without Segment. 

src/connections/destinations/catalog/optimizely-advanced-audience-targeting/index.md

@@ -0,0 +1,7 @@
+---
+title: 'Optimizely Advanced Audience Targeting Destination'
+hidden: true
+id: 64edeb2bee24614fe52ede34
+published: false
+beta: true
+---

src/connections/destinations/catalog/optimizely-web/index.md

@@ -229,21 +229,23 @@ For example, let's say you run a redirect experiment on page `http://home.com` t
 
 Our Optimizely Web destination detects this and send the effective referrer value as a property of the subsequent Experiment Viewed. Segment also overrides the `context.page.referrer` with the effective referrer.
 
-More importantly, to send the true referrer value with the initial `page` call inside the Segment snippet, you can look up `window.optimizelyEffectiveReferrer`, and if it exists, you can pass that into your `page` call. This is how you might modify your Segment snippet:
+More importantly, to send the true referrer value with the initial `page` call inside the Segment snippet, you can look up `window.optimizelyEffectiveReferrer`, and if it exists, you can pass that into your `page` call. This is how you might modify your Segment snippet to pass the extra code inside [ready()](/docs/connections/sources/catalog/libraries/website/javascript/#ready) so its only called after Optimizely SDK has finished loading:
 
 ```javascript
-<script type="text/javascript">
-  !function(){var analytics=window.analytics=window.analytics||[];if(!analytics.initialize)if(analytics.invoked)window.console&&console.error&&console.error("Segment snippet included twice.");else{analytics.invoked=!0;analytics.methods=["trackSubmit","trackClick","trackLink","trackForm","pageview","identify","reset","group","track","ready","alias","debug","page","once","off","on","addSourceMiddleware","addIntegrationMiddleware","setAnonymousId","addDestinationMiddleware"];analytics.factory=function(t){return function(){var e=Array.prototype.slice.call(arguments);e.unshift(t);analytics.push(e);return analytics}};for(var t=0;t<analytics.methods.length;t++){var e=analytics.methods[t];analytics[e]=analytics.factory(e)}analytics.load=function(t,e){var n=document.createElement("script");n.type="text/javascript";n.async=!0;n.src="https://cdn.segment.com/analytics.js/v1/"+t+"/analytics.min.js";var a=document.getElementsByTagName("script")[0];a.parentNode.insertBefore(n,a);analytics._loadOptions=e};analytics.SNIPPET_VERSION="4.1.0";
+<script>
+  !function(){var analytics=window.analytics=window.analytics||[];if(!analytics.initialize)if(analytics.invoked)window.console&&console.error&&console.error("Segment snippet included twice.");else{analytics.invoked=!0;analytics.methods=["trackSubmit","trackClick","trackLink","trackForm","pageview","identify","reset","group","track","ready","alias","debug","page","once","off","on","addSourceMiddleware","addIntegrationMiddleware","setAnonymousId","addDestinationMiddleware"];analytics.factory=function(e){return function(){if(window.analytics.initialized)return window.analytics[e].apply(window.analytics,arguments);var i=Array.prototype.slice.call(arguments);i.unshift(e);analytics.push(i);return analytics}};for(var i=0;i<analytics.methods.length;i++){var key=analytics.methods[i];analytics[key]=analytics.factory(key)}analytics.load=function(key,i){var t=document.createElement("script");t.type="text/javascript";t.async=!0;t.src="https://cdn.segment.com/analytics.js/v1/" + key + "/analytics.min.js";var n=document.getElementsByTagName("script")[0];n.parentNode.insertBefore(t,n);analytics._loadOptions=i};analytics._writeKey="YOUR_WRITE_KEY";;analytics.SNIPPET_VERSION="4.16.1";
   analytics.load("YOUR_WRITE_KEY");
 
-  /* MODIFIED SECTION */
+
+   analytics.ready(function() {
+    /* MODIFIED SECTION */
   // Hey did Optimizely set an effective referrer?
   if (window.optimizelyEffectiveReferrer) var referrer = window.optimizelyEffectiveReferrer;
 
   // If they did, override the document.referrer
-  referrer ? analytics.page({ referrer: referrer }): analytics.page();
+  referrer ? analytics.page({ referrer: referrer }):analytics.page();
   /* MODIFIED SECTION */
-
+  });
   }}();
 </script>
 ```

src/connections/functions/usage.md

@@ -69,3 +69,7 @@ for (const response of responses) {
 ```
 
 If you're only issuing a single request in your function and it is slow, you might want to contact the owner of the external API for support.
+
+## Default limit number
+
+Each workspace has a default limit of 25 Functions in total across Source, Insert, and Destination Functions. If you want to create more, please reach out to [Segment](mailto:[email protected]).

src/connections/reverse-etl/reverse-etl-source-setup-guides/postgres-setup.md

@@ -6,6 +6,13 @@ Set up Postgres as your Reverse ETL source.
 
 At a high level, when you set up Postgres for Reverse ETL, the configured user/role needs read permissions for any resources (databases, schemas, tables) the query needs to access. Segment keeps track of changes to your query results with a managed schema (`__SEGMENT_REVERSE_ETL`), which requires the configured user to allow write permissions for that schema.
 
+Segment supports the following Postgres database providers:
+- Heroku
+- RDS
+
+> warning ""
+> Segment only supports these Postgres database providers. Postgres databases from other providers aren't guaranteed to work. For questions or concerns about Segment-supported Postgres providers, [contact Segment Support](https://segment.com/help/contact){:target="_blank"}.
+
 ## Set up guide
 To set up Postgres with Reverse ETL:
 
@@ -28,4 +35,4 @@ To set up Postgres with Reverse ETL:
 ## Extra permissions
 * Give the `segment` user read permissions for any resources (databases, schemas, tables) the query needs to access. 
 
-* Give the `segment` user write permissions for the Segment managed schema (`__SEGMENT_REVERSE_ETL`), which keeps track of changes to the query results.  
+* Give the `segment` user write permissions for the Segment managed schema (`__SEGMENT_REVERSE_ETL`), which keeps track of changes to the query results.  

src/connections/sources/catalog/cloud-apps/alloyflow/index.md

@@ -1,6 +1,5 @@
 ---
 title: 'Alloy Flow Source'
-hidden: true
 id: DY0B0Q2Gce
 beta: true
 ---

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

@@ -69,6 +69,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/kotlin-android/destination-plugins/survicate-kotlin-android/
+    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/kotlin-android/destination-plugins/quantcast-kotlin-android/
     logo:
@@ -139,4 +145,4 @@ To test your destination:
 Segment recommends you to test your destination implementation end-to-end. Send some sample analytics events and ensure that they reach the destination.
 
 > info ""
-> For more information about the Analytics Kotlin Plugin architecture and how it can help you customize your tracking implementation to suit your needs, refer to the [Plugin Architecture Guide.](/docs/connections/sources/catalog/libraries/mobile/kotlin-android/kotlin-android-plugin-architecture)
+> For more information about the Analytics Kotlin Plugin architecture and how it can help you customize your tracking implementation to suit your needs, refer to the [Plugin Architecture guide](/docs/connections/sources/catalog/libraries/mobile/kotlin-android/kotlin-android-plugin-architecture).