Security News
CISA Brings KEV Data to GitHub
CISA's KEV data is now on GitHub, offering easier access, API integration, commit history tracking, and automated updates for security teams and researchers.
@sonder/analytics-react-native
Advanced tools
The hassle-free way to add analytics to your React-Native app.
The hassle-free way to add analytics to your React-Native app.
./gradlew wrapper --gradle-version=4.4
in your android
foldercom.android.tools.build:gradle
to 3.1.4
in your android/build.gradle
fileAnalytics
$ yarn add @segment/analytics-react-native
$ yarn react-native link
See the API docs for more details.
import analytics from '@segment/analytics-react-native'
import Mixpanel from '@segment/analytics-react-native-mixpanel'
import GoogleAnalytics from '@segment/analytics-react-native-google-analytics'
analytics
.setup('writeKey', {
using: [Mixpanel, GoogleAnalytics],
recordScreenViews: true,
trackAppLifecycleEvents: true,
trackAttributionData: true,
android: {
flushInterval: 60,
collectDeviceId: true
},
ios: {
trackAdvertising: true,
trackDeepLinks: true
}
})
.then(() =>
console.log('Analytics is ready')
)
.catch(err =>
console.error('Something went wrong', err)
)
analytics.track('Pizza Eaten')
analytics.screen('Home')
There are two ways to send data to your analytics services through this library:
Note: Refer to the specific destination’s docs to see if your tool must be bundled in the app or sent server-side.
When an destination’s SDK is not packaged, but it is enabled via your dashboard, the request goes through the Segment REST API, and is routed to the service’s server-side API as described here.
By default, our @segment/analytics-react-native
packages does not contain any device-based destinations.
We recommend using device-based destinations on a need-to-use basis to reduce the size of your application, and avoid running into the dreaded 65k method limit on Android.
If you would like to package device-based destinations, first search for the dependency you need using the list below.
You'll need to run react-native link
and add it in the .using()
configuration method. Example using Google Analytics :
$ yarn add @segment/analytics-react-native-google-analytics
$ yarn react-native link
In your code :
import analytics from '@segment/analytics-react-native'
import GoogleAnalytics from '@segment/analytics-react-native-google-analytics'
await analytics.setup('writeKey', {
using: [GoogleAnalytics]
})
All integrations have the same version as
@segment/analytics-react-native
Name | iOS | Android | npm package |
---|---|---|---|
Adjust | :white_check_mark: | :white_check_mark: | @segment/analytics-react-native-adjust |
Amplitude | :white_check_mark: | :white_check_mark: | @segment/analytics-react-native-amplitude |
Appboy | :white_check_mark: | :white_check_mark: | @segment/analytics-react-native-appboy |
AppsFlyer | :white_check_mark: | :white_check_mark: | @segment/analytics-react-native-appsflyer |
Branch | :white_check_mark: | :white_check_mark: | @segment/analytics-react-native-branch |
Bugsnag | :white_check_mark: | :white_check_mark: | @segment/analytics-react-native-bugsnag |
ComScore | :white_check_mark: | :x: | @segment/analytics-react-native-comscore-ios |
Countly | :white_check_mark: | :white_check_mark: | @segment/analytics-react-native-countly |
Crittercism | :white_check_mark: | :white_check_mark: | @segment/analytics-react-native-crittercism |
Facebook App Events | :white_check_mark: | :x: | @segment/analytics-react-native-facebook-app-events-ios |
Firebase | :white_check_mark: | :white_check_mark: | @segment/analytics-react-native-firebase |
Flurry | :white_check_mark: | :white_check_mark: | @segment/analytics-react-native-flurry |
Google Analytics | :white_check_mark: | :white_check_mark: | @segment/analytics-react-native-google-analytics |
Intercom | :white_check_mark: | :white_check_mark: | @segment/analytics-react-native-intercom |
Localytics | :white_check_mark: | :white_check_mark: | @segment/analytics-react-native-localytics |
Mixpanel | :white_check_mark: | :white_check_mark: | @segment/analytics-react-native-mixpanel |
Quantcast | :x: | :white_check_mark: | @segment/analytics-react-native-quantcast-android |
Taplytics | :white_check_mark: | :x: | @segment/analytics-react-native-taplytics-ios |
Tapstream | :x: | :white_check_mark: | @segment/analytics-react-native-tapstream-android |
We highly recommend using Cocoapods.
However, if you cannot use Cocoapods, you can manually install our dynamic framework allowing you to send data to Segment and on to enabled cloud-mode destinations. We do not support sending data to bundled, device-mode integrations outside of Cocoapods.
Here are the steps for installing manually:
Copy items if needed
.
General
tab for your project, search for Embedded Binaries
and add the Analytics.framework
.
Please note, if you are choosing to not use a dependency manager, you must keep files up-to-date with regularly scheduled, manual updates.
Check that ios/Podfile
doesn't exist
cd ios
pod init
Open Podfile
Edit your app target
to have these pod
declarations and the Add new pods below this line
comment :
target 'MyReactNativeApp' do
pod 'React', :path => '../node_modules/react-native'
pod 'yoga', :path => '../node_modules/react-native/ReactCommon/yoga'
# Add new pods below this line
end
pod install
If you're getting a Failed to load [...] native module
error, it means that some native code hasn't been injected to your native project.
If you're using Cocoapods, check that your ios/Podfile
file contains the right pods :
Failed to load Analytics native module
, look for the core native module:
pod 'RNAnalytics', :path => '../node_modules/@segment/analytics-react-native'
Failed to load [...] integration native module
, look for the integration native module, example with Google Analytics:
pod 'RNAnalyticsIntegration-Google-Analytics', :path => '../node_modules/@segment/analytics-react-native-google-analytics'
Also check that your Podfile
is synchronized with your workspace, run pod install
in your ios
folder.
If you're not using Cocoapods please check that you followed the iOS support without CocoaPods instructions carefully.
Check that android/app/src/main/.../MainApplication.java
contains a reference to the native module:
Failed to load Analytics native module
, look for the core native module:
import com.segment.analytics.reactnative.core.RNAnalyticsPackage;
// ...
@Override
protected List<ReactPackage> getPackages() {
return Arrays.<ReactPackage>asList(
new MainReactPackage(),
// ...
new RNAnalyticsPackage()
);
}
Failed to load [...] integration native module
, look for the integration native module, example with Google Analytics:
import com.segment.analytics.reactnative.integration.google.analytics.RNAnalyticsIntegration_Google_AnalyticsPackage;
// ...
@Override
protected List<ReactPackage> getPackages() {
return Arrays.<ReactPackage>asList(
new MainReactPackage(),
// ...
new RNAnalyticsIntegration_Google_AnalyticsPackage()
);
}
FAQs
The hassle-free way to add analytics to your React-Native app.
The npm package @sonder/analytics-react-native receives a total of 0 weekly downloads. As such, @sonder/analytics-react-native popularity was classified as not popular.
We found that @sonder/analytics-react-native demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
CISA's KEV data is now on GitHub, offering easier access, API integration, commit history tracking, and automated updates for security teams and researchers.
Security News
Opengrep forks Semgrep to preserve open source SAST in response to controversial licensing changes.
Security News
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.