Security News
GitHub Removes Malicious Pull Requests Targeting Open Source Repositories
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.
@kitten-team/react-native-google-analytics-bridge
Advanced tools
React Native bridge for using native Google Analytics libraries on iOS and Android
Google Analytics Bridge is built to provide an easy interface to the native Google Analytics libraries on both iOS and Android.
The key difference with the native bridge is that you get a lot of the metadata handled automatically by the Google Analytics native library. This will include the device UUID, device model, viewport size, OS version etc.
You will only have to send in a few parameteres when tracking, e.g:
import { GoogleAnalyticsTracker } from "react-native-google-analytics-bridge";
let tracker = new GoogleAnalyticsTracker("UA-12345-1");
tracker.trackScreenView("Home");
tracker.trackEvent("testcategory", "testaction");
You can specify googlePlayServicesVersion in "android/gradle.properties". Otherwise, it will take default version
e.g.
googlePlayServicesVersion=11.8.0
This is NOT (normally) an error with this library. Please read this guide on how to set up your Google Analytics account/property for mobile analytics.
Here I have mentioned the required steps to resolve the issues regarding the build failures, when you got updated your android studio please check the following doc to clear the issues
0.40
use version 5.0.0
(and up) of this module.0.40
use version 4.0.3
.Install with npm: npm install --save react-native-google-analytics-bridge
Or, install with yarn: yarn add react-native-google-analytics-bridge
Either way, then link with: react-native link react-native-google-analytics-bridge
If it doesn't work immediately after this, consult the manual installation guide. Both Android and iOS has a couple of prerequisite SDKs linked and installed.
Important: Does this library work with Expo? We have to sort of invert the question a bit, because it should be: does Expo work with other libraries? And the answer is no:
The most limiting thing about Expo is that you can’t add in your own native modules without
detach
ing and using ExpoKit.
This includes using create-react-native-app
which also makes use of Expo.
// You have access to three classes in this module:
import {
GoogleAnalyticsTracker,
GoogleTagManager,
GoogleAnalyticsSettings
} from "react-native-google-analytics-bridge";
// The tracker must be constructed, and you can have multiple:
let tracker1 = new GoogleAnalyticsTracker("UA-12345-1");
let tracker2 = new GoogleAnalyticsTracker("UA-12345-2");
tracker1.trackScreenView("Home");
tracker1.trackEvent("Customer", "New");
// The GoogleAnalyticsSettings is static, and settings are applied across all trackers:
GoogleAnalyticsSettings.setDispatchInterval(30);
// Setting `dryRun` to `true` lets you test tracking without sending data to GA
GoogleAnalyticsSettings.setDryRun(true);
// GoogleTagManager is also static, and works only with one container. All functions here are Promises:
GoogleTagManager.openContainerWithId("GT-NZT48")
.then(() => {
return GoogleTagManager.stringForKey("pack");
})
.then(pack => {
console.log("Pack: ", pack);
})
.catch(err => {
console.log(err);
});
In some scenarios it might be helpful to provide an opened GTM container to the bridge. Some possible scenarios where this could be helpful:
This will require that you are familiar with the native api for GTM on whatever platforms you want to support. Generally the process is to load your container at startup, and hold the creation of the react native bridge until the container is loaded. On iOS you can then initialize an RCTGoogleTagManagerBridge and set the container property. On Android the process is similar, but you will need to supply the ContainerHolder to the GoogleAnalyticsBridgePackage instead.
import { GoogleAnalyticsTracker } from "react-native-google-analytics-bridge";
let tracker = new GoogleAnalyticsTracker("UA-12345-1");
Google Analytics expects dimensions to be tracked by indices, and not field names. To simplify this, you can construct a tracker with a customDimensionsFieldsIndexMap. With this, you can map field names to indices, e.g:
let tracker2 = new GoogleAnalyticsTracker("UA-12345-3", { test: 1 });
tracker2.trackScreenViewWithCustomDimensionValues("Home", { test: "Beta" });
Here the underlying logic will transform the custom dimension, so what ends up being sent to GA is { 1: 'Beta' }
.
This should make it easier to use custom dimensions. If you do not provide a customDimensionsFieldsIndexMap, the custom dimensions are passed through untouched.
Important: Calling this will also set the "current view" for other calls. So events tracked will be tagged as having occured on the current view, Home
in this example. This means it is important to track navigation, especially if events can fire on different views.
See the Google Analytics docs for more info
tracker.trackScreenView("Home");
See the Google Analytics docs for more info.
tracker.trackEvent("testcategory", "testaction");
// or
tracker.trackEvent("testcategory", "testaction", {
label: "v1.0.3",
value: 22
});
See the Google Analytics docs for more info.
tracker.trackTiming("testcategory", 13000, { name: "LoadList" }); // name option is required
// or
tracker.trackTiming("testcategory", 13000, {
name: "loadList",
label: "v1.0.3"
});
See the Google Analytics docs for more info.
tracker.trackPurchaseEvent(
{
id: "P12345",
name: "Android Warhol T-Shirt",
category: "Apparel/T-Shirts",
brand: "Google",
variant: "Black",
price: 29.2,
quantity: 1,
couponCode: "APPARELSALE"
},
{
id: "T12345",
affiliation: "Google Store - Online",
revenue: 37.39,
tax: 2.85,
shipping: 5.34,
couponCode: "SUMMER2013"
},
"Ecommerce",
"Purchase"
);
same as trackPurchaseEvent but instead of one product you can provide an Array of products
tracker.trackMultiProductsPurchaseEventWithCustomDimensionValues(
[
{
id: "P12345",
name: "Android Warhol T-Shirt",
category: "Apparel/T-Shirts",
brand: "Google",
variant: "Black",
price: 29.2,
quantity: 1,
couponCode: "APPARELSALE"
},
{
id: "P54321",
name: "IOS T-Shirt",
category: "Apparel/T-Shirts",
brand: "Apple",
variant: "Black",
price: 10.1,
quantity: 1,
couponCode: "APPARELSALE"
}
],
{
id: "T12345",
affiliation: "Store - Online",
revenue: 52.5,
tax: 7.86,
shipping: 5.34,
couponCode: "SUMMER2013"
},
"Ecommerce",
"Purchase",
{ "1": "premium", "5": "foo" }
);
See the Google Analytics docs for more info.
try {
...
} catch(error) {
tracker.trackException(error.message, false);
}
See the Google Analytics docs for more info.
tracker.trackSocialInteraction("Twitter", "Post");
Tracks a screen view with one or more customDimensionValues. See the Google Analytics docs for more info.
tracker.trackScreenViewWithCustomDimensionValues("Home", {
"1": "premium",
"5": "foo"
});
Tracks an event with one or more customDimensionValues. See the Google Analytics docs for more info.
tracker.trackEventWithCustomDimensionValues(
"testcategory",
"testaction",
{ label: "v1.0.3", value: 22 },
{ "1": "premium", "5": "foo" }
);
Tracks an event with one or more customDimensionValues and one or more customMetricValues. See the Google Analytics docs for more info.
tracker.trackEventWithCustomDimensionAndMetricValues('testcategory', 'testaction', {label: 'v1.0.3', value: 22}, {'1':'premium', '5':'foo'}, , {'1': 3, '5': 4});
See the Google Analytics for more info.
tracker.setUser("12345678");
See the Google Analytics for more info.
tracker.setClient("35009a79-1a05-49d7-b876-2b884d0f825b");
This function lets you get the client id to be used for different purpose for logging etc.
tracker.clientId().then(clientId => console.log("Client id is: ", clientId));
See the Google Analytics for more info.
tracker.createNewSession("HomeScreen");
true
.Also called advertising identifier collection, and is used for advertising features.
Important: For iOS you can only use this method if you have done the optional step 6 from the installation guide. Only enable this (and link the appropriate libraries) if you plan to use advertising features in your app, or else your app may get rejected from the AppStore.
See the Google Analytics for more info.
tracker.allowIDFA(true);
Sets if uncaught exceptions should be tracked. This is enabled by default.
tracker.setTrackUncaughtExceptions(true);
Sets if AnonymizeIp is enabled. This is disabled by default. If enabled the last octet of the IP address will be removed.
tracker.setAnonymizeIp(true);
Overrides the app name logged in Google Analytics. The Bundle name is used by default. Note: This has to be set each time the App starts.
tracker.setAppName("someAppName");
Sets tracker sampling rate.
tracker.setSamplingRate(50);
Sets tracker currency property, see Currency Codes.
tracker.setCurrency("EUR");
This function lets you manually dispatch all hits which are queued. Use this function sparingly, as it will normally happen automatically as a batch.
tracker.dispatch().then(done => console.log("Dispatch is done: ", done));
The same as dispatch()
, but also gives you the ability to time out the Promise in case dispatch takes too long.
tracker
.dispatchWithTimeout(10000)
.then(done => console.log("Dispatch is done: ", done));
Settings are applied across all trackers.
dryRun
flag should be enabled or not.When enabled the native library prevents any data from being sent to Google Analytics. This allows you to test or debug the implementation, without your test data appearing in your Google Analytics reports.
GoogleAnalyticsSettings.setDryRun(true);
Events, screen views, etc, are sent in batches to your tracker. This function allows you to configure how often (in seconds) the batches are sent to your tracker. Recommended to keep this around 20-120 seconds to preserve battery and network traffic. This is set to 20 seconds by default.
GoogleAnalyticsSettings.setDispatchInterval(30);
Sets if OptOut is active and disables Google Analytics. This is disabled by default. Note: This has to be set each time the App starts.
GoogleAnalyticsSettings.setOptOut(true);
import { GoogleTagManager } from "react-native-google-analytics-bridge";
GoogleTagManager.openContainerWithId("GT-NZT48")
.then(() => GoogleTagManager.stringForKey("pack"))
.then(str => console.log("Pack: ", str));
Can only be used with one container. All methods returns a Promise
.
Important: Call once to open the container for all subsequent static calls.
GoogleTagManager.openContainerWithId('GT-NZT48')
.then((..) => ..)
Retrieves a string with the given key from the opened container.
GoogleTagManager.stringForKey("key").then(val => console.log(val));
Retrieves a boolean value with the given key from the opened container.
GoogleTagManager.boolForKey("key").then(val => console.log(val));
Retrieves a number with the given key from the opened container.
GoogleTagManager.doubleForKey("key").then(val => console.log(val));
Push a DataLayer event for Google Analytics through Google Tag Manager.
GoogleTagManager.pushDataLayerEvent({
event: "eventName",
pageId: "/home"
}).then(success => console.log(success));
Sets logger to verbose, default is warning
GoogleTagManager.setVerboseLoggingEnabled(true);
FAQs
React Native bridge for using native Google Analytics libraries on iOS and Android
The npm package @kitten-team/react-native-google-analytics-bridge receives a total of 0 weekly downloads. As such, @kitten-team/react-native-google-analytics-bridge popularity was classified as not popular.
We found that @kitten-team/react-native-google-analytics-bridge demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 6 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
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.
Security News
RubyGems.org has added a new "maintainer" role that allows for publishing new versions of gems. This new permission type is aimed at improving security for gem owners and the service overall.
Security News
Node.js will be enforcing stricter semver-major PR policies a month before major releases to enhance stability and ensure reliable release candidates.