Merge pull request #5985 from segmentio/develop

rchinn1 · web-flow · commit 18ff0d7004bc · 2024-02-01T10:54:28.000-08:00
Release 24.5.2
diff --git a/src/_data/catalog/destination_categories.yml b/src/_data/catalog/destination_categories.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination categories last updated 2024-01-30 
+# destination categories last updated 2024-02-01 
 items:
 - display_name: A/B Testing
   slug: a-b-testing
diff --git a/src/_data/catalog/destinations.yml b/src/_data/catalog/destinations.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2024-01-30 
+# destination data last updated 2024-02-01 
 items:
 - id: 637e8d185e2dec264895ea89
   display_name: 1Flow
@@ -11487,6 +11487,7 @@ items:
   slug: aws-s3
   hidden: false
   endpoints:
+  - EU
   - US
   regions:
   - us-west-2
@@ -15833,6 +15834,7 @@ items:
   slug: actions-braze-cohorts
   hidden: false
   endpoints:
+  - EU
   - US
   regions:
   - us-west-2
@@ -22973,7 +22975,7 @@ items:
   display_name: Display and Video 360 (Actions)
   name: Display and Video 360 (Actions)
   slug: display-and-video-360-actions
-  hidden: false
+  hidden: true
   endpoints:
   - US
   regions:
@@ -22984,18 +22986,19 @@ items:
   - Display and Video 360 (Actions)
   website: http://www.segment.com
   status: PUBLIC_BETA
-  categories: []
+  categories:
+  - Advertising
   logo:
     url: https://cdn-devcenter.segment.com/60ac526b-8825-440f-963e-d2610b4aa33d.svg
   mark:
     url: https://cdn-devcenter.segment.com/32cd0b20-9505-4e55-a637-bb199faf9fd0.svg
   methods:
     track: true
     identify: false
-    group: true
-    alias: true
+    group: false
+    alias: false
     screen: false
-    page: true
+    page: false
   platforms:
     browser: true
     mobile: false
@@ -33067,7 +33070,7 @@ items:
   display_name: Gleap (Action)
   name: Gleap (Action)
   slug: gleap-action
-  hidden: false
+  hidden: true
   endpoints:
   - US
   regions:
@@ -63052,7 +63055,7 @@ items:
   display_name: Pendo Web (Actions)
   name: Pendo Web (Actions)
   slug: pendo-web-actions
-  hidden: false
+  hidden: true
   endpoints:
   - US
   regions:
diff --git a/src/_data/catalog/destinations_private.yml b/src/_data/catalog/destinations_private.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2024-01-30 
+# destination data last updated 2024-02-01 
 items:
   - id: 54521fd725e721e32a72eec6
     display_name: Intercom
diff --git a/src/_data/catalog/source_categories.yml b/src/_data/catalog/source_categories.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# source categories last updated 2024-01-30 
+# source categories last updated 2024-02-01 
 items:
   - display_name: A/B Testing
     slug: a-b-testing
diff --git a/src/_data/catalog/sources.yml b/src/_data/catalog/sources.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# sources last updated 2024-01-30 
+# sources last updated 2024-02-01 
 items:
   - id: 8HWbgPTt3k
     display_name: .NET
@@ -1929,7 +1929,7 @@ items:
     description: Seamless Surveys Meet Powerful Analytics
     logo:
       url: >-
-        https://cdn-devcenter.segment.com/278e564b-13e9-4a4a-bb10-7ff8b1aadee2.svg
+        https://cdn-devcenter.segment.com/12e61c05-818d-48ff-a7a8-7e80b9ba34ba.svg
     categories:
       - Surveys
       - Customer Success
diff --git a/src/_includes/content/warehouse-ip.html b/src/_includes/content/warehouse-ip.html
@@ -2,12 +2,14 @@
   <div class="fa fa-exclamation-circle"></div>
   <div class="content">
     <p class="header">Update your warehouse allowlist for with new IP addresses</p>
-    <p>Starting on November 14, 2023 all warehouse customers who use allowlists in their warehouses must update those lists to include the following ranges:</p>
+    <p>Starting on November 14, 2023 all warehouse customers who use allowlists in their US warehouses must update those lists to include the following ranges:</p>
     <ul>
       <li><code class="language-plaintext highlighter-rouge">52.25.130.38/32</code></li>
       <li><code class="language-plaintext highlighter-rouge">34.223.203.0/28</code></li>
     </ul>
 
+    <p>Customers with warehouses in the EU must allowlist <code class="language-plaintext highlighter-rouge">3.251.148.96/29</code>.</p>
+
     <p>These updates coincide with reliability improvements to Segment's underlying warehouse architecture.</p>
 
 
diff --git a/src/connections/delivery-overview.md b/src/connections/delivery-overview.md
@@ -24,7 +24,7 @@ The pipeline view shows the following steps:
 - **Successfully received**: Events that Segment ingested from your source
 - **Failed on ingest**: Events that Segment received, but were dropped due to internal data validation rules
 - **Filtered at source**: Events that were discarded due to schema settings or [Protocols](/docs/protocols/) Tracking Plans
-- **Filtered at destination**: Events that were discarded due to [Destination Filters](/docs/guides/filtering-data/#destination-filters), [filtering in the Integrations object](/docs/guides/filtering-data/#filtering-with-the-integrations-object), or [per source schema integration filters](/docs/guides/filtering-data/#per-source-schema-integrations-filters). [Actions destinations](/docs/connections/destinations/actions/) also have a filtering capability: for example, if your Action is set to only send Identify events, all other event types will be filtered out. Actions destinations with incomplete triggers or disabled mappings are filtered out at this step. <!--- Beta users of [Consent Management](/docs/privacy/consent-management/) also see events discarded due to consent preferences.--->
+- **Filtered at destination**: Events that were discarded due to [Destination Filters](/docs/guides/filtering-data/#destination-filters), [filtering in the Integrations object](/docs/guides/filtering-data/#filtering-with-the-integrations-object), or [per source schema integration filters](/docs/guides/filtering-data/#per-source-schema-integrations-filters). [Actions destinations](/docs/connections/destinations/actions/) also have a filtering capability: for example, if your Action is set to only send Identify events, all other event types will be filtered out. Actions destinations with incomplete triggers or disabled mappings are filtered out at this step. Beta users of [Consent Management](/docs/privacy/consent-management/) also see events discarded due to consent preferences.
 - **Failed delivery**: Events that have been discarded due to errors or unmet destination requirements
 - **Successful delivery**: Events that were successfully delivered to the destination
 
diff --git a/src/connections/destinations/catalog/actions-google-analytics-4-web/index.md b/src/connections/destinations/catalog/actions-google-analytics-4-web/index.md
@@ -37,7 +37,7 @@ Some parameters automatically populate prebuilt [dimensions and metrics](https:/
 
 Google Analytics 4 requires the use of [recommended events](https://support.google.com/analytics/answer/9267735){:target="_blank"} and properties to power certain built-in reports. Segment’s Google Analytics 4 Web destination provides prebuilt mappings to automatically map your Segment spec events to the corresponding Google Analytics 4 events and properties. If your Segment events don’t follow the Segment spec exactly, you can modify the mappings. For example, Segment maps `Order Completed` events to the Google Analytics 4 `Purchase` event by default. If your company uses `Products Purchase` to indicate a purchase, you can map it in the Purchase action’s Event Trigger instead.
 
-Segment recommends using the prebuilt mappings when possible. However, the Segment spec doesn’t have an equivalent event for every Google Analytics 4 recommended event. If there are other recommended events you'd like to send, use the [Custom Event action](/docs/connections/destinations/catalog/actions-google-analytics-4-web/#custom-event). For example, to send a `spend_virtual_currency` event, create a mapping for Custom Event, set up your Event Trigger criteria, and input a literal string of `spend_virtual_currency` as the Event Name. You can use the Event Parameters object to add fields that are in the `spend_virtual_currency` event such as `value` and `virtual_currency_name`. You'll need to define custom parameteres as [custom dimensions and metrics](/docs/connections/destinations/catalog/actions-google-analytics-4-web/#custom-dimensions-and-metrics) in your GA4 workspace first. 
+Segment recommends using the prebuilt mappings when possible. However, the Segment spec doesn’t have an equivalent event for every Google Analytics 4 recommended event. If there are other recommended events you'd like to send, use the [Custom Event action](/docs/connections/destinations/catalog/actions-google-analytics-4-web/#custom-event). For example, to send a `spend_virtual_currency` event, create a mapping for Custom Event, set up your Event Trigger criteria, and input a literal string of `spend_virtual_currency` as the Event Name. You can use the Event Parameters object to add fields that are in the `spend_virtual_currency` event such as `value` and `virtual_currency_name`. Remember to define custom parameters as [custom dimensions and metrics](/docs/connections/destinations/catalog/actions-google-analytics-4-web/#custom-dimensions-and-metrics) in your GA4 workspace first.
 
 ### Custom events
 
diff --git a/src/connections/destinations/catalog/actions-slack/index.md b/src/connections/destinations/catalog/actions-slack/index.md
@@ -7,7 +7,7 @@ redirect_from:
   - '/connections/destinations/catalog/vendor-slack'
 versions:
   - name: Slack (Classic)
-    link: /docs/connections/destinations/slack
+    link: /docs/connections/destinations/catalog/slack/
 ---
 {% include content/plan-grid.md name="actions" %}
 
@@ -44,4 +44,4 @@ Follow the table below to map your existing Slack destination configuration to S
 > warning ""
 > Slack (Actions) uses [Slack's  formatting syntax](https://api.slack.com/reference/surfaces/formatting){:target="_blank"}. This requires that you manually re-enter any messages from Slack Classic, and pick event data from the event variable picker. The handlebars syntax from Slack Classic is not compatible.
 
-{% include components/actions-map-table.html name="slack" %}
+{% include components/actions-map-table.html name="slack" %}
diff --git a/src/connections/destinations/catalog/marketo-v2/index.md b/src/connections/destinations/catalog/marketo-v2/index.md
@@ -71,6 +71,9 @@ There are additional steps you must take to send `.identify()` calls in Device-m
 2. Input the associated **Marketo Form ID** and **Marketo Form URL** in your Marketo V2 Destination settings. This information can be found in Form Actions > Embed Code in the Marketo Design Studio:
 ![A screenshot of the Embed Code popup in Marketo.](images/form-info.png)
 
+> info ""
+> **Marketo Form ID** and **Marketo Form URL** are **required** fields for the Marketo SDK to initialize on your site. If these fields are left blank, the SDK will not initialize and data will not be sent downstream. 
+
 ### Traits
 Regardless of connection mode, we'll map the following spec'd Segment traits to Marketo's standard fields:
 
diff --git a/src/connections/sources/catalog/libraries/server/csharp/migration-guide.md b/src/connections/sources/catalog/libraries/server/csharp/migration-guide.md
@@ -5,6 +5,9 @@ strat: csharp
 
 If you’re currently using Analytics.NET or Analytics.Xamarin to send data to Segment, please follow the steps below to migrate to the [Analytics-CSharp library](/docs/connections/sources/catalog/libraries/server/csharp/).  
 
+> success ""
+> Analytics-C# does not include `v1` as part of the `url` address. If you are using the Segment EU endpoint, you will have to pass it manually. For instance, `events.eu1.segmentapis.com/v1`
+
 You can update to Analytics-CSharp in 3 steps:
 1. Bundle Analytics-CSharp into your app and remove your previous SDK.
 2. Change the namespaces.
diff --git a/src/connections/sources/catalog/libraries/website/javascript/custom-proxy.md b/src/connections/sources/catalog/libraries/website/javascript/custom-proxy.md
@@ -44,12 +44,8 @@ Hi,
 
 This is {person} from {company}. I would like to configure a proxy for the following source(s):
 
-* Source URL with Source ID
-* Source URL with Source ID
-```
-
-- **Source URL**: link to the source in your Segment workspace (for example, `https://app.segment.com/<your_slug>/sources/<source>/overview`)
-- **Source ID**: navigate to **API Keys** on the left-hand side of the source **Settings** and provide the Source ID
+**Source URL**: link to the source in your Segment workspace (for example: https://app.segment.com/<your_slug>/sources/<source>/overview)
+**Source ID**: navigate to **API Keys** on the left-hand side of the source **Settings** and provide the Source ID 
 
 Double-check the Source URL and the Source ID.
 
@@ -67,7 +63,7 @@ Follow these instructions after setting up a proxy such as [CloudFront](#custom-
 > If you've followed the instructions above to have a Segment team member enable the apiHost settings in the UI, you can skip the instructions in this section. 
 
 ### Snippet instructions
-If you're a snippet user, you need to modify the [analytics snippet](/docs/getting-started/02-simple-install/#step-1-copy-the-snippet) that's inside your `<head>`.
+If you're a snippet user, modify the [analytics snippet](/docs/getting-started/02-simple-install/#step-1-copy-the-snippet) located inside the `<head>` of your website:
 
 To proxy CDN settings and destination requests that typically go to `https://cdn.segment.com`, replace:
 ```diff
@@ -82,9 +78,9 @@ To proxy API tracking calls that typically go to `api.segment.io/v1`, replace:
 ```
 
 ### npm instructions
-See the [`npm` library-users instructions](https://www.npmjs.com/package/@segment/analytics-next){:target="_blank"} for more information.
+If you're using the [npm library](https://www.npmjs.com/package/@segment/analytics-next){:target="_blank"}, make the following changes directly in your code:
 
-Proxy settings and destination requests that typically go to `https://cdn.segment.com` through a custom proxy.
+To proxy settings and destination requests that typically go to `https://cdn.segment.com` through a custom proxy:
 
 ```ts
 const analytics = AnalyticsBrowser.load({
@@ -98,7 +94,7 @@ const analytics = AnalyticsBrowser.load({
  })
 ```
 
-Proxy tracking calls that typically go to `api.segment.io/v1` by configuring `integrations['Segment.io'].apiHost`.
+To proxy tracking calls that typically go to `api.segment.io/v1`, configure the `integrations['Segment.io'].apiHost`:
 ```ts
 const analytics = AnalyticsBrowser.load(
     {
@@ -177,4 +173,5 @@ To add a CNAME record to your DNS settings:
 Follow the instructions at [Using Analytics.js as an NPM Package](https://github.com/segmentio/analytics-next/tree/master/packages/browser#-using-as-an-npm-package), to host Analytics.js and eliminate the requirement of downloading it from the CDN file during every page load. This enables you to self-host/import the library itself.
 
 > warning ""
-> Segment does not recommend self-hosting, as it requires that you configure integration settings individually and manually redeploy Analytics.js when there are changes to your settings. When you enable third-party libraries in device-mode, Segment loads them, which defeats the purpose of self-hosting. 
+> Segment does not recommend self-hosting, as it requires that you configure integration settings individually and manually redeploy Analytics.js when there are changes to your settings. Self-hosting your own Analytics.js instead of using the CDN means that you lose the automatic downstream updates to your analytics when you make changes. Self-hosting means that you must configure the settings for each integration directly and redeploy your Analytics.js any time you make changes to your settings. When you enable third-party libraries in device-mode, Segment loads them for you, which defeats the purpose of self-hosting.
+
diff --git a/src/connections/sources/catalog/libraries/website/javascript/index.md b/src/connections/sources/catalog/libraries/website/javascript/index.md
@@ -14,6 +14,9 @@ Analytics.js enables you to send your data to hundreds of [destination tools](/d
 
 Segment's Analytics.js library is fully open-source and can be viewed on [GitHub](https://github.com/segmentio/analytics-next/){:target="_blank"}.
 
+## Getting started
+
+Use the [Analytics.js QuickStart Guide](/docs/connections/sources/catalog/libraries/website/javascript/quickstart/) to learn how to add Analytics.js to your site. Once you've installed the library, read on for the detailed API reference.
 
 ## Benefits of Analytics.js
 
@@ -26,7 +29,6 @@ Analytics.js reduces page load time and improves site performance. Its package s
 > info ""
 > Many factors impact page load time, including network conditions, hosting locations, and page weight. Page weight for each customer integration varies based on the number of device-mode destinations that are enabled for each source. The more device-mode destinations that are enabled, the more data gets added to the library, which will impact the weight of the library.
 
-
 ### Developer experience
 
 Analytics.js improves developer experience by introducing new ways for developers to augment events throughout the event timeline. For example, developers can augment events either before or after an event occurs, or while the event is in-flight.
@@ -37,10 +39,6 @@ For example, you can use Analytics.js to build features that:
 - Enrich events with customer or page context while in-flight with middleware
 - Check an event for errors after the event is sent to Segment
 
-## Getting started
-
-Use the [Analytics.js QuickStart Guide](/docs/connections/sources/catalog/libraries/website/javascript/quickstart/) to learn how to add Analytics.js to your site. Once you've installed the library, read on for the detailed API reference.
-
 ## Basic tracking methods
 
 The basic tracking methods below serve as the building blocks of your Segment tracking. They include [Identify](#identify), [Track](#track), [Page](#page), [Group](#group), and [Alias](#alias).
diff --git a/src/connections/sources/catalog/libraries/website/shopify-littledata/index.md b/src/connections/sources/catalog/libraries/website/shopify-littledata/index.md
@@ -52,9 +52,6 @@ Here's an architecture diagram that shows how the Littledata app mediates data f
 7. Segment's **Analytics.js** library, Littledata **tracking script** and **webhooks** will be automatically applied to the store and the installation process will then be complete.
    ![Screenshot of adding AnalyticsJS to Shopify](images/kvjNx4M.png)
 
-## Event schema
-
-This source has a full [tracking plan and event schema](https://docs.google.com/spreadsheets/d/1aljowRhMU9_7uGXmcipbP1Y14S4cOSdXGQA2Vx7BHko/edit){:target="\_blank"} in Google Sheets, which is ready to [upload into Protocols](/docs/protocols/apis-and-extensions/#google-sheets-tracking-plan-uploader).
 
 ## Device-mode events
 
diff --git a/src/connections/storage/catalog/aws-s3/index.md b/src/connections/storage/catalog/aws-s3/index.md
@@ -488,4 +488,10 @@ For user-property destinations, Segment sends an [identify](/docs/connections/sp
 
 When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs send updates for users whose membership has changed since the last sync.
 
+## FAQ
+
+### AWS S3 destination connection error “Multiple instance of AWS S3 are not allowed for this source"
+
+You might encounter this error if you already have a S3 destination connected to the source in question. Segment only supports one AWS S3 destination per source.
+
 {% include content/destination-footer.md %}
diff --git a/src/connections/storage/catalog/redshift/index.md b/src/connections/storage/catalog/redshift/index.md
@@ -148,6 +148,12 @@ You can also unload data to a s3 bucket and then load the data into another Reds
 
 Segment does not currently support SSH tunneling to Redshift. You can usually allow Segment's ETL to write to Redshift without leaving the cluster available to other connections by using IP level restrictions.
 
+Segment supports several layers of Redshift's security model:
+
+ - **Security groups**: Security groups control the incoming and outgoing traffic to a resource. You can think of this like a pinhole in a firewall that only allows traffic from Segment's IP address. Security groups are a fundamental building block of AWS security.
+- **SSL**:  This secures data in transit and allows Segment to validate that the warehouse at the other end is actually a warehouse owned by AWS. This is especially important if your Redshift warehouse is not located in the `us-west-2` region.
+- **Username and password**: This is the basic method used to authenticate database users and apply varying levels of permissions - for example, who can create tables, who can delete data, who can see which tables.
+
 ### Do you support Redshift Serverless?
 
 Segment does not currently support Serverless Redshift. While you can set up the connection in the Segment app, Segment does not have the functionality to query Redshift's SYS tables.
diff --git a/src/guides/regional-segment.md b/src/guides/regional-segment.md
diff --git a/src/privacy/configure-consent-management.md b/src/privacy/configure-consent-management.md
diff --git a/src/privacy/consent-in-segment-connections.md b/src/privacy/consent-in-segment-connections.md
diff --git a/src/privacy/consent-in-unify.md b/src/privacy/consent-in-unify.md
diff --git a/src/privacy/consent-management.md b/src/privacy/consent-management.md
diff --git a/src/unify/linked-profiles/data-graph.md b/src/unify/linked-profiles/data-graph.md
diff --git a/src/unify/linked-profiles/linked-events.md b/src/unify/linked-profiles/linked-events.md
