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