Merge pull request #2834 from segmentio/revert-2805-documenting-obfuscation-feature

Revert "Bundle Obfuscation [DOC-508]"

Author: stayseesong

src/connections/sources/catalog/libraries/website/javascript/index.md

@@ -483,6 +483,9 @@ Destination flags are **case sensitive** and match [the destination's name in th
 
 ### Load Options
 
+> info ""
+> **Note:** To use this feature, you must be on snippet version 4.1.0 or later. You can get the latest version of the snippet [here](/docs/connections/sources/catalog/libraries/website/javascript/quickstart/#step-2-copy-the-segment-snippet).
+
 You can modify the `.load` method in Analytics.js (the second line of the snippet) to take a second argument. If you pass an object with an `integrations` dictionary (matching the format [above](#selecting-destinations-with-the-integrations-object)), then Segment only loads the integrations in that dictionary that are marked as enabled with the boolean value `true`.
 
 You can only call `.load` on page load, or reload (refresh). If you modify the `.load` method between page loads, it does not have any effect until the page is reloaded.
@@ -493,7 +496,15 @@ For example:
 analytics.load('writekey', { integrations: { All: false, 'Google Analytics': true, 'Segment.io': true } })
 ```
 
-#### Bundle Obfuscation 
+This way, you can conditionally load integrations based on what customers opt into on your site. The example below shows how you might load only the tools that the user agreed to use.
+
+```js
+onConsentDialogClosed(function(consentedTools){
+  analytics.load('writekey', { integrations: consentedTools })
+})
+```
+
+#### Bundle Obfuscation
 You can also add an `obfuscate` property to the object in the second parameter, which obscures the URL from which your integrations and destination actions are loaded. This helps prevent words that are flagged by ad blockers to not be detected in your URL, enabling the integration to properly load.
 
 For example: