Skip to content

Commit 83ad413

Browse files
authored
Merge pull request #5700 from segmentio/ashton-huxtable-patch-2
Add info about using classic destination with plugins
2 parents d4335b1 + eb88fe9 commit 83ad413

File tree

1 file changed

+4
-0
lines changed
  • src/connections/sources/catalog/libraries/mobile/react-native/destination-plugins

1 file changed

+4
-0
lines changed

src/connections/sources/catalog/libraries/mobile/react-native/destination-plugins/index.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -84,6 +84,10 @@ plugins:
8484

8585
Analytics React Native uses its timeline/plugin architecture to support sending data to bundled SDKs when a Cloud Mode connection is not possible. Destination Plugins are similar to traditional Device Mode integrations available in Analytics React Native 1.x in that Segment makes calls directly to the destination tool’s API from the device. However, Destination Plugins are more customizable, giving you the ability to control and enrich your data at a much more granular level on the device itself.
8686

87+
> info "Choosing the right destination"
88+
> Segment built device mode destination [plugins](/docs/connections/sources/catalog/libraries/mobile/react-native/react-native-plugin-architecture/){:target='_blank’} to be used with the classic/legacy destinations, not Actions destinations. The exception to this is the Amplitude plugin. The Amplitude plugin is a session plugin meant to be used with Amplitude Actions. If a classic/legacy destination is in maintenance mode, Segment continues to make updates pertaining to the mobile plugins, but not the server or web components.
89+
> If you run into any issues setting up your destination, reach out to support.
90+
8791
## Device-mode Vs. Cloud-Mode
8892
Analytics React Native allows you to choose how you send data to Segment and your connected destinations from your app. There are two ways to send data:
8993

0 commit comments

Comments
 (0)