Merge branch 'master' into add_Braze_warning_image

Author: markzegarelli

src/_data/catalog/destination_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination categories last updated 2021-08-06 
+# destination categories last updated 2021-08-16 
 items:
 - display_name: A/B Testing
   slug: a-b-testing

src/_data/catalog/destinations.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2021-08-06 
+# destination data last updated 2021-08-16 
 items:
 - display_name: ActiveCampaign
   name: ActiveCampaign
@@ -2305,8 +2305,8 @@ items:
     type: boolean
     defaultValue: true
     description: >-
-      Enabling this will send referrer information as a user property to
-      Amplitude when you call Segment's `page` method.
+      Client Side Only - Enabling this will send referrer information as a user
+      property to Amplitude when you call Segment's `page` method. 
     required: false
     label: Track Referrer to Amplitude
   - name: trackRevenuePerProduct
@@ -11395,8 +11395,10 @@ items:
     defaultValue: ''
     description: >-
       Enter your UBX account's base URL endpoint here. This can be found in the
-      email you received from UBX after setting up your UBX account. It shoul
-      have the format `https://<subdomain>.ubx.ibmmarketing.cloud/<path>`.
+      email you received from UBX after setting up your UBX account. It should
+      have either the format
+      `https://<subdomain>.ubx.ibmmarketingcloud.com/<path>/` or
+      `https://<subdomain>.goacoustic.com/<path>/`.
     required: true
     label: API URL
   - name: authToken
@@ -16162,8 +16164,7 @@ items:
   - Marketing Automation
   - Personalization
   logo:
-    url: >-
-      https://public-segment-devcenter-production.s3.amazonaws.com/58c0f9b4-3ec6-43c3-9158-0942ff36262b.svg
+    url: 'https://cdn.filepicker.io/api/file/R1AmIwNrRNGc139Q5SlY'
   mark:
     url: >-
       https://public-segment-devcenter-production.s3.amazonaws.com/d180bde1-ed0e-4155-95c4-e8013e6bda4e.svg
@@ -21525,8 +21526,7 @@ items:
   - Analytics
   - Enrichment
   logo:
-    url: >-
-      https://public-segment-devcenter-production.s3.amazonaws.com/ebca8275-d3b2-4d71-934d-2ad6ae777ccd.svg
+    url: 'https://cdn.filepicker.io/api/file/BUciQq3kSzqCn8EKMtBN'
   mark:
     url: >-
       https://public-segment-devcenter-production.s3.amazonaws.com/4dd0d6c4-3d47-4945-b932-3c9af3530349.svg

src/_data/catalog/source_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# source cateogries last updated 2021-08-06 
+# source cateogries last updated 2021-08-16 
 items:
   - display_name: A/B Testing
     slug: a-b-testing

src/_data/catalog/sources.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# sources last updated 2021-08-06 
+# sources last updated 2021-08-16 
 items:
   - display_name: .NET
     slug: net

src/_data/catalog/warehouse_papi.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# warehouse data last updated 2021-08-06 
+# warehouse data last updated 2021-08-16 
 items:
 - display_name: Azure SQL Data Warehouse
   slug: azuresqldw

src/connections/destinations/catalog/adroll/index.md

@@ -60,7 +60,7 @@ Then, inside AdRoll you can create a "segment" of all users doing any of those e
 
 ### Conversion Value
 
-When you include an event property labeled `revenue` it will be tracked to AdRoll as `adroll_conversion_value`.
+When you include an event property labeled `price` it will be tracked to AdRoll as `adroll_conversion_value`.
 
 ### Currency
 

src/connections/destinations/catalog/braze/index.md

@@ -184,7 +184,7 @@ analytics.track('Purchased Item', {
     name: 'bag'
 })
 ```
-When you `track` an event, Segment sends that event to Braze as a custom event. Braze does not support arrays or nested objects for custom track event properties.
+When you `track` an event, Segment sends that event to Braze as a custom event.
 
 > note ""
 > Braze requires that you include a `userId` or `braze_id` for all calls made in cloud-mode. Segment sends a `braze_id` if `userId` is missing. When you use a device-mode connection, Braze automatically tracks anonymous activity using the `braze_id` if a `userId` is missing.

src/connections/schema-defaults-eol.md

@@ -5,43 +5,25 @@ hidden: true
 
 ## Schema Defaults Removal FAQs
 
-Schema Defaults allows you to block new events and traits by default. This feature was launched to Private Beta in 2017 as an exploration feature before the introduction of Protocols. It will be removed on August 11, 2021.
-
-#### How do I know if I’m using Schema Defaults?
-Navigate to **Connections** and choose your source. In the **Settings** tab under **Schema Configuration**, if you see the **Schema Defaults** section and have any events or traits that are marked **Block** or **Omit**, you have Schema Defaults enabled.
-
-![Schema Defaults](images/schema-defaults-eol-1.png)
+Schema Defaults allows you to block new events and traits by default. This feature was launched to Private Beta in 2017 as an exploration feature before the introduction of Protocols.
 
 #### What happens after Schema Defaults is removed?
 Any events and traits that were blocked by Schema Defaults will continue to be blocked. Any new events and traits will automatically be allowed.
 
-Before they are removed, you can change your Source Schema settings to allow or block individual events, properties, and traits by following these steps:
-
-1. Go to the **Schema** tab of your source.
-2. Use the toggle to allow or block the different events, properties, and traits.
-
-![toggling schema defaults](images/schema-defaults-eol-2.png)
+If you still want to block new events and traits by default, you can connect a [Protocols Tracking Plan](/docs/protocols/) to your source.
 
 #### What happens if a source with Schema Defaults enabled has a Tracking Plan connected to it?
-Tracking Plans _replace_ Schema Defaults, so these sources will continue to behave the same.
+[Tracking Plans](/docs/protocols/tracking-plan/) replace Schema Defaults, so these sources will continue to behave the same.
 
-#### How should I prepare for the removal of Schema Defaults?
-If you still want to block new events and traits by default, you can connect a [Protocols Tracking Plan](/docs/protocols/) to your source.
 
 ## Event Requirements Removal FAQs
 
-Event Requirements allow you to define rules for an event property and block violating events. This feature was launched to Private Beta in 2017 as an exploratory feature before the introduction of Protocols. It will be removed on August 11, 2021.
-
-#### How do I know if I’m using Event Requirements?
-Navigate to **Connections** and choose your source. Go to the **Schema** tab and click on an event. If you’re able to click on an event and view the properties and rules for it, you’re using Event Requirements.
-
-![Event Requirements](images/schema-defaults-eol-3.png)
+Event Requirements allows you to define rules for an event property and block violating events. This feature was launched to Private Beta in 2017 as an exploratory feature before the introduction of Protocols.
 
 #### What happens after Event Requirements is removed?
 Events that violate the rules set up in Event Requirements will no longer be blocked. The Event Requirements UI will be removed from the Segment web app, and you won’t be able to interact with the feature settings.
 
+If you still want to block the events that you set up in Event Requirements, you can connect a [Protocols Tracking Plan](/docs/protocols/tracking-plan/) to your source.
+
 #### What happens if a source with Event Requirements enabled has a Tracking Plan connected to it?
 [Tracking Plans](/docs/protocols/tracking-plan/) replace any Event Requirements, so these sources will continue to behave the same.
-
-#### How should I prepare for the removal of Event Requirements?
-If you still want to block the events that you set up in Event Requirements, you can connect a [Protocols Tracking Plan](/docs/protocols/tracking-plan/) to your source.