diff --git a/src/_includes/content/react-dest.md b/src/_includes/content/react-dest.md
deleted file mode 100644
index 260f9a937c..0000000000
--- a/src/_includes/content/react-dest.md
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-{% assign currentSlug = page.url | split: "/" | last %}
-{% assign thisDest = site.data.catalog.destinations.items | where: "slug", currentSlug | first %}
-{% assign thisDestName = thisDest.display_name %}
-{% assign thisDestRNspecific = include.only %}
-
-
-{% if thisDestRNspecific %}
-
-
-
-The {{thisDestName}} device-mode destination SDK is only available for {{thisDestRNspecific}} in React Native.
-
-{%endif%}
-
-To add the {{thisDestName}} device-mode SDK to a [React Native](/docs/connections/sources/catalog/libraries/mobile/react-native/) project using Segment's `1.5.1≤` release:
-1. Navigate to the root folder of your project, and run a `yarn add @segment/analytics-react-native-{{thisDestName | downcase | replace: " ", "-" }}{% if thisDestRNspecific %}-{{thisDestRNspecific}}{%endif%}` command to add the destination SDK to your project.
-2. Add an `import` statement to your project, as in the example below.
- ```js
- import {{thisDestName | replace: " ", "" }} from '@segment/analytics-react-native-{{thisDestName | downcase | replace: " ", "-" }}{% if thisDestRNspecific %}-{{thisDestRNspecific}}{%endif%}'
- ```
-3. In the same project file, add the destination to the `using` list in the `await` command.
- ```js
- await analytics.setup('YOUR_WRITE_KEY', {
- // Add any of your Device-mode destinations. This ensures they load before continuing.
- using: {{thisDestName | replace: " ", "" }}
- // ...
- })
- ```
-4. Finally, change to your iOS development folder ( `cd ios` ) and run `pod install`.
diff --git a/src/connections/destinations/catalog/actions-launchdarkly-audiences/index.md b/src/connections/destinations/catalog/actions-launchdarkly-audiences/index.md
new file mode 100644
index 0000000000..ccadb85bb4
--- /dev/null
+++ b/src/connections/destinations/catalog/actions-launchdarkly-audiences/index.md
@@ -0,0 +1,32 @@
+---
+title: LaunchDarkly Audiences Destination
+id: 64e72a310da9ebedf99c8937
+beta: true
+---
+
+{% include content/plan-grid.md name="actions" %}
+
+[LaunchDarkly](https://launchdarkly.com){:target="_blank"} is a feature management platform that empowers development teams to safely deliver, control, and measure their software through feature flags.
+
+With LaunchDarkly, you can release features that target specific groups, such as beta users, and premium accounts, using segments. This destination allows you to sync Engage Audiences to LaunchDarkly segments, letting you concentrate more on deploying features and less on managing end users between platforms.
+
+LaunchDarkly maintains this destinatino. For any issues with the destination, [contact the LaunchDarkly Support team](mailto:support@launchdarkly.com).
+
+{% include content/ajs-upgrade.md %}
+
+## Getting started
+
+1. In LaunchDarkly, navigate to [Account settings](https://app.launchdarkly.com/settings/projects){:target="_blank"} and copy the client-side ID for the project and environment where you would like to create an Engage Audience synced segment.
+2. In LaunchDarkly, create a service token with either a Writer role or a custom role. If your service token has a custom role, it must have the actions `createSegment` and `updateIncluded` to sync a segment from an Engage Audience. To learn how to create a service token, read [Creating API access tokens](https://docs.launchdarkly.com/home/account-security/api-access-tokens#creating-api-access-tokens){:target="_blank"}.
+3. From the Segment web app, navigate to **Engage > Audiences**. Ensure you are in the Engage space you plan to use with the LaunchDarkly Audiences destination. Either choose an existing Engage audience or create a new one. This is the audience you plan to sync with LaunchDarkly.
+4. Navigate to **Engage > Engage Settings** and click **Destinations**. Ensure you are still in the correct Engage space.
+5. Search for `LaunchDarkly Audiences` and select the destination. Click **Add destination**.
+6. On the **Select Source** screen, your Engage space should already be selected as the source. Click **Confirm Source**.
+7. On the Destination **Settings** tab, name your destination and provide your LaunchDarkly client-side ID and service token.
+8. Toggle **Enable Destination** on and click **Save Changes**.
+9. Navigate to the **Mappings** tab, click **New Mapping**, and select the **Sync Engage Audience to LaunchDarkly** pre-built mapping.
+10. Under **Select mappings**, modify the default mappings as needed. In most cases, you shouldn't need to make any changes.
+11. Click **Save**.
+12. Ensure the **Status** toggle on the **Mappings** tab is enabled.
+
+{% include components/actions-fields.html %}
diff --git a/src/connections/destinations/catalog/adjust/index.md b/src/connections/destinations/catalog/adjust/index.md
index 8b390b2906..2c62812ebd 100644
--- a/src/connections/destinations/catalog/adjust/index.md
+++ b/src/connections/destinations/catalog/adjust/index.md
@@ -109,10 +109,6 @@ analytics = new Analytics.Builder(this, "write_key")
After you build and release to the App Store, Segment automatically starts translating and sending your data to Adjust.
-### React Native
-
-{% include content/react-dest.md %}
-
### Server
The Cloud-mode integration allows you to send *supplemental* data to Adjust. This *does not* include attribution events. If you rely on the Adjust server-side component, and do not bundle the Segment-Adjust SDK, your installs will not be attributed. E-commerce events and other general `track` events are supported out of the box. You **must** map your `track` events to your custom Adjust Event Token in your [Adjust destination settings](#map-your-events-to-custom-adjust-event-tokens).
diff --git a/src/connections/destinations/catalog/amplitude/index.md b/src/connections/destinations/catalog/amplitude/index.md
index caf8a4d3e7..87082a1238 100644
--- a/src/connections/destinations/catalog/amplitude/index.md
+++ b/src/connections/destinations/catalog/amplitude/index.md
@@ -42,11 +42,6 @@ In addition to Segment's Amplitude documentation, Amplitude provides a [Segment
If you included Segment's JavaScript snippet on your page, then Amplitude's SDK loads on your page automatically and you can use Segment's to begin sending events right away.
-### React Native device mode set up
-
-{% include content/react-dest.md %}
-
-
## Page and Screen
If you're not familiar with the Segment Specs, take a look to understand what the [Page](/docs/connections/spec/page/) and [Screen](/docs/connections/spec/screen/) methods do. By default, Segment does not send these standard calls to Amplitude. However, you can enable them with the destination settings below, which you can find under the "Optional Settings" tab.
diff --git a/src/connections/destinations/catalog/branch-metrics/index.md b/src/connections/destinations/catalog/branch-metrics/index.md
index 00b6ecec68..fd90fa40d9 100644
--- a/src/connections/destinations/catalog/branch-metrics/index.md
+++ b/src/connections/destinations/catalog/branch-metrics/index.md
@@ -29,28 +29,6 @@ This destination is maintained by Branch. For any issues with the destination, [
5. Paste the Branch Key in the destination settings and click **Save**.
-### Adding Branch device-mode SDKs for React Native
-
-
-
-To add the Branch device-mode SDK to a [React Native](/docs/connections/sources/catalog/libraries/mobile/react-native/) project using Segment's `1.5.1≤` release:
-1. Navigate to the root folder of your project, and run a `yarn add branch` command to add the destination SDK to your project.
-2. Add an `import` statement to your project, as in the example below.
- ```js
- import Branch from '@segment/analytics-react-native-branch'
- ```
-3. In the same project file, add the destination to the `using` list in the `await` command.
- ```js
- await analytics.setup('YOUR_WRITE_KEY', {
- // Add any of your Device-mode destinations. This ensures they load before continuing.
- using: Branch
- // ...
- })
- ```
-4. Finally, change to your iOS development folder ( `cd ios` ) and run `pod install`.
-
-
-
## Identify
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 iOS call would look like:
diff --git a/src/connections/destinations/catalog/braze/index.md b/src/connections/destinations/catalog/braze/index.md
index 8a6fed2f56..59a192524c 100644
--- a/src/connections/destinations/catalog/braze/index.md
+++ b/src/connections/destinations/catalog/braze/index.md
@@ -108,30 +108,6 @@ To use the latest Braze SDK to collect IDFAs you must do the following:
.build();
```
-### React Native device-mode set up
-
-
-
-To add the Braze device-mode SDK to a [React Native](/docs/connections/sources/catalog/libraries/mobile/react-native/) project using Segment's `1.5.1≤` release:
-1. Navigate to the root folder of your project, and run a `yarn add appboy` command to add the destination SDK to your project.
-2. Add an `import` statement to your project, as in the following example.
- ```js
- import Braze from '@segment/analytics-react-native-appboy'
- ```
-3. In the same project file, add the destination to the `using` list in the `await` command.
- ```js
- await analytics.setup('YOUR_WRITE_KEY', {
- // Add any of your Device-mode destinations. This ensures they load before continuing.
- using: [Braze]
- // ...
- })
- ```
-4. Change to your iOS development folder ( `cd ios` ) and run `pod install`.
-
-
-> note ""
-> Braze was formerly known as "Appboy", and the Braze React component still uses that name. Be sure to use the old name!
-
## Page
If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like:
diff --git a/src/connections/destinations/catalog/bugsnag/index.md b/src/connections/destinations/catalog/bugsnag/index.md
index 54fc98b617..9ad909dece 100644
--- a/src/connections/destinations/catalog/bugsnag/index.md
+++ b/src/connections/destinations/catalog/bugsnag/index.md
@@ -31,13 +31,6 @@ If you'd like to integrate with Bugsnag's iOS and/or Android SDKs, in addition t
2. [iOS](https://github.com/segment-integrations/analytics-ios-integration-bugsnag)
-
-### React Native
-
-{% include content/react-dest.md %}
-
-- - -
-
## Identify
Once you've correctly set up your Bugsnag integration, you should [`identify`](/docs/connections/spec/identify/) each of your users as soon as you know their identity (this typically happens after log in or sign up), so that Bugsnag can provide you with more visibility into which user is encountering which error.
diff --git a/src/connections/destinations/catalog/clevertap/index.md b/src/connections/destinations/catalog/clevertap/index.md
index 1a2143e1f7..380bc9a4d3 100644
--- a/src/connections/destinations/catalog/clevertap/index.md
+++ b/src/connections/destinations/catalog/clevertap/index.md
@@ -163,12 +163,6 @@ No further action is required to integrate in-app notifications, which are regis
CleverTap has created a sample iOS application that integrates CleverTap using Segment. Check it out at the [GitHub repository](https://github.com/CleverTap/clevertap-segment-ios/tree/master/Example){:target="_blank"}.
-
-## React Native
-
-{% include content/react-dest.md %}
-
-
## Server-Side
### Push Tokens
diff --git a/src/connections/destinations/catalog/comscore/index.md b/src/connections/destinations/catalog/comscore/index.md
index 9d7f3c7d4f..2917cf4ba7 100644
--- a/src/connections/destinations/catalog/comscore/index.md
+++ b/src/connections/destinations/catalog/comscore/index.md
@@ -30,10 +30,6 @@ To install comScore via Segment on iOS, please follow the additional set up step
### Android
To install comScore via Segment on Android, please follow the additional set up steps in the Segment-Comscore Android repository [here](https://github.com/segment-integrations/analytics-android-integration-comscore#analytics-android-integration-comscore).
-### React Native
-
-{% include content/react-dest.md only="ios"%}
-
## Page
Calling `page` on web will automatically send a call to comScore's Application Tag, along with any `labels` mapped in the **Beacon Param Map** setting.
diff --git a/src/connections/destinations/catalog/countly/index.md b/src/connections/destinations/catalog/countly/index.md
index af294f4b3e..b15ac525e9 100644
--- a/src/connections/destinations/catalog/countly/index.md
+++ b/src/connections/destinations/catalog/countly/index.md
@@ -12,11 +12,6 @@ After you integrate the appropriate destination with your app, add the Countly d
These new settings take up to an hour to propagate to existing users, but is instantaneous for new users.
-### React Native set up
-
-{% include content/react-dest.md %}
-
-
## Track
Countly helps you better understand your user's behavior. To accomplish that, [`track`](/docs/connections/spec/track/) your user's actions in detail.
diff --git a/src/connections/destinations/catalog/crittercism/index.md b/src/connections/destinations/catalog/crittercism/index.md
index c292c46af7..78db02ee0b 100644
--- a/src/connections/destinations/catalog/crittercism/index.md
+++ b/src/connections/destinations/catalog/crittercism/index.md
@@ -11,13 +11,6 @@ To get started with Crittercism and Segment, you'll want to integrate our [Andro
Once the Segment library is integrated with your app, toggle Crittercism on in your Segment destination catalog, and add your **App Id** which you can find in your [Crittercism app settings](https://app.crittercism.com/developers/login). These new settings will take up to an hour to propagate to all of your existing users. For new users it'll be instantaneous!
-### React Native set up
-
-{% include content/react-dest.md %}
-
-- - -
-
-
## Identify
Crittercism can show you information about the user using your app. You can record that info with our [`identify`](/docs/connections/spec/identify/) method. You should put the `identify` call as soon as you know the user's identity. This usually happens after they register or log in.
diff --git a/src/connections/destinations/catalog/facebook-app-events/index.md b/src/connections/destinations/catalog/facebook-app-events/index.md
index 7c310e6544..655ae329f2 100644
--- a/src/connections/destinations/catalog/facebook-app-events/index.md
+++ b/src/connections/destinations/catalog/facebook-app-events/index.md
@@ -28,10 +28,6 @@ This page is about the **Facebook App Events**. For documentation on other Faceb
3. In the destination settings, enter your Facebook App ID which can be retrieved from your [Facebook Apps dashboard](https://developers.facebook.com/apps/).
4. Once you turn on the Facebook App Events integration in your app's Segment project, we'll start sending `track` data to Facebook's App Events endpoints.
-### Using Facebook App Events with React Native Device Mode
-
-{% include content/react-dest.md only="ios" %}
-
## Screen
If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](/docs/connections/spec/screen/) does. An example call would look like:
diff --git a/src/connections/destinations/catalog/flurry/index.md b/src/connections/destinations/catalog/flurry/index.md
index f9343302ef..ae42070158 100644
--- a/src/connections/destinations/catalog/flurry/index.md
+++ b/src/connections/destinations/catalog/flurry/index.md
@@ -19,10 +19,6 @@ Our Flurry destination code is open sourced on GitHub. Feel free to check it out
_Note: Flurry does not always display data in real time. We've seen that it can take anywhere from a few hours to a few days for certain types of data to sync with Flurry._
-### React Native set up
-
-{% include content/react-dest.md %}
-
## Screen
If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](/docs/connections/spec/screen/) does.
diff --git a/src/connections/destinations/catalog/inflection/index.md b/src/connections/destinations/catalog/inflection/index.md
index a0c58895a1..c5ac0630e6 100644
--- a/src/connections/destinations/catalog/inflection/index.md
+++ b/src/connections/destinations/catalog/inflection/index.md
@@ -21,24 +21,6 @@ This destination is maintained by Inflection. For any issues with the destinatio
Inflection supports the following methods, as specified in the [Segment Spec](/docs/connections/spec).
-### Page
-
-Send [Page](/docs/connections/spec/page) calls to be added to *Product Activity* on Inflection App. For example:
-
-```js
-analytics.page()
-```
-
-
-### Screen
-
-Send [Screen](/docs/connections/spec/screen) calls to be added to *Product Activity* on Inflection App. For example:
-
-```obj-c
-[[SEGAnalytics sharedAnalytics] screen:@"Home"];
-```
-
-
### Identify
Send [Identify](/docs/connections/spec/identify) calls to Identify a user. The traits should have the `email` trait to be processed. All the other reserved traits are optional, but will be used to populate *Person DB* if available.
@@ -58,4 +40,18 @@ Send [Track](/docs/connections/spec/track) calls to be added to *Product Activit
```js
analytics.track('Login Button Clicked')
+```
+
+### Group
+
+Send [Group](/docs/connections/spec/group) calls to tie a user to an org. There are two IDs that are relevant in a group call: the userId, which belongs and refers to the user, and the groupId, which belongs and refers to the specific group. A user can belong to multiple groups, each associated with a different groupId, but the user will have only one userId linked to each of these different groups.
+
+```js
+ analytics.group("0e8c78ea9d97a7b8185e8632", {
+name: "Initech",
+industry: "Technology",
+employees: 329,
+plan: "enterprise",
+"total billed": 830
+});
```
\ No newline at end of file
diff --git a/src/connections/destinations/catalog/intercom/index.md b/src/connections/destinations/catalog/intercom/index.md
index 560cda4cfd..abdc986c82 100644
--- a/src/connections/destinations/catalog/intercom/index.md
+++ b/src/connections/destinations/catalog/intercom/index.md
@@ -52,10 +52,6 @@ Before reading the specific instructions for iOS or Android below, make sure you
.build();
```
-### React Native
-
-{% include content/react-dest.md %}
-
## Page
If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like:
diff --git a/src/connections/destinations/catalog/localytics/index.md b/src/connections/destinations/catalog/localytics/index.md
index 246593ab78..f13d1bcc1c 100644
--- a/src/connections/destinations/catalog/localytics/index.md
+++ b/src/connections/destinations/catalog/localytics/index.md
@@ -31,12 +31,6 @@ is not yet supported.
You must also add the Maven Localytics repo (since Localytics doesn't publish it on Maven Central). You can see an example of how to add that
[here](https://github.com/segment-integrations/analytics-android-integration-localytics/blob/master/build.gradle#L44).
-### React Native set up
-
-{% include content/react-dest.md %}
-
-- - -
-
## Identify
When you call [`identify`](/docs/connections/spec/identify/), we'll set the Localytics
diff --git a/src/connections/destinations/catalog/loops-actions/index.md b/src/connections/destinations/catalog/loops-actions/index.md
new file mode 100644
index 0000000000..2e0025bf08
--- /dev/null
+++ b/src/connections/destinations/catalog/loops-actions/index.md
@@ -0,0 +1,7 @@
+---
+title: 'Loops (Actions) Destination'
+hidden: true
+id: 63360a5fe290ca3fdfad4a68
+published: false
+beta: true
+---
diff --git a/src/connections/destinations/catalog/mixpanel/index.md b/src/connections/destinations/catalog/mixpanel/index.md
index 5336e0bbbc..e352e09563 100644
--- a/src/connections/destinations/catalog/mixpanel/index.md
+++ b/src/connections/destinations/catalog/mixpanel/index.md
@@ -22,10 +22,6 @@ Segment's Mixpanel destination code is open source and available on GitHub. You
3. Copy your Mixpanel "API Secret" and "Token", and paste them into the Connection Settings in Segment.
4. Enable the destination to start sending your data to Mixpanel.
-### Adding device-mode SDKs to React Native
-
-{% include content/react-dest.md %}
-
## Page
If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like:
diff --git a/src/connections/destinations/catalog/quantcast/index.md b/src/connections/destinations/catalog/quantcast/index.md
index 19561e625e..5e70c002ab 100644
--- a/src/connections/destinations/catalog/quantcast/index.md
+++ b/src/connections/destinations/catalog/quantcast/index.md
@@ -15,10 +15,6 @@ Quantcast supports the `identify` and `track` methods on our API.
Note: For Quantcast to load you must call our page method. There is a call to page in your JavaScript snippet by default, so as long as you don't remove it Quantcast will load whenever your snippet loads!
-## React Native set up
-
-{% include content/react-dest.md only="android" %}
-
### Page
When you call `.page()`, we will automatically pass the labels. [See below for details](#labels).
diff --git a/src/connections/destinations/catalog/taplytics/index.md b/src/connections/destinations/catalog/taplytics/index.md
index 2cc13b2771..e818c003f1 100644
--- a/src/connections/destinations/catalog/taplytics/index.md
+++ b/src/connections/destinations/catalog/taplytics/index.md
@@ -23,10 +23,6 @@ To get up and running with Taplytics on Android, there a couple of steps we will
To enable its full functionality (like Push Notifications, Deep linking), there are a couple of extra steps that you have to take care of in your Android app. [This document explains how to set up Push Notifications](https://docs.taplytics.com/docs/guides-push-notifications) and [ths one explains how to set up deep linking](https://support.taplytics.com/hc/en-us/articles/360004176632-Deep-Linking-Guide-).
-### React Native set up
-
-{% include content/react-dest.md only="ios" %}
-
## Identify
Use [Identify](/docs/connections/sources/catalog/libraries/mobile/ios/#identify) to track user specific attributes. It equivalent to tracking [user attributes](https://docs.taplytics.com/docs/guides-user-insights) on Taplytics. Taplytics supports traits supported by Segment as well as custom traits. If you set traits.id, we set that as the Unique ID for that user.
diff --git a/src/connections/destinations/catalog/tapstream/index.md b/src/connections/destinations/catalog/tapstream/index.md
index b272135956..201e5391f3 100644
--- a/src/connections/destinations/catalog/tapstream/index.md
+++ b/src/connections/destinations/catalog/tapstream/index.md
@@ -3,5 +3,4 @@ title: 'Tapstream Destination'
hidden: true
id: 54521fdb25e721e32a72eef7
---
-
+
diff --git a/src/protocols/tracking-plan/create.md b/src/protocols/tracking-plan/create.md
index b628e83c0c..8244da80ec 100644
--- a/src/protocols/tracking-plan/create.md
+++ b/src/protocols/tracking-plan/create.md
@@ -174,6 +174,9 @@ To edit the common JSON schema using the Public API, you'll need to add your new
> info "Specifying data type"
> Property or trait data type should adhere to the [data types defined by JSON schema](https://json-schema.org/understanding-json-schema/reference/type.html){:target="_blank”}. Data type names must be lower-cased as specified in JSON schema. Datetime properties should be represented as a `string` type with [`format` keyword](https://json-schema.org/understanding-json-schema/reference/string.html#format){:target="_blank”} (for example: "format": "date-time").
+> info "Blocking data"
+> JSON schema violation event blocking is **only** supported in cloud-mode Destinations. See [the Customize your schema controls docs](/docs/protocols/enforce/schema-configuration/) for more information on blocking data.
+
### Extend the Tracking Plan
Some customers prefer to manage the Tracking Plan with outside tools and resources. See the [APIs and extensions](/docs/protocols/apis-and-extensions/) section to learn more.
diff --git a/src/segment-app/iam/roles.md b/src/segment-app/iam/roles.md
index 3ab052a8f9..966a054cc9 100644
--- a/src/segment-app/iam/roles.md
+++ b/src/segment-app/iam/roles.md
@@ -67,10 +67,10 @@ The following roles are only available to Segment Business Tier accounts.
* **Scope:** Grants access to *all* warehouses.
#### Entities Admin
-Full CRUD (create, read, access, and delete) access to all Entities within a workspace. You can also grant or revoke user permissions.
+Full edit and view access to all entity models and connection details.
#### Entities Read-only
-Read-only access to all Entities models and destinations in a workspace.
+Read-only access, with the ability to view entity models.
## PII Access
diff --git a/src/engage/images/large_trait_csv.png b/src/unify/images/large_trait_csv.png
similarity index 100%
rename from src/engage/images/large_trait_csv.png
rename to src/unify/images/large_trait_csv.png
diff --git a/src/engage/images/trait_overview.png b/src/unify/images/trait_overview.png
similarity index 100%
rename from src/engage/images/trait_overview.png
rename to src/unify/images/trait_overview.png
diff --git a/src/unify/linked-profiles/linked-events.md b/src/unify/linked-profiles/linked-events.md
index 423f6a315e..542abb863d 100644
--- a/src/unify/linked-profiles/linked-events.md
+++ b/src/unify/linked-profiles/linked-events.md
@@ -39,10 +39,8 @@ The following Segment access [roles](/docs/segment-app/iam/roles/) apply to Link
**Entities Read-only Access**: Entities Read-only users have the ability to view entity models.
-To create models and enrich events in destinations, you need the following roles:
-- `Workspace Owner` and `Entities Admin`
+To create models and enrich events in destinations, you need to be a `Workspace Owner` or have the following roles:
-OR:
- `Unify and Engage Admin`
- `Entities Admin`
- `Source Admin`