Issue
In Firestore Analytics I am unable to re-use custom unique text event parameters created.
Attempted Solution
Per the Firebase guidelines 10 textual custom event parameters may be used. In the Firebase console it specifies these parameters can be unique: You can have up to 10 unique text parameters..
For my event named Archived I have defined 7 custom text parameters as seen below: content_type, creator, feed_type, item_id, item_name, quality_score, and timestamp.
I am unable to re-use the same 7 custom text parameters in the event named SAVED. These event parameters should not be counted as unique since they are exactly as defined in the first event ARCHIVED.
The documentation does not imply that you should be able to re-use them. If you could, then you could simply make 10 generic parameters and use them for every event. I do agree that it's very limiting, but they are trying to push users to connect their Firebase instance with BigQuery.
I suggest that you do just this and analyse your custom parameters from there as I am unaware of any way to bypass the 10 parameter limit. For us there has been no downside to connecting with BigQuery, even with millions of users it has cost us nothing/close to nothing.
Related
We've developed a Flutter mobile App and we've firebase account.
For our App we need to add Firebase analytics for the App Events such as button clicks.
We've integrated the Analytics SDK in the Mobile App and created an Events with custom parameters and we can see the count of Events and Users counts in the Firebase Excel/CSV report but we're unable to see the custom parameters in the report.
Our requirement is to see the Events analytics reports with the custom parameters in CSV report without linking the Bigquery. Please advise with the steps.
Thanks!
Custom parameters are included in the download as a CSV report. You can actually replicate this using the Firebase demo project. Go to Analytics > Events > click on level_complete event. In the level_complete page, you will see the level_name parameter card and its values. When you download this as CSV, you can see the list of level_name values in the file with metrics such as the number of times it has been logged and number of users who logged it.
Please note that when you register custom parameters, a data card for each parameter is added to the related event-detail report. However, it may take up to 24 hours for the data card to appear. During this 24-hour period, you may see (not set) appear as a parameter value. Once that initial 24-hour period has passed, you will see the expected parameter values from that point forward. See this documentation for your reference.
For seeing parameters in firebase dashboard as well as in csv report first check if the event is triggered in DebugView and then you need to define some custom definitions.
In new custom definition choose from your previously given parameters. Normally it takes several hours to get the parameters in event parameter.
The parameter will be shown in Dashboard as event parameter after 24 hours and you can download it as CSV/pdf
Also for analyze data you can use Google Data Studio which imports your data from analytics and helps to generate different types of graphical reports according to your need.
I am using Google Analytics for years for my iOS apps and was truly satisfied with it. For my regret Google is sunsetting Google Analytics later this year so I am switching to Firebase API so I can keep tracking my apps. I already done most of the integration work and can see the events appearing in Firebase console. However, I can't see custom parameter values but only event count.
For example, sending event named add_book and adding parameter named isbn with value of 1234, I will be able to see in the console only the number of times that add_book arrived and also that it contains an isbn parameter. However, it seems there is no way to view the value (i.e. 1234) of the isbn parameter. I registered the isbn parameter for the add_book event as required. Am I missing something?
Does having the full functionality of the sunsetting Google Analytics (including advanced filtering + regex filters, etc.), means I should use both Firebase Analytics and BigQuery together?
By the way, I linked Firebase Analytics with BigQuery and exported the data as suggested by Firebase Analytics, but I can't see any Analytics tables yet in BigQuery. Do I need to allow several hours before I can view the exported data?
As of March 2019, Firebase Analytics is not so easy to use or test when setting it up (in comparison to Google Analytics). The main steps for setting up event parameters are:
Send your events with their event parameters. Send at least 80-90 events of one type, otherwise the parameters will appear as zero or "not set", until you reach 80 individual events.
The events will not display in the website until after one day. So wait for 24 hours.
When the events appear on the website, you must register their event parameters, with the '3 dots' menu -> "Edit Parameter Reporting" - Like this:
Then:
(Image credit: Firebase Analytics custom events params and Firebase Analytics. Can not add custom parameter to event )
After registering the event parameters, you must wait another 24 hours to see the parameters displayed on the website.
More info:
https://www.reddit.com/r/androiddev/comments/9zbvk4/alternative_to_google_analytics_not_firebase/
https://www.tatvic.com/blog/firebase-analytics-reporting-tips-overcome-limitations-favorite-mobile-app-analytics-tool-google/
In your event overview from Firebase Console you can enable parameter reporting for individual events. The option is found in the 3 dot overflow menu.
You can do that for up to 10 unique text parameters and 40 unique numeric parameters.
Beyond those limits or for more control BigQuery is the way to go. And yes you need to wait for your first data in BigQuery. They populate a new table with one days data every day once.
We have a project with analytics enabled which tracks custom events.
Recently we needed to report on a specific parameter on these events but found the parameter was not included in the parameter reporting options, we have enabled this but the previous events over the past couple of months do not include this parameter now.
Is there any way to get the full data of events tracked to retrieve the data of this specific parameter before it was included in the parameter reporting options?
It is not possible, custom parameter reports are populated after you add them on your Firebase console.
When you register custom parameters, a data card for each parameter is added to the related event-detail report. However, it may take up to 24 hours for the data card to appear.
We have some exciting new features coming soon to Google Analytics for Firebase, but we’ve noticed some issues with your project’s configuration which will prevent us from making those features available to you.
Our records indicate that you have a Firebase project (****513) that will be affected.
In the past, we’ve enforced configuration limits independently on each of the apps in your Firebase project. However, going forward, these limits will be enforced on a project-wide basis. As such, we need your help in making the necessary and appropriate changes to your project’s configuration to pave the way for access to our coming upgrades.
Specifically, we need you to make the following changes by April 25, 2018:
Reduce the number of distinct registered text parameters (in name, type) defined in your project to 20.
What's the number of distinct registered text parameters? because Firebase just gives 10 text parameter quota per app!
So what I undrestand from searching that reporting is moving from app-level to project-level, as they said In the past, we’ve enforced configuration limits independently on each of the apps in your Firebase project. However, going forward, these limits will be enforced on a project-wide basis. - this means that they all share the same user properties: for example, lets say "favorite_item" is a user property on 2 apps, then it would just be a single user property at the project level.
Listed here are the configurations which will be based project-wide:
Audience: 50 *Audiences which are identical in name (case-sensitive) and definition across every app will be counted as 1.
User Property: 25 *firebase_last_notification is included. *User properties which are identical in name (case-sensitive) across every app will be counted as 1.
Custom Parameters: 10 text and 40 numeric *For reporting only. 25 custom parameters per event for logging still applies. *Projects with 20 registered parameters or fewer are going to be ‘grandfathered’, they will be allowed to keep them. However, they won't be able to register new parameters.
Conversion events: 10 *Custom events only. Pre-defined events are not included.
A response from Firebase Support to Denny Huang
Thanks for reaching out to us. We have sent that email to all customers who are exceeding
limits for future enhancements to the product.
If you got an email for exceeding custom parameters in your project, this means the project
(combined all apps) has more than 10 distinct text parameters and/or more than 40 distinct
numeric parameters. It the project exceeds 20 distinct text parameters, you must unregister
extraneous text parameters to get below 20. Otherwise, if the project already exceeds the
limit of 10 distinct text parameters, no changes are required at this time, but the limit of 10 will
be applied when you attempt to register new parameters.
I got the same message, the problem was I had too many parameter reporting.
Every event has 3 dots on the right side to "edit parameter reporting". Remove few of those to get to max 20 across all project.
In logEvent documentation google documentation you can read:
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 FirebaseAnalytics.Event and/or FirebaseAnalytics.Param is recommended for optimal reporting.
Also you have a limit on user properties:
If your app needs to collect additional data, you can set up to 25 different Analytics User Properties in your app. Note that user property names are case-sensitive and that setting two user properties whose names differ only in case results in two distinct user properties being logged.
it seems that you are logging an event with more than 20 different texts in the event parameters in all your apps
I need to track events in Google Analytics from a server through the Measurement Protocol. I can do this just fine, but my problem is that I want to send additional/custom data along with the event. Specifically, I want to send a UUID along with the event so that it is possible for me to fetch data from the Google Analytics API in the future and correlate events with rows in a relational database.
Is there any decent way to send custom data along with events? I looked at using the event value, but it must be an integer, and it is not intended for things like this. The event category, action, and label are reserved for other purposes.
I am not that proficient in Google Analytics, so the solutions off the top of my head would be:
Send an additional event containing the UUID in the event label or something like that. Seems like a bit of a hack/workaround to send two events, with one being used exclusively behind the scenes.
Perhaps using a custom dimension or metric. I am not 100% sure about the implications of this and if that's a decent approach or not.
So basically my question is: what would be the best way for me to send a UUID along with a Google Analytics event from a server, taking into consideration that I cannot use the event category, action, and label for the current event? Is there any other way in which I could link events retrieved from the Google Analytics API to rows in a database?
So let's say I trigger a "Completed Order" event to GA, and I also have orders in a MySQL database. So what I want to do, is to link an event to an order row in the database.
There are several things that you can do and it pretty much depends on what you want to do with the information you are storing. For starters, all your requests should include the uid field with the value being the user ID within your system. This way all Google Analytics data will be calculated on the same user. Note: this is an internal value used within Google Analytics and you won't be able to see it.
Second, I would create a custom dimension of the name user_id and store the user information in that. You will then be able to use this information within your reports to see what each user is doing. Note: it's against TOS to send user name, email, or any other PII (personally identifiable information) to Google Analytics. But you can send your internal user ID.
I have done both of these in the past and found it to work quite well.
More info on User-ID.