Merge pull request #6523 from segmentio/develop

forstisabella · web-flow · commit dd44057cdefc · 2024-05-09T15:03:09.000-04:00
Release 24.19.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-05-07 
+# destination categories last updated 2024-05-09 
 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-05-07 
+# destination data last updated 2024-05-09 
 items:
 - id: 637e8d185e2dec264895ea89
   display_name: 1Flow
@@ -72119,15 +72119,16 @@ items:
     type: string
     defaultValue: ''
     description: >-
-      To find your API key, log into Pendo and navigate to “your user name” >
-      Site settings > Basic Information > API key. If your account has not fully
-      been set up yet, you can see the API key inside of the code snippet on the
-      Pendo setup page.
+      To find your API key, have a Pendo admin log into Pendo, navigate to
+      Settings > Subscription Settings > Applications, open the relevant app,
+      and locate the API key value. If your account has not fully been set up
+      yet, you can see the API key inside of the code snippet on the Pendo setup
+      page.
     required: false
     label: API Key
   actions: []
   presets: []
-  partnerOwned: false
+  partnerOwned: true
 - id: 6501a4325a8a629197cdd691
   display_name: Pendo Web (Actions)
   name: Pendo Web (Actions)
@@ -91446,6 +91447,15 @@ items:
       settings](https://app.startdeliver.com/settings/apikeys)
     required: true
     label: Startdeliver API-key
+  - name: segmentOverrideMatchingField
+    type: string
+    defaultValue: ''
+    description: >-
+      If you do not wish to match Track/Screen/Page-Usage events on the
+      Segment-event key `userId` you can enter another field to match here. For
+      example `properties.myCustomField` or `properties['Field With Space']`
+    required: false
+    label: Override Segment Matching-value from "userId" to another field.
   - name: startdeliverUserCustomFieldToMatchOn
     type: string
     defaultValue: ''
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-05-07 
+# destination data last updated 2024-05-09 
 items:
   - id: 54521fd925e721e32a72eee1
     display_name: Pardot
diff --git a/src/_data/catalog/regional-supported.yml b/src/_data/catalog/regional-supported.yml
@@ -98,7 +98,7 @@ sources:
       - us
   - id: xNpohElkX2
     display_name: Azure
-    hidden: false
+    hidden: true
     slug: azure
     url: connections/sources/catalog/cloud-apps/azure
     regions:
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-05-07 
+# source categories last updated 2024-05-09 
 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-05-07 
+# sources last updated 2024-05-09 
 items:
   - id: 8HWbgPTt3k
     display_name: .NET
@@ -198,7 +198,7 @@ items:
     isCloudEventSource: false
     slug: azure
     url: connections/sources/catalog/cloud-apps/azure
-    hidden: false
+    hidden: true
     regions:
       - us
     endpoints:
diff --git a/src/connections/destinations/catalog/actions-display-video-360/index.md b/src/connections/destinations/catalog/actions-display-video-360/index.md
@@ -150,6 +150,8 @@ With consent mode, you can configure your website to dynamically adjust the trac
 
 Segment automatically sends consent as `TRUE` for this destination.  Segment uses the [bulk-uploader workflow](https://developers.google.com/authorized-buyers/rtb/bulk-uploader#workflow){:target="_blank"} which requires consented data. Ensure all audiences and journeys are connected to consented audiences.  
 
+{% include components/actions-fields.html %}
+
 ## FAQ
 ### What is Segment's relationship with Google DV360 and is the data that Segment sends considered to be First or Third party?
 
diff --git a/src/connections/destinations/catalog/actions-stackadapt/index.md b/src/connections/destinations/catalog/actions-stackadapt/index.md
@@ -156,7 +156,7 @@ This is necessary when using backend SDKs but not for events sent from the front
 
 When sending past events to StackAdapt using a Reverse ETL tool, the user agent, IP address, event type, and either the page URL (for conversion trackers with URL rules), or the fields the event rules match on, must be included in your mappings. For example, the below mapping for a Snowflake source can be used to match a conversion tracker with an event rule that matches an `action` of `User Registered`:
 
-![Image showing Snowflake mapping to forward User Registered events](images/snowflake-mapping.png)
+![Image showing Snowflake mapping to forward User Registered events](images/snowflake-mappings.png)
 
 Rows forwarded to StackAdapt with this mapping will be matched by the `User Registered` event rule shown below:
 
diff --git a/src/connections/sources/catalog/cloud-apps/azure/index.md b/src/connections/sources/catalog/cloud-apps/azure/index.md
@@ -0,0 +1,6 @@
+---
+title: 'Azure Source'
+hidden: true
+published: false
+id: xNpohElkX2
+---
diff --git a/src/connections/sources/images/source-overview.jpeg b/src/connections/sources/images/source-overview.jpeg
diff --git a/src/connections/sources/images/source-overview.png b/src/connections/sources/images/source-overview.png
diff --git a/src/connections/sources/index.md b/src/connections/sources/index.md
@@ -49,7 +49,7 @@ analytics.identify('user_123', {
 {% endcomment %}
 
 > info "If you don't see the source you're looking for in our catalog"
-> If a tool is not listed as a supported source in our [catalog](https://segment.com/catalog/){:target='_blank’}, then it is not possible to incorporate the integration out-of-the-box within a Segment workspace. However, as an alternative, you can use the [HTTP API](/docs/connections/sources/catalog/libraries/server/http-api/) source to collect data from the tool's API. You can also use [Functions](/docs/connections/functions/) to send or receive data from other tools.
+> If a tool is not listed as a supported source in Segment's [catalog](https://segment.com/catalog/){:target='_blank’}, then it is not possible to incorporate the integration out-of-the-box within a Segment workspace. However, as an alternative, you can use the [HTTP API](/docs/connections/sources/catalog/libraries/server/http-api/) source to collect data from the tool's API. You can also use [Functions](/docs/connections/functions/) to send or receive data from other tools.
 
 ## Types of sources
 
@@ -79,18 +79,30 @@ Event streams sources collect data from your website or app to monitor user acti
 
 ### Source Overview
 
-When viewing the Source Overview page for an event stream source, you can view a line chart and breakdown table that reflects the volume and details of the events that Segment ingested from your source.
+The Source Overview page for an event stream source shows you a [pipeline view](#pipeline-view) of all events Segment receives from your source, events that failed on ingest, events that are filtered at the source level, and "eligible events", which are the events that will flow into your destinations. If you select one of the steps in the pipeline view, you can see a line chart that reflects the fluctuations in volume alongside a [breakdown table](#breakdown-table) that has more details about the events impacted by the selected step.
 
-You can use the time picker located on the Source Overview page to specify a time period (last 10 minutes, 1 hour, 24 hours, 7 days, 2 weeks, or a custom date range over the last two weeks) for which you’d like to see data.
+#### Pipeline view
 
-![A screenshot of the Source Overview page for an Android source.](images/source-overview.jpeg)
+The pipeline view shows each of the four steps Segment encounters when processing data from your source: 
 
-The breakdown table displays the following details:
-* **Event type**: The Segment Spec event type (Track call vs. Identify call, for example).
-* **Event name**: The event name, provided by you or the source. You should only expect to see track calls with event names. If you see unnamed events in the breakdown table, it's because for other specs, you're either identifying users/groups or tracking what page/screen the user is on. Both of which do not have event names. The exception to this is if you provide a name in the Page call. Named Page calls also show up in this section with the name of the Page as the event name. 
-<!-- NOT SUPPORTED IN CURRENT VERSION: ADD IN ONCE THIS IS SUPPORTED* **App version**: The app/release version, provided by you or the source-->
-* **Event count**: How many of each event was successfully received by your source.
-* **% Change**: Insight into how the event counts differ from the last comparable time range as a percentage.
+- **Events successfully received**: All events that Segment received from your source.
+- **Failed on ingest**: Events that failed at the Tracking API level. For more information about errors that might cause events to fail on ingest, see Delivery Overview's [Troubleshooting](/docs/connections/delivery-overview/#troubleshooting) documentation.
+- **Filtered at source**: Events that were filtered out by source schema controls, Tracking Plans, or a common JSON schema.
+- **Eligible events**: Eligible events are the events that flow downstream to your Segment destinations. This value is read-only, but you can see the events that flow downstream to a particular destination using [Delivery Overview](/docs/connections/delivery-overview).
+
+> success ""
+> You can use the time picker located on the Source Overview page to specify a time period (last 10 minutes, 1 hour, 24 hours, 7 days, 2 weeks, or a custom date range over the last two weeks) for which you’d like to see data. Segment sets the time picker to show data for the last 24 hours by default. 
+
+![A screenshot of the Source Overview page for an Go source, with the Failed on ingest step selected.](images/source-overview.png)
+
+#### Breakdown table
+
+The breakdown table displays three tabs, **Event type**, **Event name**, and **App version**. 
+* **Event type**: The Segment Spec event type (Track call vs. Identify call, for example). _This tab also contains a "% change" metric, which displays how the event counts differ from the last comparable time range, represented as a percentage._
+* **Event name**: The event name, provided by you or the source.
+* **App version**: The app/release version, provided by you or the source. 
+
+Each of these tabs displays an event count, which is the total number of events that Segment received in a particular step. 
 
 ### Website libraries
 
diff --git a/src/privacy/faq.md b/src/privacy/faq.md
@@ -69,3 +69,12 @@ If you have the Amplitude destination enabled in one or more sources, you must i
 
 #### Google Analytics
 To send user deletion requests to Google Analytics you must authenticate your Google Analytics account with Segment using OAuth. If you have the Google Analytics destination enabled in one or more sources, you must authenticate your account in each destination(s) settings. Navigate to the **User Deletion** settings in your Segment Google Analytics settings and use your email and password to authenticate your account.
+
+### What regulation types does Segment support?
+
+Segment supports the following regulation types:
+- **SUPPRESS_ONLY**: Suppress new data based on the `userId` without deleting existing data stored in your workspace and in downstream destinations.
+- **UNSUPPRESS**: Stop the ongoing suppression of a `userId`.
+- **SUPPRESS_WITH_DELETE**: Suppress new data based on the `userId` and also delete all existing data for that ID from your workspace and our internal archives. While Segment forwards the deletion request to your downstream destinations, Segment cannot guarantee deletion in your third-party tools.
+- **DELETE_INTERNAL**: Deletes user data from within Segment archives only and not from any connected destinations.
+- **DELETE_ONLY**: Deletes user data from Segment and your connected warehouses. Also sends a deletion request to your downstream destinations.
