From be1b35c7f3bf9d7c183bba83108366d77a07294c Mon Sep 17 00:00:00 2001 From: Irina Gorelik Date: Tue, 21 Jan 2020 14:43:15 -0700 Subject: [PATCH 1/2] adding note under Destination Filters that it only supports cloud-mode destinations --- src/connections/destinations/destination-filters.md | 2 +- src/guides/filtering-data.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/connections/destinations/destination-filters.md b/src/connections/destinations/destination-filters.md index c3736eedec..5f9c08c3a0 100644 --- a/src/connections/destinations/destination-filters.md +++ b/src/connections/destinations/destination-filters.md @@ -17,7 +17,7 @@ With Destination Filters, you can: - Prevent test or internally-generated events from reaching your production tools. - **Note**: Destination Filters are currently available to Business Tier customers only + **Note**: Destination Filters are currently available to Business Tier customers only. ### Destination Filtering Limitations diff --git a/src/guides/filtering-data.md b/src/guides/filtering-data.md index e51883a7e1..548ea93f31 100644 --- a/src/guides/filtering-data.md +++ b/src/guides/filtering-data.md @@ -44,7 +44,7 @@ Your data is sent to your warehouse (if you have one) and into the Segment backe [Destination Filters](https://segment.com/docs/connections/destinations/destination-filters/) allow you to control the data flowing into each specific destination, by examining event payloads, and conditionally preventing data from being sent to destinations. You can filter out entire events, or just specific fields in the properties, in the traits, or in the context of your events. Destination filters are not available for, and do not prevent data from reaching your warehouse(s) or S3 destinations. -Destination Filters are available in workspaces that are on a Business Tier plan only. + **Note**: Destination Filters are available in workspaces that are on a Business Tier plan only. Destination Filters can only be applied to Cloud-mode ("server-side") streaming destinations. Device-mode destinations are not supported. ![](images/destination-filter-create.png) From de3d086d2fb6d4905dcd5244514cead172cea48e Mon Sep 17 00:00:00 2001 From: Irina Gorelik Date: Tue, 21 Jan 2020 14:57:14 -0700 Subject: [PATCH 2/2] update note styling --- src/connections/destinations/destination-filters.md | 3 ++- src/guides/filtering-data.md | 3 ++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/src/connections/destinations/destination-filters.md b/src/connections/destinations/destination-filters.md index 5f9c08c3a0..47812f7015 100644 --- a/src/connections/destinations/destination-filters.md +++ b/src/connections/destinations/destination-filters.md @@ -17,7 +17,8 @@ With Destination Filters, you can: - Prevent test or internally-generated events from reaching your production tools. - **Note**: Destination Filters are currently available to Business Tier customers only. + > note "" + > **Note**: Destination Filters are currently available to Business Tier customers only. ### Destination Filtering Limitations diff --git a/src/guides/filtering-data.md b/src/guides/filtering-data.md index 548ea93f31..7041da651b 100644 --- a/src/guides/filtering-data.md +++ b/src/guides/filtering-data.md @@ -44,7 +44,8 @@ Your data is sent to your warehouse (if you have one) and into the Segment backe [Destination Filters](https://segment.com/docs/connections/destinations/destination-filters/) allow you to control the data flowing into each specific destination, by examining event payloads, and conditionally preventing data from being sent to destinations. You can filter out entire events, or just specific fields in the properties, in the traits, or in the context of your events. Destination filters are not available for, and do not prevent data from reaching your warehouse(s) or S3 destinations. - **Note**: Destination Filters are available in workspaces that are on a Business Tier plan only. Destination Filters can only be applied to Cloud-mode ("server-side") streaming destinations. Device-mode destinations are not supported. +> note "" +> **Note**: Destination Filters are available in workspaces that are on a Business Tier plan only. Destination Filters can only be applied to Cloud-mode ("server-side") streaming destinations. Device-mode destinations are not supported. ![](images/destination-filter-create.png)