Merge branch 'develop' into DOC-648

Author: markzegarelli

src/connections/destinations/actions.md

@@ -171,6 +171,9 @@ The available operators depend on the property's data type:
 
 You can combine criteria in a single group using **ALL** or **ANY**.  Use an ANY to “subscribe” to multiple conditions. Use ALL when you need to filter for very specific conditions. You can only create one group condition per destination action. You cannot created nested conditions.
 
+> info "Unsupported Special Characters"
+> Mappings do not support the use of double quotes " or a tilde ~ in the trigger fields.
+
 > info "Destination Filters"
 > Destination filters are compatible with Destination Actions. Consider a Destination Filter when:
 > - You need to remove properties from the data sent to the destination

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

@@ -10,9 +10,6 @@ hide-dossier: false
 
 Segment's Braze Cohorts destination syncs Engage audiences to Braze as cohorts. This is a more scalable alternative to storing audience subscription in user-level attributes in Braze. It also is more efficient as audiences are uploaded as a list, as opposed to individual events.
 
-> info ""
-> The Braze Cohorts destination is in beta and is in active development. Some functionality may change before it becomes generally available.
-
 ## Getting started
 
 Before connecting to the Braze Cohorts destination, you must have a [Braze](https://dashboard-01.braze.com/sign_in){:target="_blank"} account and an Ad Account ID.

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

@@ -15,9 +15,6 @@ versions:
 
 When you have Segment installed, you can use your existing tracking implementation to fulfill your data collection needs with Google Analytics 4. When you use the Google Analytics 4 Web destination, Segment loads the [gtag.js library](https://support.google.com/analytics/answer/9310895?hl=en#zippy=%2Cin-this-article){:target="_blank"}  for you. 
 
-> info ""
-> The Google Analytics 4 Web destination is in beta and is in active development. Some functionality may change before it becomes generally available.
-
 ## Getting started
 
 Before you connect Segment to Google Analytics 4, configure a Google Analytics 4 property in your Analytics account. For more information, see Google's article [Set up Analytics for a website and/or app](https://support.google.com/analytics/answer/9304153){:target='_blank'}.
@@ -61,7 +58,6 @@ Google Analytics 4 collects events triggered by basic interactions with your sit
 
 Google may take [24-48 hours](https://support.google.com/analytics/answer/9333790){:target="_blank"} to process data sent to Google Analytics. As a result, the Google Analytics user interface may not reflect the most current data. The Google Analytics [Realtime report](https://support.google.com/analytics/answer/9271392){:target="_blank"} displays activity on your site as it happens.
 
-
 ### Data is not sent to Google
 
 Ensure that at least one mapping has been configured and enabled in the destination mappings for an event you want to send to Google Analytics. If no mappings are enabled, the destination does not send events.

src/connections/destinations/catalog/actions-segment-profiles/index.md

@@ -9,9 +9,6 @@ The Segment Profiles destination allows you to send your warehouse data back to
 > success "Source compatibility"
 > This destination supports connections from Reverse ETL warehouse sources, and is not compatible with other source types.
 
-> info ""
-> The Segment Profiles destination is in beta and is in active development. Some functionality may change before it becomes generally available.
-
 ## Getting started
 
 ### Create a Profile space

src/connections/destinations/destination-filters.md

@@ -29,6 +29,7 @@ Keep the following limitations in mind when you use destination filters:
 - *(For device-mode)* Destination filters don't filter on native events that the destination SDK collects. Instead, you can use the load option to conditionally load relevant bundled JavaScript on the page. See the docs for [load options](/docs/connections/sources/catalog/libraries/website/javascript/#load-options).
 - *(For device-mode)* Destination filters don't filter some fields that are collected by the destination SDK outside of Segment such as `page.url` and `page.referrer`.
 - *(For web device-mode)* Destination filters for web device-mode only supports the Analytics.js 2.0 source. You need to enable device mode destination filters for your Analytics.js source. To do this, go to your Javascript source and navigate to **Settings > Analytics.js** and turn the toggle on for **Destination Filters**.
+- *(For web device-mode)* Destination filters for device-mode only supports the Analytics.js 2.0 source. Destination filters for mobile is currently not supported.
 
 [Contact Segment](https://segment.com/help/contact/){:target="_blank"} if these limitations impact your use case.
 

src/guides/what-is-replay.md

@@ -32,6 +32,8 @@ Replays can process an unlimited amount of data, however they are rate limited t
 
 Replays do not affect your [MTU count](/docs/guides/usage-and-billing/mtus-and-throughput/), unless you are using a [Repeater destination](/docs/connections/destinations/catalog/repeater/). Notify your team before initiating a Replay if you're using a Repeater destination.
 
+Once a replay starts, you will not see replayed events in the Event Delivery tab.
+
 ### Replay-eligible destinations
 
 Replays are available for any destinations which support cloud-mode data (meaning data routed through Segment) and which also process timestamps. Destinations that are only available in device-mode (meaning where data is sent directly from the users' devices to the destination tool) cannot receive Replays.