Release 21.49.1

Release 21.49.1

Author: forstisabella

src/_data/landing.yml

@@ -4,7 +4,7 @@ sections:
   section:
   - name: Getting started with Segment
     icon: getting-started.svg
-    description: "Learn about Segment, work through a basic implementation, plan a full implementation and learn about features and extensions. "
+    description: "Learn about Segment, plan and work through a basic implementation, and explore features and extensions."
     path: /getting-started/
 - section_title: How can Segment help you?
   section_col: 6
@@ -19,22 +19,22 @@ sections:
     path: /protocols/
   - name: Personalize interactions
     icon: personas.svg
-    description: "Improve customer interactions by building audiences to power personalized experiences."
+    description: "Improve customer interactions by building audiences that power personalized experiences."
     path: /personas/
   - name: Respect users' privacy
     icon: privacy.svg
-    description: "Use Segment's tools for data discovery and policy enforcement to keep customer data private."
+    description: "Keep customer data private with Segment's data discovery and policy enforcement tools."
     path: /privacy/
 
 - section_title: Get Data into Segment
-  section_description: "The Segment Spec provides guidance on meaningful data to capture, and the best format for it, across all of our libraries and APIs. When you use these formats it’s simple to send data to downstream tools."
+  section_description: "The Segment Spec helps you identify, capture, and format meaningful data for use with Segment libraries and APIs as well as downstream tools."
   section_col: 4
   section:
   - name: Segment calls
-    description: "Use Track, Page, and Identify, and learn about the other calls Segment tracking is built on."
+    description: "Use Track, Page, Identify, and other Segment tracking calls."
     path: /connections/spec/
   - name: Common traits
-    description: "Save time by letting the Segment calls collect information automatically."
+    description: "Save time by letting Segment calls collect information for you."
     path: /connections/spec/common/
   - name: Use case specs
     description: "Use our business-case specs to ensure that your tools get the most from your data."
@@ -45,17 +45,17 @@ sections:
   section:
   - name: Segment for Developers
     icon: git-repo.svg
-    description: "An overview of the basics of your Segment implementation."
+    description: "The basics of your Segment implementation."
     path: /guides/intro-impl/
   - name: How-To Guides
     icon: book.svg
-    description: "Over a dozen how-to guides to help you accomplish common tasks."
+    description: "Over a dozen how-to guides that help you accomplish common tasks."
     path: /guides/how-to-guides/
 
 - section_title: Connect your app to Segment
   section_col: 4
   section:
-  - name: Javascript
+  - name: JavaScript
     path: /connections/sources/catalog/libraries/website/javascript/
   - name: HTTP Tracking API
     path: /connections/sources/catalog/libraries/server/http-api/

src/_includes/components/feedback.html

@@ -1,11 +1,11 @@
 <div class="flex flex--wrap waffle waffle--large waffle--xxlarge@medium">
-  <div class="flex__column flex__column--12 flex__column--6@medium flex">
+  <div class="flex__column flex__column--12 flex__column--4@medium flex">
     <div class="feedback-box flex flex--stack flex--justify waffle waffle--large@medium">
       <div class="flex__column flex__column--shrink">
         <div class="feedback-box__content">
           <h3>Need support?</h3>
 
-          <p>Questions? Problems? Need more info? Contact us, and we can help!</p>
+          <p>Questions? Problems? Need more info? Contact Segment Support for assistance!</p>
         </div>
       </div>
 
@@ -14,16 +14,24 @@ <h3>Need support?</h3>
       </div>
     </div>
   </div>
-
-  <div class="flex__column flex__column--12 flex__column--6@medium flex">
+  <div class="flex__column flex__column--12 flex__column--4@medium flex">
+    <div class="flex__column flex__column--shrink">
+      <div class="feedback-box__content">
+        <h3>Help improve these docs!</h3>
+        {%include sidebar/edit-tools.html %}
+      </div>
+    </div>
+  </div>
+  <div class="flex__column flex__column--12 flex__column--4@medium flex">
     <div class="feedback-box flex flex--stack flex--justify waffle waffle--none waffle--large@medium">
       <div class="flex__column flex__column--shrink">
         <div class="feedback-box__content">
           <h3>Was this page helpful?</h3>
 
           <div class="flex gutter gutter--large">
             <div class="flex__column flex__column--shrink">
-              <button class="button button-hollow gutter gutter--small" data-feedback-button="helpful" data-active-class="button-fill button-fill--secondary">
+              <button class="button button-hollow gutter gutter--small" data-feedback-button="helpful"
+                data-active-class="button-fill button-fill--secondary">
                 <span class="button__icon">
                   {% include icons/symbols/thumb-up.svg %}
                 </span>
@@ -33,7 +41,8 @@ <h3>Was this page helpful?</h3>
             </div>
 
             <div class="flex__column flex__column--shrink">
-              <button class="button button-hollow gutter gutter--small" data-feedback-button="unhelpful" data-active-class="button-fill button-fill--gray">
+              <button class="button button-hollow gutter gutter--small" data-feedback-button="unhelpful"
+                data-active-class="button-fill button-fill--gray">
                 <span class="button__icon">
                   {% include icons/symbols/thumb-down.svg %}
                 </span>
@@ -52,4 +61,5 @@ <h3>Was this page helpful?</h3>
       </div>
     </div>
   </div>
+
 </div>

src/_sass/components/_button.scss

@@ -39,4 +39,5 @@
   padding: 8px 0px;
   text-align: left;
   color: #8f95b2;
+  display: block;
 }

src/connections/destination-data-control.md

@@ -37,4 +37,27 @@ If you no longer want to track an event, you can either remove it from your code
 
 ![](/docs/protocols/images/event-filters.png)
 
-Once you block an event in Segment, we'll stop forwarding it to all of your Destinations, including your warehouses. You can remove it from your code at your leisure. In addition to blocking track calls, Business plan customers can block all Page and Screen calls, as well as Identify traits and Group properties. 
+Once you block an event in Segment, Segment stops forwarding it to all of your Destinations, including your warehouses. You can remove it from your code at your leisure. In addition to blocking track calls, Business plan customers can block all Page and Screen calls, as well as Identify traits and Group properties. 
+
+## Export your Source Schema
+
+Segment allows you to download your Source Schema as a CSV file, maximizing portability and access to event data. You can download a copy of your schema by visiting the Source Schema page.
+
+![](images/export-source-schema.png)
+
+CSV files generate based on the current view of your Source Schema. Any search parameters or filters you apply to the current Source Schema view also apply to the CSV.
+
+You can download the following Track events:
+- Event Name
+- Last Seen (UTC)
+  - If greater than 30 days, the value is "more than 30 days ago"
+- Allowed Count
+- Blocked Count
+- Total Count
+- Planned (available for Protocols customers with a connected Tracking Plan)
+  - Values are "planned" or "unplanned"
+
+Export Schema is not available for Identify or Group events.
+
+> note ""
+> Export Schema doesn't include any actual values (for example, personal data) for the events, properties, and traits you are tracking for a specific source. Properties aren't included in the CSV.

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

@@ -10,7 +10,7 @@ hide-cmodes: true
 
 1. From the Segment web app, click **Catalog**.
 2. Search for "Appcues" in the Catalog, select it, and choose the source you'll connect to the destination.
-3. In the destination settings, enter your `Appcues Id` (for client-side integration functionality) and/or your `API Key` (for server-side integration functionality) from the [Appcues account page](https://my.appcues.com/account).
+3. In the destination settings, enter your `Account ID` (for client-side integration functionality) and/or your `API Key` (for server-side integration functionality) from the [Appcues account page](https://my.appcues.com/account).
 
 ### Server
 

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

@@ -137,8 +137,6 @@ Segment sends Page calls to Braze as custom events if you have enabled either **
 > info "Tip"
 > Add Segment's open-source [Middleware](https://github.com/segmentio/segment-braze-mobile-middleware) tool to optimize your integration. This tool limits [Data Point](https://www.braze.com/docs/user_guide/onboarding_with_braze/data_points/) use by debouncing duplicate identify() calls from Segment. For more information, see the project's [README](https://github.com/segmentio/segment-braze-mobile-middleware/blob/master/README.md#how-does-this-work).
 
-
-
 If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like:
 
 ```js
@@ -151,10 +149,42 @@ analytics.identify('ze8rt1u89', {
 
 When you Identify a user, Segment passes that user's information to Braze with `userId` as Braze's External User ID.
 
-If you are using a device-mode connection, Braze's SDK also automatically assigns a `braze_id` to every user. This allows Braze to capture anonymous activity from the device by matching on `braze_id` instead of `userId`. This applies to _device-mode connections_.
+If you're using a device-mode connection, Braze's SDK assigns a `device_id` and a backend identifier, `braze_id`, to every user. This allows Braze to capture anonymous activity from the device by matching on those identifiers instead of `userId`. This applies to _device-mode connections_.
 
 To send anonymous user data in cloud-mode, you must manually include the user's `braze_id` in all your Segment API calls in the `integrations.Braze.braze_id` or `context.integrations.Braze.braze_id` object.
 
+### Capture the braze_id of anonymous users
+
+Pass one of the many identifiers that may exist on an anonymous user profile to the [Braze's User by Identifier REST endpoint](https://www.braze.com/docs/api/endpoints/export/user_data/post_users_identifier/){:target='_blank'} to capture and export the `braze_id`. These identifiers include:
+- email address
+- phone number
+- device_id
+
+Choose an identifier that is available on the user profile at that point in the user lifecycle.
+
+For example, if you pass device_id to the User by Identifier endpoint:
+
+```js
+{
+  "device_id": “{{device_id}}",
+  "fields_to_export": ["braze_id"]
+}
+```
+
+The endpoint returns:
+
+```js
+{
+  "users": [
+    {
+        "braze_id": “{{braze_id}}"
+    }
+  ],
+  "message": "success"
+} 
+```
+
+
 > info "Tip"
 > Braze is complex. If you decide to use the `braze_id`, consider [contacting Segment Success Engineering](https://segment.com/help/contact/) or a Solutions Architect to verify your Braze implementation.
 

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

@@ -4,7 +4,7 @@ rewrite: true
 redirect_from: '/connections/destinations/catalog/supervised-ai/'
 ---
 
-[DataBrain](https://usedatabrain.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) is a tool for product-led companies that helps Sales and Customer Success teams close deals, adopt products, and retain customers through data and analytics. It ingests data from Segment and leverages machine learning techniques to send users automated alerts, and predict churn, conversion, and retention on any event you need to track.
+[DataBrain](https://usedatabrain.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) is a tool for product-led companies that helps Sales and Customer Success teams close deals, increase product adoption, and retain customers. DataBrain ingests data from Segment and leverages machine learning techniques to send users automated alerts, and predict churn, conversion, and retention on any event you need to track.
 
 This destination is maintained by DataBrain. For any issues with the destination, [contact the DataBrain Support team](mailto:[email protected]).
 

src/connections/destinations/catalog/facebook-app-events/index.md

@@ -249,10 +249,36 @@ You will have to be sure that the [IDFA](/docs/connections/sources/catalog/libra
 
 Similarly, on Android, you'll need to include the Play Services Ads library as [mentioned here](/docs/connections/sources/catalog/libraries/mobile/android/#how-do-you-handle-unique-identifiers-) in order for the `advertisingId` to populate.
 
-Once you have added these, you will start to see the `context.device.advertisingId` populate and the `context.device.adTrackingEnabled` flag set to `true` unless the user has ad tracking limited or is using a mobile ad blocker.
-
-_Note_: While the network is deprecated, the relevant iOS [framework](https://developer.apple.com/reference/iad) is not.
-
+Once you've added these, you will start to see the `context.device.advertisingId` populate and the `context.device.adTrackingEnabled` flag set to `true` unless the user has ad tracking limited or is using a mobile ad blocker.
+
+> note ""
+> While the network is deprecated, the relevant iOS [framework](https://developer.apple.com/reference/iad) is not.
+
+Facebook requires that payloads include the following:
+- `context.device.id`
+- `context.device.type`
+- `context.os.version`
+
+For example:
+
+```json
+{
+  "anonymousId": "507f191e810c19729de860ea",
+  "event": "Event Name",
+​  "context": {
+    "device": {
+      "id": "B5372DB0-C21E-11E4-8DFC-AA07A5B093DB",
+      "type": "ios"
+    },
+    "os": {
+      "version": "8.1.3"
+    }
+  },​
+  "messageId": "bbac-11e4-8dfc-aa07a53436b09b45567i8245237824",
+  "type": "track",
+  "userId": "97980cfea0067"
+}
+```
 
 ### Missing custom events
 

src/connections/destinations/catalog/google-analytics/index.md

@@ -2,6 +2,8 @@
 title: Google Universal Analytics Destination
 strat: google
 hide-dossier: true
+redirect_from:
+  - '/connections/destinations/catalog/google-universal-analytics'
 ---
 
 > warning "Migrate mobile implementations to Firebase"

src/connections/destinations/catalog/index-all.md

@@ -1,5 +1,6 @@
 ---
 title: Destination list
+hide-dossier: true
 ---