I created a android app using firebase analytics,i want one brand can only see its own data and cannot see other brands,how i manage the firebase analytics member in the firebase analytics console
Related
I have an iOS which I have implemented analytics on - I have created events for each time the screen of the app is changed.
When I view Analytics in Firebase Console I can see that they have been picked up and registered.
This issue comes when then trying to use BigQuery.
I used the app on 25/2/22, the events appeared in Firebase Console and then in BigQuery.
However, I then used the app on 1/3/22, the events have appeared in Firebase Console but not in BigQuery.
My question is how do I make sure that the data collected that I can see in Firebase Control is transferred to BigQuery so that I can query the data?
The firebase console under Settings -> Integrations -> Google Analytics has a Data Sharing section with a bunch of check boxes, one of which is:
Share Analytics data with all Firebase features (Recommended):
Including Crashlytics, Predictions, A/B Testing, Remote Config, Cloud
Messaging, and In-App Messaging
The word "Share" is confusing to me. Does this mean there's an underlying set of data that is collected by default and unless I check this box, these other firebase features won't have access to that data?
If I don't select this option will data still be collected? Will data be available to any part of my system?
If you disable Share Analytics data with all Firebase features then the analytics data in your Firebase project is only available within the analytics panel, and won't be used in the other Firebase products.
So if you uncheck the box, you won't be able to (for example) send targeted notifications (using Cloud Messaging or In-App Messaging) based on analytics data, or run predictions of future user behavior. But you will be able to see the analytics data in the Firebase console, and you can allow the data to be exported to BigQuery.
Firebase Crashlytics dashboard shows "Crash-free statistics". How to get/enable Crash-Free Users Statistics/Metrics in Firebase ?
Crash-Free User metrics helps monitor the health of your app releases and the effectiveness of recent improvements to your app. Monitoring your crash free users statistic over time allows you to see changes in stability easily. Firebase calculates this metric using Google Analytics for Firebase data. In order to populate the chart in your Crashlytics dashboard must include the Google Analytics for Firebase SDK. Once populated, you can see the percentage of users who did not experience a crash in your app over the selected timeframe and filter by build. You can see the same data in the latest release section of the Google Analytics for Firebase dashboard. To get started, add Google Analytics for Firebase to your iOS or Android app.
I am using node js Firebase SDK.
How can I access analytics data from Firebase, with the help of Firebase admin API.
Update: there is now an API to get the Analytics reports data. See my answer here: Is there any api for dashboard analytics data?
You can also:
download the analytics report data from the Firebase console by clicking the Download CSV option from the ⠇ overflow menu. Also see my answer here: Is it possible to embed Firebase Analytics data from my apps into a webpage?
connect Firebase Analytics to BigQuery to export the raw events, and query them in BigQuery, or visualize them with Data Studio.
I set up Firebase Analytics and Firebase Crashlytics for my project.
Can I view Analytics events and user properties in Firebase Crashlytics reports (including automatically collected events)?
Should I log events for Analytics and Crashlytics independently?
Should I set user properties for Analytics and customs keys for Crashlytics independently?
It looks like duplication.
EDIT: Crashlytics is now able to show Analytics events.
ORIGINAL ANSWER:
Firebase Crash Reporting and Firebase Crashlytics are fully independent products, so you will have to deal with them separately.
Crashlytics currently is not able to show Analytics events in crash reports. That is something the team would like to add in the future.