Release 25.45.2

src/connections/delivery-overview.md

@@ -48,14 +48,25 @@ The pipeline view for storage destination includes the following steps:
 - **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), [Destination Insert functions](/docs/connections/functions/insert-functions/), 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. [Consent Management](/docs/privacy/consent-management/) users also see events discarded due to consent preferences.
-- **Events to warehouse rows**: A read-only box that shows the point in the delivery process where Segment converts events into warehouse rows.
+- **Events pending retry**: A read-only box that shows the number of events that are awaiting retry. 
 - **Failed to sync**: Syncs that either failed to sync or were partially successful. Selecting this step takes you to a table of all syncs with one or more failed collections. Select a sync from the table to view the discard reason, any collections that failed, the status, and the number of rows that synced for each collection. For information about common errors, see Ware
-- **Successfully synced**: A record of all successful or partially successful syncs made with your destination. To view the reason a partially successfully sync was not fully successful, see the Failed to sync step. 
+- **Successfully synced**: A record of all successful or partially successful syncs made with your destination. To view the reason a partially successfully sync was not fully successful, see the Failed to sync step.
 
 The following image shows a storage destination with 23 partially successful syncs: 
 
 ![A screenshot of the Delivery Overview tab for a Storage destination, with the Failed to sync step selected and a table of partially successful syncs.](images/delivery-overview-storage-destinations.png)
 
+##### Linked Audiences to Snowflake destination
+
+You can view information about events sent from Linked Audiences downstream to the Snowflake destination with the following pipeline view: 
+
+- **Events from audience**: Events that Segment created for your activation. The number of events for each compute depends on the changes detected in your audience membership.
+- **Filtered at source**: Events discarded by Protocols: either by the [schema settings](/docs/protocols/enforce/schema-configuration/) or [Tracking Plans](/docs/protocols/tracking-plan/create/). 
+- **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), [Destination Insert functions](/docs/connections/functions/insert-functions/), 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. [Consent Management](/docs/privacy/consent-management/) users also see events discarded due to consent preferences.
+- **Events pending retry**: A read-only box that shows the number of events that are awaiting retry. 
+- **Failed delivery**: Events that have been discarded due to errors or unmet destination requirements. Select a discard reason from the table to view all events that failed, sorted by collection. For information about common errors, see [Warehouse Errors](/docs/connections/storage/warehouses/warehouse-errors).
+- **Successful delivery**: Events that were successfully delivered to Snowflake. 
+
 #### Destinations connected to Engage Destinations
 
 > info "Delivery Overview for Engage Destinations is in Public Beta"
@@ -151,4 +162,4 @@ The Delivery Overview pipeline steps Failed on Ingest, Filtered at Source, Filte
 This table provides a list of all possible discard reasons available at each pipeline step. 
 
 {% include content/delivery-overview-discards.html %}
-<!--- not in the product yet{% include content/retl-discards.md %}--->
+<!--- not in the product yet{% include content/retl-discards.md %}--->

src/connections/destinations/catalog/actions-braze-cloud/index.md

@@ -16,7 +16,7 @@ versions:
 [Braze](https://www.braze.com/){:target="_blank"}, formerly Appboy, is an engagement platform that empowers growth by helping marketing teams to build customer loyalty through mobile, omni-channel customer experiences.
 
 > success ""
-> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Braze Segment destination. There's also a page about the [non-Actions Braze destination](/docs/connections/destinations/catalog/braze/). Both of these destinations receives data _from_ Segment. There's also the [Braze source](/docs/connections/sources/catalog/cloud-apps/braze//), which sends data _to_ Segment!
+> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Braze Segment destination. There's also a page about the [non-Actions Braze destination](/docs/connections/destinations/catalog/braze/). Both of these destinations receives data _from_ Segment. There's also the [Braze source](/docs/connections/sources/catalog/cloud-apps/braze/), which sends data _to_ Segment!
 
 ## Benefits of Braze Cloud-Mode (Actions) vs Braze (Classic)
 
@@ -77,4 +77,4 @@ Braze requires one of either `external_id`, `user_alias`, or `braze_id` to be pr
 #### Missing events
 When an event is sent under an alias, it might appear to be missing if the alias cannot be found in Braze. This might be due to an incorrect search for the alias in Braze. 
 
-To search for an alias in Braze, use the format `Alias Label:Alias Name`. For example, if the "Alias Label" field is set as email and "Alias Name" field is set as email address, for example: "test@email.com", you should search for the alias using "email:test@email.com".
+To search for an alias in Braze, use the format `Alias Label:Alias Name`. For example, if the "Alias Label" field is set as email and "Alias Name" field is set as email address, for example: "test@email.com", you should search for the alias using "email:test@email.com".

src/connections/destinations/catalog/actions-ms-bing-capi/index.md

@@ -16,8 +16,8 @@ redirect_from: "/connections/destinations/catalog/microsoft-bing-capi/"
 3. Select an existing source to connect to the destination.
 4. Give the destination a name and click **Create destination**.
 5. In **Basic Settings**, enter the Bing **UetTag** and **ApiToken**.
-    > * To find the UET tag, see Microsoft's steps on [how to create a UET tag](https://help.ads.microsoft.com/#apex/3/en/56682/2-500){:target="_blank"}. 
-    > * To generate the API token, contact [Microsoft support](https://about.ads.microsoft.com/en/support){:target="_blank"} or fill out a [request form](https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbRwMZAe0PcMxHmZ0AjDaNRmxUM0o5UURRVktCRkxHNEFLTVNYQjI3NDNBUS4u){:target="_blank"}.
+    * To find the UET tag, see Microsoft's steps on [how to create a UET tag](https://help.ads.microsoft.com/#apex/3/en/56682/2-500){:target="_blank"}. 
+    * To generate the API token, contact [Microsoft support](https://about.ads.microsoft.com/en/support){:target="_blank"} or fill out a [request form](https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbRwMZAe0PcMxHmZ0AjDaNRmxUM0o5UURRVktCRkxHNEFLTVNYQjI3NDNBUS4u){:target="_blank"}.
 6. Toggle **Enable Destination** on to start sending data to Microsoft Bing CAPI from Segment.
 
 {% include components/actions-fields.html %}

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

@@ -1,8 +1,8 @@
 ---
 title: AWS S3 (Actions) Destination
-hide-boilerplate: true
-hide-dossier: false
 id: 66eaa166f650644f04389e2c
+hide-boilerplate: true
+hide-dossier: true
 private: true
 beta: true
 # versions:

src/connections/destinations/catalog/actions-stackadapt-audiences/index.md

@@ -9,7 +9,7 @@ redirect_from: "/connections/destinations/catalog/actions-stackadapt/"
 
 {% include content/plan-grid.md name="actions" %}
 
-[StackAdapt](https://www.stackadapt.com/){:target="_blank"} is a leading programmatic advertising platform designed to maximize audience engagement. It enables marketers to run high-performing, cross-channel campaigns through real-time bidding, advanced audience targeting, and powerful data-driven insights.  
+[StackAdapt](https://www.stackadapt.com/){:target="\_blank"} is a leading programmatic advertising platform designed to maximize audience engagement. It enables marketers to run high-performing, cross-channel campaigns through real-time bidding, advanced audience targeting, and powerful data-driven insights.
 
 With the [Engage](/docs/engage/) integration, you can seamlessly sync your Engage Audiences and user data with StackAdapt to refine targeting precision and drive stronger campaign performance.
 
@@ -60,6 +60,9 @@ Each Engage audience should only contain profiles that have a valid email addres
    - Select the source field for `Standard User Properties`. Ensure the source field matches the profile traits selected in step 4. You can learn more about the field format by hovering over the info icon of the field.
    - Follow the Destinations Actions documentation to [customize mappings](/docs/connections/destinations/actions/#customize-mappings).
 
+> note "Trait synchronization"
+> Both Custom, Computed, and Consent Traits are mapped and included in the initial data synchronization. However, for ongoing updates, please be aware that only Computed Traits will be updated within StackAdapt's Data Hub.
+
 To verify that your audience syncs with StackAdapt, open StackAdapt and navigate to **Audience & Attribution > Customer Data > Profiles**. On the Profiles tab, you should be able to see a list of profiles being synced to the StackAdapt platform.
 
 > info "Syncs can take up to 4 hours"

src/connections/destinations/catalog/criteo-app-web-events/index.md

@@ -395,4 +395,4 @@ Criteo Events can receive dates in a specific format, in order for us to pass al
 
 ### Is the mobile integration bundled?
 
-Even though we don't support integrating with Criteo Events using Segment from a server source, it's still not necessary for you to [bundle](/docs/connections/spec/mobile-packaging-sdks//) the Criteo Events SDK into the Segment SDK! This is because while our mobile integration with them is powered from our servers, the integration requires metadata that can only be supplied by the user's mobile device (which is collected and passed along automatically by the Segment mobile SDK).
+Even though we don't support integrating with Criteo Events using Segment from a server source, it's still not necessary for you to [bundle](/docs/connections/spec/mobile-packaging-sdks/) the Criteo Events SDK into the Segment SDK! This is because while our mobile integration with them is powered from our servers, the integration requires metadata that can only be supplied by the user's mobile device (which is collected and passed along automatically by the Segment mobile SDK).

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

@@ -1,6 +1,7 @@
 ---
 title: SatisMeter Destination
 id: 54c02a5adb31d978f14a7f6f
+hide-dossier: true
 ---
 [Our SatisMeter destination code](https://github.com/segment-integrations/analytics.js-integration-satismeter){:target="_blank"} is all open-source on GitHub if you want to check it out.
 

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

@@ -75,6 +75,6 @@ To more details how Wishpond's identify works  visit [Wishpond API Docs: #track]
 
 Make sure you have copied the right keys from Wishpond's ["API Keys" dialog](https://www.wishpond.com/central/welcome?api_keys=true){:target="_blank"}, this destination will need `Merchant ID` and `Tracking Key`.
 
-[Analytics.js]: https://segment.com//docs/connections/sources/catalog/libraries/website/javascript/
+[Analytics.js]: https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/
 [ci-link]: https://circleci.com/gh/segment-integrations/analytics.js-integration-wishpond
 [ci-badge]: https://circleci.com/gh/segment-integrations/analytics.js-integration-wishpond.svg?style=svg

src/connections/sources/catalog/cloud-apps/rise-ai/index.md

@@ -32,8 +32,8 @@ The table below lists events that Rise AI sends to Segment. These events appear
 
 | Event name          | Description                                                        |
 | ------------------- | ------------------------------------------------------------------ |
-| walkthrough-progress | User progress through AI-guided walkthroughs and onboarding flows |
-| chats               | AI chat session creation and interactions                          |
+| Walkthrough Progress | User progress through AI-guided walkthroughs and onboarding flows |
+| Chats               | AI chat session creation and interactions                          |
 
 
 ## Event properties

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

@@ -51,13 +51,13 @@ plugins:
     mark:
       url: https://cdn.filepicker.io/api/file/k1fi9InSu6eint2IHilP
   - name: Firebase
-    url: connections/sources/catalog/libraries/mobile/react-native//destination-plugins/firebase-react-native/
+    url: connections/sources/catalog/libraries/mobile/react-native/destination-plugins/firebase-react-native/
     logo:
       url: https://cdn.filepicker.io/api/file/W6teayYkRmKgb8SMqxIn
     mark:
       url: https://cdn.filepicker.io/api/file/ztKtaLBUT7GUZKius5sa
   - name: FullStory
-    url: connections/sources/catalog/libraries/mobile/react-native//destination-plugins/fullstory-react-native/
+    url: connections/sources/catalog/libraries/mobile/react-native/destination-plugins/fullstory-react-native/
     logo:
       url: https://cdn.filepicker.io/api/file/0ET4vgkqTGNMRtZcFWCA
     mark:

src/connections/sources/catalog/libraries/server/net/quickstart.md

@@ -106,6 +106,6 @@ Congratulations! You can now track any event from the browser and the backend. H
 
 ## What's Next?
 
-We just walked through the quickest way to get started with Segment using Analytics.js and the .NET library. You might also want to check out our full [Analytics.js reference](//docs/connections/sources/catalog/libraries/website/javascript/) to see what else is possible, or read about the [Tracking API methods](/docs/connections/spec/) to get a sense for the bigger picture.
+We just walked through the quickest way to get started with Segment using Analytics.js and the .NET library. You might also want to check out our full [Analytics.js reference](/docs/connections/sources/catalog/libraries/website/javascript/) to see what else is possible, or read about the [Tracking API methods](/docs/connections/spec/) to get a sense for the bigger picture.
 
 If you're running an **Ecommerce** site or app you should also check out our [Ecommerce API reference](/docs/connections/spec/ecommerce/v2/) to make sure your products and checkout experience is instrumented properly!

src/connections/sources/catalog/libraries/server/node/migration.md

@@ -60,7 +60,7 @@ If you're using the [classic version of Analytics Node.js](/docs/connections/sou
 
 #### Removals
 The updated Analytics Node.js removed these configuration options:
-- `errorHandler` (see the docs on [error handling](/docs/connections/sources/catalog/libraries/server/node//#error-handling) for more information)
+- `errorHandler` (see the docs on [error handling](/docs/connections/sources/catalog/libraries/server/node/#error-handling) for more information)
 
 The updated Analytics Node.js library removed undocumented behavior around `track` properties