This is the only Firebase Analytics package for React Native that has universal platform support (iOS, Android, Web, and Electron).
expo-firebase-analytics enables the use of native Google Analytics for Firebase. Google Analytics for Firebase is a free app measurement solution that provides insight on app usage and user engagement.
Learn more in the official Firebase Docs.
The use of Native Firebase Analytics requires that the google-services configuration is bundled and linked into your app. Since the standard Expo client loads projects on demand, it does not have the google-services configuration linked into its app-bundle.
Instead, the standard Expo client relies on a JavaScript-based implementation of Firebase Analytics to log events. This means that certain native life-cycle events are not recorded in the standard client, but you can still use logEvent to record events.
You may want to use Firebase Analytics in Expo client to verify that you are logging events at the time you intend to and with the data that you want to attach without having to do a standalone app build. To set this up, ensure that the Firebase web configuration is set in app.json and that measurementId exists in your firebase config. If measurementId doesn't exist, then you need to enable or update Google Analytics in your Firebase project.
This limitation only applies to the Expo client in the App/Play store, standalone builds, custom clients & bare apps support the full native Firebase Analytics experience.
To get extra features like audiences, campaign attribution, and some user properties, such as Age and Interests, you will need to include AdSupport. This is currently only possible in the Bare Workflow and not enabled by default because Apple & Google are strict with allowing apps to use this library.
To enable the AdSupport framework:
In your Xcode project, select your project's target
Select the General tab for your target
Expand the Linked Frameworks and Libraries section
Logs an app event. The event can have up to 25 parameters. Events with the same name must have
the same parameters. Up to 500 event names are supported. Using predefined events and/or
parameters is recommended for optimal reporting.
The following event names are reserved and cannot be used:
The name of the event. Should contain 1 to 40 alphanumeric characters or underscores. The name must start with an alphabetic character. Some event names are reserved. The firebase_, google_, and ga_ prefixes are reserved and should not be used. Note that event names are case-sensitive and that logging two events whose names differ only in case will result in two distinct events.
properties
Object
The dictionary of event parameters. Passing undefined indicates that the event has no parameters. Parameter names can be up to 40 characters long and must start with an alphabetic character and contain only alphanumeric characters and underscores. Only String and Number (signed 64-bit integer and 64-bit floating-point number) parameter types are supported. String parameter values can be up to 100 characters long. The firebase_, google_, and ga_ prefixes are reserved and should not be used for parameter names.
Sets the current screen name, which specifies the current visual context in your app. This helps
identify the areas in your app where users spend their time and how they interact with your app.
The name of the current screen. Should contain 1 to 100 characters. Set to undefined to clear the current screen name.
screenClassOverride
string
The name of the screen class. Should contain 1 to 100 characters. By default this is the class name of the current screen (UIViewController on iOS). Set to undefined to revert to the default class name.
The user ID to ascribe to the user of this app on this device, which must be non-empty and no more than 256 characters long. Setting userID to null removes the user ID.
Sets a user property to a given value. Up to 25 user property names are supported. Once set,
user property values persist throughout the app life-cycle and across sessions.
The following user property names are reserved and cannot be used:
The name of the user property to set. Should contain 1 to 24 alphanumeric characters or underscores and must start with an alphabetic character. The firebase_, google_, and ga_ prefixes are reserved and should not be used for user property names.
value
string | null
The value of the user property. Values can be up to 36 characters long. Setting the value to null removes the user property.
Enables or disables the warning and log messages when using Firebase Analytics on the Expo client.
Firebase Analytics is not available on the Expo client and therefore logs the requests to the console
for development purposes. To test Firebase Analytics, create a stand-alone build or custom client.
This function can be called to disable the warning and log messages when using Firebase Analytics
on the Expo client.
This option is only available on the standard Expo client. When using a standalone build, the bare workflow or web, use the natively available options.
You can gain deeper insight into what works and what doesn't by using the logEvent property. Also it's just a lot of fun to see that people actually use the features you work hard on! 😍
/*
* Say we are in a tinder clone, and a user presses the card to view more
* information on a user. We should track this event so we can see if people
* are even using it.
*
* If lots of users are opening the card then swiping through photos, just
* to dismiss again, then we should consider making it possible to look
* through photos without having to enter the profile.
*/onPressProfileButton=uid=>{Analytics.logEvent('ExpandProfile',{/*
* We want to know if the user came from from the swipe card as
* opposed to from chat or a deep link.
*/
sender:'card',/*
* This may be too specific and not very useful, but maybe down the line * we could investigate why a certain user is more popular than others.
*/
user: uid,/*
* We can use this information later to compare against other events.
*/
screen:'profile',
purpose:'Viewing more info on a user',});};
importReactfrom'react';// Import Navigationimport{ createBottomTabNavigator }from'react-navigation';// Import Firebaseimport*asAnalyticsfrom'expo-firebase-analytics';// Import some screensimportHomeScreenfrom'../screens/HomeScreen';importProfileScreenfrom'../screens/ProfileScreen';// Create a generic NavigatorconstAppNavigator=createBottomTabNavigator({// The name `Profile` or `Home` are what will appear in Firebase Analytics.Profile:ProfileScreen,Home:HomeScreen,});// Get the current screen from the navigation statefunctiongetActiveRouteName(navigationState){if(!navigationState)returnnull;const route = navigationState.routes[navigationState.index];// Parse the nested navigatorsif(route.routes)returngetActiveRouteName(route);return route.routeName;}exportdefault()=>(<AppNavigator
onNavigationStateChange={(prevState, currentState)=>{const currentScreen =getActiveRouteName(currentState);const prevScreen =getActiveRouteName(prevState);if(prevScreen !== currentScreen){// Update Firebase with the name of your screenAnalytics.setCurrentScreen(currentScreen);}}}/>);