Merge pull request #2247 from segmentio/friday-fixes

Batch of small fixes

Author: markzegarelli

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/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
 ---
 
 

src/connections/sources/catalog/libraries/server/java/index.md

@@ -16,7 +16,8 @@ Want to stay updated on releases? Subscribe to the [release feed](https://github
 
 ## Getting Started
 
-[![Javadocs](https://javadoc-badge.appspot.com/com.segment.analytics.java/analytics.svg?label=javadoc)](https://javadoc-badge.appspot.com/com.segment.analytics.java/analytics)
+[![Maven Central](https://maven-badges.herokuapp.com/maven-central/com.segment.analytics.java/analytics/badge.svg)](https://maven-badges.herokuapp.com/maven-central/com.segment.analytics.java/analytics)
+
 
 ### Install the library
 

src/privacy/faq.md

@@ -55,8 +55,10 @@ In addition to your Raw Data destinations (Amazon S3 and Data Warehouses), we ca
 - Appcues
 - Vero
 - Google Analytics
+- Customer.io
+- Optimizely Full Stack
 
-Segment cannot guarantee that data is deleted from your Destinations. When you issue a user deletion request, Segment forwards the request to supported streaming Destinations. You must still contact these Destinations to confirm that they have executed the request.
+Segment cannot guarantee that data is deleted from your Destinations. When you issue a user deletion request, Segment forwards the request to supported streaming Destinations. You must still contact these Destinations to confirm that they've executed the request.
 
 ### Which destinations require additional destination setting configuration?