Merge pull request segmentio#349 from segmentio/repo-sync

bot-docsteam · web-flow · commit 2101adacf51a · 2022-05-03T09:44:00.000-07:00
repo sync
diff --git a/src/_data/sidenav/engage.yml b/src/_data/sidenav/engage.yml
@@ -89,27 +89,27 @@ sections:
     title: Message Events
   # - path: '/engage/analytics/custom-events'
   #   title: Custom Events
-- section_title: Settings
-  section:
-  - path: '/engage/settings/messaging-settings'
-    title: Messaging Settings
-  - path: '/engage/settings/identity-resolution'
-    title: Identity Resolution
-  - path: '/engage/settings/sources'
-    title: Sources
-  - path: '/engage/settings/destinations'
-    title: Destinations
-  - path: '/engage/settings/debugger'
-    title: Debugger
-  - path: '/engage/settings/connection-policy'
-    title: Connection Policy
-  - path: '/engage/settings/warehouse-sources'
-    title: Warehouse Sources
-  - path: '/engage/settings/api-access'
-    title: API Access
-  - path: '/engage/settings/rename-space'
-    title: Rename Space
-  - path: '/engage/settings/labels'
-    title: Labels
+# - section_title: Settings
+#   section:
+#   - path: '/engage/settings/messaging-settings'
+#     title: Messaging Settings
+#   - path: '/engage/settings/identity-resolution'
+#     title: Identity Resolution
+#   - path: '/engage/settings/sources'
+#     title: Sources
+#   - path: '/engage/settings/destinations'
+#     title: Destinations
+#   - path: '/engage/settings/debugger'
+#     title: Debugger
+#   - path: '/engage/settings/connection-policy'
+#     title: Connection Policy
+#   - path: '/engage/settings/warehouse-sources'
+#     title: Warehouse Sources
+#   - path: '/engage/settings/api-access'
+#     title: API Access
+#   - path: '/engage/settings/rename-space'
+#     title: Rename Space
+#   - path: '/engage/settings/labels'
+#     title: Labels
 path: '/engage/contact'
 title: Support
diff --git a/src/connections/destinations/catalog/ambassador/index.md b/src/connections/destinations/catalog/ambassador/index.md
@@ -3,15 +3,15 @@ rewrite: true
 title: Ambassador Destination
 id: 573a3dfb80412f644ff13679
 ---
-[Ambassador](https://www.getambassador.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) empowers companies to easily create, track & manage custom incentives that drive referrals and evangelize their users. The Ambassador Destination is open-source. You can browse the code [on GitHub](https://github.com/segment-integrations/analytics.js-integration-ambassador).
+[Ambassador](https://www.getambassador.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) empowers companies to easily create, track & manage custom incentives that drive referrals and evangelize their users. 
 
 ## Getting Started
 
 {% include content/connection-modes.md %}
 
-  1. From the Segment web app, click **Catalog**.
-  2. Search for "Ambassador" in the Catalog, select it, and choose which of your sources to connect the destination to.
-  3. In the destination settings, enter your "Client ID" from your Ambassador dashboard, and populate any "Campaigns" to be mapped as per the below [Mapping campaigns to URLs](#mapping-campaigns-to-urls) section.
+1. From the Segment web app, click **Catalog**.
+2. Search for "Ambassador" in the Catalog, select it, and choose which of your sources to connect the destination to.
+3. In the destination settings, enter your "Client ID" from your Ambassador dashboard, and populate any "Campaigns" to be mapped as per the below [Mapping campaigns to URLs](#mapping-campaigns-to-urls) section.
 
 
 Your changes appear in the Segment CDN in about 45 minutes, and then Analytics.js starts asynchronously loading the Ambassador snippet on your page and sending data.
diff --git a/src/connections/sources/catalog/cloud-apps/facebook-ads/index.md b/src/connections/sources/catalog/cloud-apps/facebook-ads/index.md
@@ -49,7 +49,7 @@ Collections are the groupings of resources we pull from your source. In your war
 
 | Collection  | Type   | Description                                                                                                                                                                                            |
 | ----------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| ad_accounts | object | An [ad account](https://developers.facebook.com/docs/marketing-api/reference/ad-account) is an account used to manage ads on Facebook                                                                  |
+| ad_accounts | object | An ad account is an account used to manage ads on Facebook                                                                  |
 | ad_sets     | object | An [ad set](https://developers.facebook.com/docs/marketing-api/reference/ad-campaign) is a group of ads that share the same daily or lifetime budget, schedule, bid type, bid info, and targeting data |
 | ads         | object | An [ad](https://developers.facebook.com/docs/marketing-api/reference/adgroup) object contains the data necessary to visually display an ad and associate it with a corresponding ad set.               |
 | campaigns   | object | A [campaign](https://developers.facebook.com/docs/marketing-api/reference/v13.0) is a grouping of ad sets which are organized by the same business objective.                              |
diff --git a/src/connections/sources/catalog/cloud-apps/nudgespot/index.md b/src/connections/sources/catalog/cloud-apps/nudgespot/index.md
@@ -4,7 +4,7 @@ id: 5GkpcyvNey
 ---
 {% include content/source-region-unsupported.md %}
 
-Nudgespot is the easiest way to trigger emails, SMS, push notifications or in-app messages to your customers, at the right time.  [Visit Website](http://www.nudgespot.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners)
+Nudgespot is the easiest way to trigger emails, SMS, push notifications or in-app messages to your customers, at the right time.  [Visit Website](https://zetaglobal.com/){:target="_blank"}.
 
 Take your company's email analysis to the next level by **adding Nudgespot as a Source to Segment.** Segment automatically  collects email events like `Email Delivered` and `Email Opened`, forward them to your destinations, and load them into your data warehouse. 
 
diff --git a/src/connections/sources/catalog/libraries/website/javascript/index.md b/src/connections/sources/catalog/libraries/website/javascript/index.md
@@ -483,19 +483,19 @@ 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.
 
-An example:
+For example:
 
 ```js
 analytics.load('writekey', { integrations: { All: false, 'Google Analytics': true, 'Segment.io': true } })
 ```
 
-> 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).
-
 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
@@ -504,6 +504,17 @@ onConsentDialogClosed(function(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:
+
+```js
+analytics.load('writekey', { obfuscate: true })
+```
+
+The `obfuscate` value is `false` by default.
+
 
 ## Retries
 
