add rn

markzegarelli · markzegarelli · commit 8ca279edda01 · 2021-05-07T10:01:12.000-07:00
diff --git a/scripts/changelog.js b/scripts/changelog.js
@@ -18,7 +18,7 @@ const getLog = async (url = "") => {
     console.log(error)
   }
 }
-let libraries = ["analytics-android","analytics-ios"]
+let libraries = ["analytics-android","analytics-ios", "analytics-react-native", "analytics-java"]
 
 const updateLog = async(library) => {
 
diff --git a/src/_data/changelogs/analytics-android.yml b/src/_data/changelogs/analytics-android.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM GITHUB API. DO NOT EDIT
-# Releases last updated 2021-05-04 
+# Releases last updated 2021-05-07 
 releases:
 - version: 4.9.4
   url: 'https://github.com/segmentio/analytics-android/releases/tag/4.9.4'
diff --git a/src/_data/changelogs/analytics-ios.yml b/src/_data/changelogs/analytics-ios.yml
@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM GITHUB API. DO NOT EDIT
-# Releases last updated 2021-05-04 
+# Releases last updated 2021-05-07 
 releases:
 - version: 4.1.4
   url: 'https://github.com/segmentio/analytics-ios/releases/tag/4.1.4'
diff --git a/src/_data/changelogs/analytics-react-native.yml b/src/_data/changelogs/analytics-react-native.yml
@@ -0,0 +1,15 @@
+# AUTOGENERATED FROM GITHUB API. DO NOT EDIT
+# Releases last updated 2021-05-07 
+releases:
+- version: 1.4.0
+  url: 'https://github.com/segmentio/analytics-react-native/releases/tag/v1.4.0'
+  date: '2021-02-09T00:13:10Z'
+  notes: "# [1.4.0](https://github.com/segmentio/analytics-react-native/compare/v1.3.2...v1.4.0) (2021-02-08)\r\n\r\n### Bug Fixes\r\n\r\n- **android:** fix crash when promise resolves in debug mode ([#267](https://github.com/segmentio/analytics-react-native/issues/267)) ([a0e21d9](https://github.com/segmentio/analytics-react-native/commit/a0e21d9))\r\n- **package:** missing repo info ([#268](https://github.com/segmentio/analytics-react-native/issues/268)) ([6a2a93b](https://github.com/segmentio/analytics-react-native/commit/6a2a93b))\r\n- change React dependency to React-Core ([#254](https://github.com/segmentio/analytics-react-native/issues/254)) ([c51e689](https://github.com/segmentio/analytics-react-native/commit/c51e689))\r\n- don't call stringValue of strings ([#253](https://github.com/segmentio/analytics-react-native/issues/253)) ([226a9e4](https://github.com/segmentio/analytics-react-native/commit/226a9e4))\r\n\r\n### Features\r\n\r\n- **android:** allow opt-out for new lifecycle methods ([#256](https://github.com/segmentio/analytics-react-native/issues/256)) ([8dbadad](https://github.com/segmentio/analytics-react-native/commit/8dbadad))\r\n"
+- version: 1.4.4
+  url: 'https://github.com/segmentio/analytics-react-native/releases/tag/v1.4.4'
+  date: '2021-02-09T00:12:43Z'
+  notes: "Bug Fixes\r\n-android: bump deps and fix config issues (#298) (5a2ed9b)\r\n-ios bridge to respect promise (#295) (640aa73)\r\n"
+- version: v1.3.1
+  url: 'https://github.com/segmentio/analytics-react-native/releases/tag/v1.3.1'
+  date: '2020-09-10T00:05:06Z'
+  notes: "## [1.3.1](https://github.com/segmentio/analytics-react-native/compare/v1.3.0...v1.3.1) (2020-09-09)\r\n\r\n### Bug Fixes\r\n\r\n- **android:** bump android dependency ([#214](https://github.com/segmentio/analytics-react-native/issues/214)) ([acd0f2f](https://github.com/segmentio/analytics-react-native/commit/acd0f2f))\r\n- **ios:** bump ios dependency ([#217](https://github.com/segmentio/analytics-react-native/issues/217)) ([4848bbd](https://github.com/segmentio/analytics-react-native/commit/4848bbd))\r\n\r\n<a name=\"1.3.0\"></a>"
diff --git a/src/_data/changelogs/analytics-ruby.yml b/src/_data/changelogs/analytics-ruby.yml
@@ -0,0 +1,3 @@
+# AUTOGENERATED FROM GITHUB API. DO NOT EDIT
+# Releases last updated 2021-05-07 
+releases: []
diff --git a/src/_data/sidenav/strat.yml b/src/_data/sidenav/strat.yml
@@ -152,3 +152,6 @@ sections:
     title: Troubleshooting Analytics-React-Native
   - path: /connections/sources/catalog/libraries/mobile/react-native/react-faqs/
     title: React-Native FAQs
+  - path: /connections/sources/catalog/libraries/mobile/react-native/changelog
+    title: Analytics-React-Native Changelog
+
diff --git a/src/connections/data-residency.md b/src/connections/data-residency.md
@@ -71,7 +71,33 @@ To begin with Local Data Storage, complete the following steps in your AWS accou
 
     Segment requires this access to write raw data to your regionally hosted S3 bucket. Specifically, this allows Segment (as the Segment S3-copy user) to use `s3:PutObject`. To enable encryption at rest, use the default S3 mechanism. If you have server-side encryption enabled with AWS KMS managed keys, see the additional [required configuration step](/docs/connections/storage/catalog/amazon-s3/#encryption). To edit the bucket policy, right-click the bucket name in the AWS management console, and select **Edit policy**.
 
-4. Create a new IAM role in your AWS account with a trust relationship to the role which allows Segment to use the Segment `workspace_id` as `externalID`.
+4. Create a new IAM role in your AWS account for Segment to assume. Attach the following trust relationship document to the role:
+    ```json
+    {
+      "Version": "2012-10-17",
+      "Statement": [
+        {
+          "Sid": "",
+          "Effect": "Allow",
+          "Principal": {
+            "AWS": [
+              "arn:aws:iam::595280932656:role/segment-regional-archives-production-access"
+            ]
+          },
+          "Action": "sts:AssumeRole",
+          "Condition": {
+            "StringEquals": {
+              "sts:ExternalId": [
+                "WORKSPACE_ID"
+              ]
+            }
+          }
+        }
+      ]
+    }
+    ```
+  **Note**: This IAM role is used for replays only. The writes to the bucket are performed directly by the user added in step 3.
+
 5. Attach this IAM policy to the role defined in Step 4.
   ```json
     {
@@ -90,7 +116,7 @@ To begin with Local Data Storage, complete the following steps in your AWS accou
           "Effect": "Allow",
           "Action": "s3:*Object*",
           "Resource": [
-            "arn:aws:s3:::YOUR_BUCKET_NAME/*",
+            "arn:aws:s3:::YOUR_BUCKET_NAME/*"
           ]
         }
       ]
diff --git a/src/connections/destination-data-control.md b/src/connections/destination-data-control.md
@@ -38,109 +38,3 @@ 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. 
-
----
-
-
-
-## How do I prevent new data from being allowed by default?
-
-If you've solidified your tracking plan and don't want any rogue events finding their way to your warehouses and end tools, we recommend activating our new feature, **Schema Defaults**. When you lock your schema, or set your Schema Defaults to "Block," Segment will automatically prevent these calls from being sent downstream. You can activate this for new events—including `track`, `page`, and `screen` calls—or for new `identify` traits and `group` properties. 
-
-Locking your schema only takes a few seconds and will protect your data from un-spec'd events or tracking errors. To configure your Schema Defaults, go to your Schema page, and then select "General" from the left-hand navigation.
-
-![](images/schema-defaults.png)
-
-
-**Overview of Schema Default Settings**
-
-**Default**
-
-**Allow**
-
-**Block**
-
-**New Events**
-
-All new events will be allowed in Segment and sent to all Destinations.
-
-No new events will be allowed in Segment or sent to your Destinations. Any event that is already being tracked and part of your Schema will not be impacted.
-
-**New Group Properties**
-
-All new group properties will be allowed in Segment and sent to all Destinations.
-
-No new group properties will be allowed in Segment or sent to your Destinations.
-
-**New Identify Traits**
-
-All new identify traits will be allowed in Segment and sent to all Destinations.
-
-No new identify traits will be allowed in Segment or sent to your Destinations.
-
-**Example: Order Completed**
-
-For example, if you set your Schema Defaults for New Events to "Block," and a new event, `Order Completed`, is tracked, Segment will automatically block the event and it will not be sent to your warehouse or downstream tools. The event will continue to be blocked until you actively choose to allow it.
-
-You will need to upgrade to the latest [iOS](/docs/connections/sources/catalog/libraries/mobile/ios/#install-the-sdk) and/or [Android](/docs/connections/sources/catalog/libraries/mobile/android/#step-1-install-the-library) SDKs for Schema Defaults to apply to events sent from mobile sources. 
-
-## **What is considered a "new" event?**
-
-New events refer to events that have not previously been sent to a given Source. Let's say you've only sent the following events from your Javascript source:
-
-*   `Products Searched`
-
-*   `Product List Viewed`
-
-*   `Product List Filtered`
-
-
-Your Schema Default setting will not have any impact on these three events because they are not considered new. You can manually block them, but your Schema Default setting will not change the status of these events. 
-
-Here's what will happen the first time a new event, `Promotion Viewed`, is sent to this Source:
-
-*   **Schema Default Set to Allow:** `Promotion Viewed` will be "allowed," which means the event will be sent to all enabled Destinations.
-
-*   **Schema Default Set to Block:** `Promotion Viewed` will be "blocked," which means the event will not be sent to any Destinations.
-
-
-## **What happens to blocked events and properties? **
-
-When an event or property is blocked, the name of the event or property will be added to your Schema page, but no data will be tracked. By default, data from blocked events and properties is not recoverable. You can always re-enable the event or property if you want to begin tracking it going forward.
-
-If you're concerned about permanently discarding data from blocked events, you can use advanced settings to forward these events to a designated Source. From there, you can send your data to a separate S3 bucket or warehouse for further analysis. That way if you decide you _do_ want the data in your downstream tools, you can ask Segment to Replay the data into your server-side Destinations. If you choose to route blocked events, this will contribute to your MTU count. 
-
-**How do I forward blocked events?**
-
-First, you will want to create a new Source to receive data from blocked Events and Traits. This Source should only be configured to received blocked data, so make sure it isn't receiving data from anywhere else. We recommend creating a new "Javascript" source and naming it "Blocked Data from \[Source Name\]." 
-
-After you have created a new source, go to the Schema page for your primary Source and then select "General" from the left-hand navigation. Under "Advanced Settings," you will see two options:
-
-*   Block and discard: select this option if you want to permanently discard data from blocked Events and Traits.
-
-*   Forward: select this option if you would like to forward data from blocked Events and Traits to a separate source.
-
-
-Select "Forward," and then select the new Source you created to receive blocked data. **As a reminder, if you choose to route blocked events, this will contribute to your MTU count. **
-
-## **How am I charged for blocked events? **
-
-Your bill is based on the number of Monthly Tracked Users (MTU). MTUs are the number of identified and anonymous users that you track with Segment. We only count users once per month, even if they perform multiple actions across your site or app. In most cases, blocked events will have no impact on your MTU count. If you choose to route blocked events, this will contribute to your MTU count. 
-
-## **How do I configure notifications?**
-
-While protecting the integrity of your data is helpful, we also want to flag any blocked events for you, so you can make any needed changes in your code or approve a new event. Source notifications will alert you when a new event is blocked due to your Schema Defaults. You can view these notifications in the Activity Feed in the app or subscribe to email notifications. 
-
-You can view these notifications in the Activity Feed in the app or subscribe to email notifications. To subscribe to email notifications, go to your workspace settings, then click "Notification Settings," and subscribe to notifications for Sources by entering your email address and clicking "Save Changes." You can enter multiple email addresses separated by a comma.
-
-## **When should I lock my schema? **
-
-Whether you're just about to implement a new spec or you have been tracking the same events for years, Schema Defaults make it easy to protect your data and fix data quality issues.
-
-Here are a few signs you may be ready to lock your schema:
-
-*   You are concerned about developers implementing rogue events
-
-*   You want to actively approve which events are tracked and routed to your downstream Destinations
-
-*   You have created a tracking plan and want to use Segment to enforce it
diff --git a/src/connections/destinations/add-destination.md b/src/connections/destinations/add-destination.md
@@ -115,8 +115,11 @@ To connect a source to more than one instance of a destination in the Segment we
 You must give each instance of the destination connected to the same source a unique name. Segment recommends that you use descriptive names rather than numbers, so other Segment users can understand which Segment destinations are linked to which tool instances. For example, you might use "Amplitude North America" and "Amplitude South America", instead of "Amplitude 1" and "Amplitude 2".
 
 If you added the first instance of your destination before multi-instance destinations became available, that instance is automatically named for the destination with no other identifiers, for example "Amplitude". You cannot currently edit these first destinations' names.
+
 Some destinations do not support having multiple instances connected to the same source. In that case, the option to add a second instance of that destination does not appear.
 
+You can create unique destination filters for each destination instance connected to the same source. 
+
 ### Connect to more than one instance of a destination using the Config API
 
 You can add multiple instances of a destination using the Segment Config API. See the Segment Config [API documentation](https://reference.segmentapis.com/?version=latest#39ce0439-0969-48c3-ba49-b22a46c41060). If a destination does not support multi-instance, the Config API throws an appropriate error.
@@ -137,7 +140,6 @@ For more information see [the compatible destination lists below](#multi-instanc
 
 ### Other multi-instance destination considerations
 
-- **Destination filters and multi-instance destinations:** Destination filters are specific to each source, and currently operate on *all* instances of a destination connected to that source. Support for destination filters for individual destination instances is coming soon.
 
 - **Multiple Data Lakes:** Segment does not currently support connecting a single source to multiple instances of a data lakes destination. [Contact Segment Customer Success](https://segment.com/help/contact/) if this would be useful for your organization.
 
diff --git a/src/connections/destinations/catalog/braze/index.md b/src/connections/destinations/catalog/braze/index.md
@@ -132,6 +132,11 @@ Page calls are only sent to Braze if you have enabled either "Track All Pages" o
 
 ## Identify
 
+> 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
@@ -148,8 +153,8 @@ If you are using a device-mode connection, Braze's SDK also automatically assign
 
 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.
 
-> tip ""
-> **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 validate your Braze implementation.
+> 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 validate your Braze implementation.
 
 Segment's special traits recognized as Braze's standard user profile fields (in parentheses) are:
 
@@ -168,6 +173,11 @@ All other traits (except their [reserved user profile fields](https://www.braze.
 
 ## Track
 
+> info "Tip"
+> To lower [Data Point](https://www.braze.com/docs/user_guide/onboarding_with_braze/data_points/) use, send only the Events which are relevant for campaigns and segmentation to the Braze destination. For more information, see /docs/protocols/schema/.
+
+
+
 If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like:
 
 ```
@@ -507,8 +517,8 @@ The following custom event appears in Braze on the user’s profile:
 
 ![](images/last_viewed-track-braze.png)
 
-> success ""
-> **Tip**: You can change the name of the “computed trait” event that Braze receives by going to the Personas Destination Connection Settings.
+> info "Tip"
+> You can change the name of the “computed trait” event that Braze receives in the Personas Destination Connection Settings.
 
 ### Audiences in Braze
 
@@ -548,8 +558,8 @@ The following custom event appears in Braze on the user’s profile when they en
 
 ![](images/dormant-track-braze.png)
 
-> success ""
-> **Tip**: You can change the name of the “Audience Entered” event that Braze receives from the Personas Destination Connection Settings.
+> info "Tip"
+> You can change the name of the “Audience Entered” event that Braze receives in the Personas Destination Connection Settings.
 
 ## Setting up Personas with Braze
 
diff --git a/src/connections/destinations/catalog/facebook-pixel-server-side/index.md b/src/connections/destinations/catalog/facebook-pixel-server-side/index.md
@@ -4,6 +4,7 @@ rewrite: true
 beta: true
 strat: facebook
 redirect_from: '/connections/destinations/catalog/facebook-conversions-api/'
+hide-dossier: true
 ---
 
 <!-- LR: 2/16/2021: Redirect pulls in from `facebook-conversions-api` because while this destination's display name has changed, the slug is still the old name and the docs build needs to match on slug to find it in `destinations.yml` -->
diff --git a/src/connections/sources/catalog/libraries/mobile/android/changelog.md b/src/connections/sources/catalog/libraries/mobile/android/changelog.md
@@ -1,5 +1,6 @@
 ---
 title: Analytics-Android Changelog
 repo: analytics-android
+strat: android
 ---
 {% include content/changelog.html %}
diff --git a/src/connections/sources/catalog/libraries/mobile/android/index.md b/src/connections/sources/catalog/libraries/mobile/android/index.md
@@ -4,14 +4,17 @@ strat: android
 repo: analytics-android
 ---
 
-Analytics for Android makes it simple to send your data to any tool without having to learn, test or implement a new API every time.
 
-All of Segment's client sources are open-source, so you can [view Analytics for Android on GitHub](https://github.com/segmentio/analytics-android), or check out Segment's other [browser and server-side sources](/docs/connections/sources/catalog/) too.
+[![Maven Central](https://maven-badges.herokuapp.com/maven-central/com.segment.analytics.android/analytics/badge.svg)](https://maven-badges.herokuapp.com/maven-central/com.segment.analytics.android/analytics)
+
+Analytics for Android makes it simple to send your data to any tool without having to learn, test or implement a new API every time.
 
-Want to stay updated on releases? Subscribe to the [release feed](https://github.com/segmentio/analytics-android/releases.atom).
 
 Analytics for Android only supports any Android device running API 14 (Android 4.0) and higher. This includes Amazon Fire devices.
 
+> info "Analytics-Kotlin Pilot"
+> A pilot release of the analytics-kotlin library is available at the [Analytics-Kotlin](https://github.com/segmentio/analytics-kotlin) repository. This library is governed by Segment's [First-Access and Beta terms](https://segment.com/legal/first-access-beta-preview/), and should not be used in production scenarios.
+
 > success ""
 > In addition to the documentation here, you can also [read the Javadocs for all versions of Analytics-Android on Javadoc.io](https://javadoc.io/doc/com.segment.analytics.android/analytics/latest/index.html).
 
diff --git a/src/connections/sources/catalog/libraries/mobile/ios/changelog.md b/src/connections/sources/catalog/libraries/mobile/ios/changelog.md
@@ -1,5 +1,6 @@
 ---
 title: Analytics-iOS Changelog
 repo: analytics-ios
+strat: ios
 ---
 {% include content/changelog.html %}
diff --git a/src/connections/sources/catalog/libraries/mobile/ios/index.md b/src/connections/sources/catalog/libraries/mobile/ios/index.md
diff --git a/src/connections/sources/catalog/libraries/mobile/react-native/changelog.md b/src/connections/sources/catalog/libraries/mobile/react-native/changelog.md
diff --git a/src/connections/sources/catalog/libraries/mobile/react-native/index.md b/src/connections/sources/catalog/libraries/mobile/react-native/index.md
diff --git a/src/guides/filtering-data.md b/src/guides/filtering-data.md
diff --git a/src/personas/using-personas-data.md b/src/personas/using-personas-data.md
diff --git a/src/protocols/schema.md b/src/protocols/schema.md
diff --git a/src/protocols/validate/connect-sources.md b/src/protocols/validate/connect-sources.md

Original file line number	Diff line number	Diff line change
`@@ -18,7 +18,7 @@ const getLog = async (url = "") => {`
`18`	`18`	`console.log(error)`
`19`	`19`	`}`
`20`	`20`	`}`
`21`		`-let libraries = ["analytics-android","analytics-ios"]`
	`21`	`+let libraries = ["analytics-android","analytics-ios", "analytics-react-native", "analytics-java"]`
`22`	`22`
`23`	`23`	`const updateLog = async(library) => {`
`24`	`24`
Original file line number	Diff line number	Diff line change
`@@ -0,0 +1,3 @@`
	`1`	`+# AUTOGENERATED FROM GITHUB API. DO NOT EDIT`
	`2`	`+# Releases last updated 2021-05-07`
	`3`	`+releases: []`