From 4481e637933c5f4540f7fb779e8c41a9833069f3 Mon Sep 17 00:00:00 2001
From: markzegarelli <mark.zegarelli@segment.com>
Date: Thu, 7 Jul 2022 15:02:22 -0700
Subject: [PATCH] Updated the way that the integrations object handles All:
 false

---
 src/connections/destination-data-control.md | 7 ++++---
 src/guides/filtering-data.md                | 2 +-
 2 files changed, 5 insertions(+), 4 deletions(-)

diff --git a/src/connections/destination-data-control.md b/src/connections/destination-data-control.md
index 417103375d..c860e0be77 100644
--- a/src/connections/destination-data-control.md
+++ b/src/connections/destination-data-control.md
@@ -18,14 +18,15 @@ analytics.identify('user_123', {
   name: 'Jane Kim'
 }, {
   integrations: {
-    'All': false,
+    'All': true,
     'Intercom': true,
-    'Google Analytics': true
+    'Google Analytics': true,
+    'Mixpanel': false
   }
 });
 ```
 
-Destination flags are **case sensitive** and match [the Destination's name in the docs](/docs/connections/destinations/catalog/) (i.e. "AdLearn Open Platform", "awe.sm", "MailChimp", etc.).
+Destination flags are **case sensitive** and match [the Destination's name in the docs](/docs/connections/destinations/catalog/) (for example, "AdLearn Open Platform", "awe.sm", "MailChimp", etc.).
 
 If you're on Segment's Business plan, you can filter track calls right from the Segment UI on your Source Schema page by clicking on the field in the "Integrations" column and then adjusting the toggle for each tool. We recommend using the UI if possible since it's a much simpler way of managing your filters and can be updated with no code changes on your side.
 
diff --git a/src/guides/filtering-data.md b/src/guides/filtering-data.md
index 820b4680d4..47657136ae 100644
--- a/src/guides/filtering-data.md
+++ b/src/guides/filtering-data.md
@@ -35,7 +35,7 @@ You can use the `integrations` JSON object as part of your Segment payloads to c
 }
 ```
 
-By *default*, the `integrations` object is set to `'All':``true`. You do not need to include this flag in the object to use this behavior, but if you'll be using the integrations object frequently to control destination filtering, you might want to do this to make it explicit for later readers. You can also change this to `'All': false` to prevent destinations from receiving any data by default. You can also add destinations to the object by key, and provide a `true` or `false` value to allow or disallow data to flow to them. The `All` flag is superseded by any destination specific options.
+By *default*, the `integrations` object is set to `'All': true`. You do not need to include this flag in the object to use this behavior, but if you'll be using the integrations object frequently to control destination filtering, you might want to do this to make it explicit for later readers. Change this to `'All': false` to prevent both Segment and any downstream destinations from receiving data. You can also add destinations to the object by key, and provide a `true` or `false` value to allow or disallow data to flow to them on an individual basis.
 
 If you are using [multiple instances of a destination](/docs/connections/destinations/add-destination/#connecting-one-source-to-multiple-instances-of-a-destination), any settings you set in the integrations object are applied to all instances of the destination. You cannot specify an instance of a destination to apply Integrations object settings to.