I've gone over a ton of documentation on this topic and still aren't sure if the 25 custom params/property limit in Firebase is per app or per event name?
Say I have 50 different events with 5 unique property names each, that would be a total of 250 unique property names. Is such a thing supported or do I start with a limit of 25 across all events?
I have Firebase hooked up to Bigquery so I'm less concerned about the limitations in the Firebase reporting admin.
Thanks.
Limitations for each Firebase project:
Limit for 25 params is per logEvent call.
Limit for 500 events is per app instance.
Limit for 50 custom parameter (40 numeric and 10 texts) is the global limit in Google Analytics for Firebase dashboard.
No limit for custom parameters in Big Query.
This is as of 03/20/2018.
The limits are documented here.
Google Analytics for Firebase lets you specify up to 25 custom
parameters per event (Android or iOS).
You can also identify up to 50 of those custom event parameters per
project (40 numeric and 10 textual) to include in reporting by registering
those parameters with their corresponding events. Once you register
your custom parameters, Google Analytics for Firebase displays a
corresponding card showing the data in each related event-detail
report.
The javadoc for logEvent gets more specific:
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.
Related
I have 2 problems with Firebase.
1) Can I add custom parameters to standard events in Firebase with GTM?
2) I have read that 500 events can be added per App Instance. Is this just a number that limits the data on the panel? Do I still have 500 event limit problems when I transfer the data to Big Query?
Thank You
1) The parameters are all strings, you can furthe cast them to timestamps in BigQuery or transform them using any ETL tool.
2)
- 500 different types of Events per app
- 25 unique parameters with each Event type
I'm setting up Firebase analytics for my app for both android and ios. I just learned that there's a 50 custom parameters limit I can create, also learned there are prescribed event parameters that firebase suggests with recommended events.
My question is, are these prescribed parameters counted as custom parameters when used?
My guess is yes, but I want to be clear before I actually start coding and possibly mess up with the number of parameters.
By "custom parameters" do you mean custom parameters in event? If that's the case then limit is 25 per event.
Maybe you thought about custom parameters in reporting? Then the limit is indeed 50, but it is only for reporting.
If you ask about user properties then the limit is 25 per app and no - predefined/default user properties don't count, so you can add 25 user properties yourself.
As a general rule - usually default stuff doesn't count for limits.
For more info on up-to-date limits see here: https://support.google.com/firebase/answer/9237506
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