Merge pull request #3362 from segmentio/destinations-sources-overview-fixes

fixes for sources and destinations overview

Author: stayseesong

src/_includes/content/connection-modes-intro.md

@@ -1,7 +1,14 @@
-Our Web source (Analytics.js), and our native client-side libraries (iOs, Android, React-native) allow you to choose how you send data to Segment from your website or app. Two ways are available:
+Segment's web source (Analytics.js), and native client-side libraries (iOS, Android, React-native) allow you to choose how you send data to Segment from your website or app. There are two ways to send data:
 
-- **Cloud-mode**: in this mode, the sources send data directly to the Segment servers, which then translate it for each connected downstream destination, and send it on. Translation is done on the Segment servers, keeping your page size, method count, and load time small.
+- **Cloud-mode**: The sources send data directly to the Segment servers, which then translate it for each connected downstream destination, and send it on. Translation is done on the Segment servers, keeping your page size, method count, and load time small.
 
-- **Device-mode**: in this mode, you include additional code on your website or mobile app which allows Segment to use the data you collect on the device to make calls directly to the destination tool's API, without sending it to the Segment servers _first_. (You still send your data to the Segment servers, but this occurs asynchronously.) This is also called "wrapping" or "bundling", and it might be required when the source has to be loaded on the page to work, or loaded directly on the device to function correctly. When you use Analytics.js, you can change the device-mode destinations that a specific source sends to from within the Segment web app, without touching any code.
+- **Device-mode**: You include additional code on your website or mobile app which allows Segment to use the data you collect on the device to make calls directly to the destination tool's API, without sending it to the Segment servers _first_. (You still send your data to the Segment servers, but this occurs asynchronously.) This is also called *wrapping* or *bundling*, and it might be required when the source has to be loaded on the page to work, or loaded directly on the device to function correctly. When you use Analytics.js, you can change the device-mode destinations that a specific source sends from within the Segment web app, without touching any code.
 
-> **Note:** If you use Server source libraries, they only send data directly to Segment in Cloud-mode. (Server library implementations operate in the server backend, and can't load additional destination SDKs.)
+
+<div class="premonition info">
+  <div class="fa fa-info-circle"></div>
+  <div class="content">
+    <p class="header"></p>
+    <p>If you use Server source libraries, they only send data directly to Segment in Cloud-mode. Server library implementations operate in the server backend, and can't load additional destination SDKs.</p>
+  </div>
+</div>

src/connections/destinations/destination-filters.md

@@ -3,35 +3,32 @@ title: Destination Filters
 rewrite: true
 ---
 
-Use Destination Filters to prevent certain data from flowing into a destination.
-
-With Destination Filters, you can conditionally filter out event properties, traits, and fields, or even filter out the event itself.
-
-Common use cases for Destination Filters include the following:
+Use Destination Filters to prevent certain data from flowing into a destination. With Destination Filters, you can conditionally filter out event properties, traits, and fields, or even filter out the event itself.
 
+Common use cases for Destination Filters include:
 - Managing PII (personally identifiable information) by blocking fields from reaching certain destinations
 - Controlling event volume by sampling or dropping unnecessary events for specific destinations
 - Increasing data relevance in your destinations by removing unused or unwanted data
 - Preventing test or internally-generated events from reaching your production tools
 
-> note ""
-> Destination Filters are available to Business Tier customers only.
+> info ""
+> Destination Filters are only available to Business Tier customers.
 
-### Destination filtering limitations
+### Limitations
 
 Keep the following limitations in mind when you use Destination Filters:
 
 - Segment applies Destination Filters one at a time in the order that they appear in your workspace.
-- Destination Filters can only be applied to cloud-mode (server-side) streaming destinations. Device-mode destinations aren't supported.
+- Destination Filters can only be applied to cloud-mode (server-side) streaming destinations.
+- Device-mode destinations aren't supported.
 - You can't apply Destination Filters to Warehouses or S3 destinations.
 - Each filter can only apply to one source-destination pair.
 
 [Contact Segment](https://segment.com/help/contact/){:target="_blank"} if these limitations impact your use case.
 
 ## Create a Destination Filter
 
-To create a Destination Filter, follow these steps:
-
+To create a Destination Filter:
 1. Go to **Connections > Destinations** and select your destination.
 2. Click on the **Filters** tab of your destination.
 3. Click **+ New Filter**.
@@ -43,22 +40,28 @@ To create a Destination Filter, follow these steps:
 
 ## Destination Filters API
 
-The Destination Filters API provides more power than the Segment dashboard's Destination Filters settings. With the API, you can create complex filters that are conditionally applied using Segment's [Filter Query Language (FQL)](/docs/config-api/fql).
+The Destination Filters API provides more power than Segment's dashboard Destination Filters settings. With the API, you can create complex filters that are conditionally applied using Segment's [Filter Query Language (FQL)](docs/api/config-api/fql/).
 
 The Destination Filters API offers four different filter types:
 
 | Filter             | Details                                                      |
 | ------------------ | ------------------------------------------------------------ |
-| `drop_event`       | Don't send matched events to the destination.                |
-| `sample_event`     | Send only a percentage of events through to the destination. |
-| `whitelist_fields` | Only send whitelisted properties to the destination.         |
-| `blocklist_fields` | Don't send blocklisted properties to the destination.        |
+| `drop_event`       | Doesn't send matched events to the destination.                |
+| `sample_event`     | Sends only a percentage of events through to the destination. |
+| `whitelist_fields` | Only sends whitelisted properties to the destination.         |
+| `blocklist_fields` | Doesn't send blocklisted properties to the destination.        |
 
-To learn more, read Segment's [Destination Filters API docs](https://reference.segmentapis.com/#6c12fbe8-9f84-4a6c-848e-76a2325cb3c5){:target="_blank"}.
+To learn more, read Segment's [Destination Filters API docs](https://docs.segmentapis.com/tag/Destination-Filters){:target="_blank"}.
 
 ## Examples
 
-The following examples illustrate common Destinations Filters use cases.
+The following examples illustrate common Destinations Filters use cases:
+* [PII management](#pii-management)
+* [Control event volume](#control-event-volume)
+* [Cleaner data](#cleaner-data)
+* [Remove internal and test events from production tools](#remove-internal-and-test-events-from-production-tools)
+* [Sample a percentage of events](#sample-a-percentage-of-events)
+* [Drop events](#drop-events)  
 
 ### PII management
 
@@ -83,39 +86,39 @@ This example shows a rule that only sends track calls to Google Analytics.
 
 ### Remove internal and test events from production tools
 
-This rule targets email addresses with internal domains to stop test events from reaching Destinations.
+In the example below, the rule targets email addresses with internal domains to stop test events from reaching Destinations.
 
 ![Example of a filter that removes internal and test events from production tools](images/destination-filters/internal_example.png)
 
-This rule prevents an event from sending if `Order Completed` and `properties.email` contain an internal `@segment.com` email address.
+In the example below, the rule prevents an event from sending if `Order Completed` and `properties.email` contain an internal `@segment.com` email address.
 
 ![Internal domain filter example](images/destination-filters/internal_example2.png)
 
 ### Sample a percentage of events
 
-Using the [Destination Filters API](https://reference.segmentapis.com/#6c12fbe8-9f84-4a6c-848e-76a2325cb3c5){:target="_blank"}, you can create a rule to randomly sample video heartbeat events.
+Using the [Destination Filters API](https://docs.segmentapis.com/tag/Destination-Filters){:target="_blank"}, you can create a rule to randomly sample video heartbeat events.
 
 ### Drop events
 
 [Watch this Destination Filters walkthrough](https://www.youtube.com/watch?v=47dhAF1Hoco){:target="_blank"} to learn how to use event names to filter events sent to destinations.
 
 ## Important notes
 
-**Conflicting settings**
+#### Conflicting settings
 
 Some destinations offer settings that also allow you to filter data. For example, the Facebook App Events destination allows you to map `Screen` events to `Track` events. Because Destination Filters are evaluated and applied _before_ the Destination settings are applied, they can conflict with your settings.
 
-In the example in the video above, if you have a Destination Filter that filters Track events _and_ you have the **Use Screen Events as Track Events** setting enabled, `Track` events will be dropped, but `Screen` events still process. The destination settings will transform it into a `Track` event - *after* the filters.
+For example, if you have a Destination Filter that filters Track events _and_ you have the **Use Screen Events as Track Events** setting enabled, `Track` events drop, but `Screen` events still process. The destination settings transform it into a `Track` event - *after* the filters.
 
-**Error handling**
+#### Error handling
 
-Segment makes effort to ensure that Destination Filters handle unexpected situations. For example, if you use the `contains()` FQL function on `null` field, Segment returns `false` instead of returning an error. If Segment can't infer your intent, Segment logs an internal error and drops the event. Segment defaults to this behavior to prevent sensitive information, like a PII filter, from getting through.
+Segment makes effort to ensure that Destination Filters can handle unexpected situations. For example, if you use the `contains()` FQL function on the `null` field, Segment returns `false` instead of returning an error. If Segment can't infer your intent, Segment logs an internal error and drops the event. Segment defaults to this behavior to prevent sensitive information, like a PII filter, from getting through.
 
 Errors aren't exposed in your Destination's Event Deliverability tab. For help diagnosing missing destination filter events, [contact Segment](https://segment.com/help/contact/){:target="_blank"}.
 
-## FAQ
+## FAQs
 
-**How do Destination Filters work with array properties?**
+#### How do Destination Filters work with array properties?
 
 Destination Filters can filter properties out of objects nested in an array. For example, you can filter out the `price` property of every object in an array at `properties.products`. You can also filter out an entire array from the payload. However, you can't drop nested objects in an array or filter properties out of a single object in an array.
 
@@ -125,38 +128,36 @@ For example, the `properties.products.newElement` filter blocks all `newElement`
 
 ![Filter array properties](images/destination-filters/filter-array-properties.png)
 
-To block the Identify event trait `products.newElement`, select the option under the **User Traits** list instead. To block a context object field `products.newElement`, select it from the **Context Fields** list.
+To block the Identify event trait `products.newElement`, select the option under the **User Traits** list instead. To block the context object field `products.newElement`, select it from the **Context Fields** list.
 
-**How many filters can I create?**
+#### How many filters can I create?
 
 Segment supports 10 filters per destination. If you need help consolidating filters or would like to discuss your use case, [contact Segment](https://segment.com/help/contact/){:target="_blank"}.
 
-**Can I set multiple `Only Send` Destination Filters?**
+#### Can I set multiple `Only Send` destination filters?
 
 Segment evaluates multiple `Only Send` filters against each other and resolves Destination Filters in order. If multiple `Only Send` filters conflict with each other, Segment won't send information downstream.
 
-**How many properties can I view in the filter dropdown?**
+#### How many properties can I view in the filter dropdown?
 
 Segment displays the most recent 15,000 properties. To find a property not in the filter dropdown, enter the property manually.
 
-**How can I filter out warehouse events?**
+#### How can I filter out warehouse events?
 
 To filter out events from warehouses, use Selective Sync.
 
-**I don't see a `name` property at the top level of my events to filter on "event name".**
-
-Generally, only Track calls have "name" properties, which correspond to the "Event" field in an event.
+#### I don't see a *name* property at the top level of my events to filter on *event* name".
 
-**How can I find out when new Destination Filters have been added or removed?**
+Generally, only Track calls have *name* properties, which correspond to the *event* field in an event.
 
-The activity feed shows the action, date, and user who performed the action when a Destination Filter is created, modified, enabled, disabled, or deleted. You can also subscribe to notifications for any of these changes in the Activity Feed settings page.
+#### How can I find out when new Destination Filters have been added or removed?
 
-The Activity Feed shows the user, date, and action performed when a Destination Filter is created, modified, enabled, disabled, or deleted.
+The Activity Feed shows the action, date, and user who performed the action when a Destination Filter is created, modified, enabled, disabled, or deleted. You can also subscribe to notifications for any of these changes in the **Activity Feed** settings page.
 
-**Why am I getting a permissions denied error when I try to save a filter?**
+#### Why am I getting a permissions denied error when I try to save a filter?
 
-You must have write access to save and edit filters; read permission allows viewing and testing access only.
+You must have write access to save and edit filters. Read permission access only allows viewing and testing access.
 
-**How can I test my filter?**
+#### How can I test my filter?
 
 Use the Destination Filter tester during setup to verify that you're filtering out the right events. Filtered events show up on the schema page but aren't counted in event deliverability graphs.