Firebase event parameters

Firebase event parameters DEFAULT

Custom Parameter Reporting In Google Analytics: App + Web

In Google Analytics: App + Web, you collect events. One event differs from another event by the name it uses. An event with the name is different from, say, an event with the name .

This is all run-of-the-mill stuff. You know this.

However, the fundamental change that App + Web introduces, when compared to Universal Analytics, is how event parameters are collected and processed.

custom-parameter-reporting-app-web.jpg

This gets more complicated than it should be. The complication arises from the fact that there are several components to how App + Web handles event parameters, including:

  • Data collection time - limitations on the number of parameters that can be collected with the hit.
  • Data processing time - events are processed, and the parameters and their values are shown in the real-time stream views. A maximum of 25 custom parameters included in the hit are made available to reports and the BigQuery Export (assuming you’ve enabled it for your App + Web property).
  • Data reporting time - to be able to actually segment and report on these parameters, you need to enable them as custom parameters in your reports. This is the main focus of the article you are reading.
X

The Simmer Newsletter

Subscribe to the Simmer newsletter to get the latest news and content from Simo Ahava into your email inbox!

Data collection - parameter limit

Google Analytics: App + Web has the same limitation as Google Analytics for Firebase (makes sense, since they share the same technical infrastructure) - you can only send up to 25 custom event parameters per hit. This is in addition to the automatically collected parameters (such as for the event).

For example, here I have a custom event with 26 custom parameters:

Too many parameters

When that tag is fired on the web page, all 26 custom parameters are sent with the hit.

In the App + Web reporting interface, only 25 custom parameters are made available. What makes it even more unfortunate is that there doesn’t seem to be a discernible pattern for which parameter is dropped. In the example below, parameter is the one that was dropped.

Removed parameter

The next time I dispatched the event, it was that was dropped. It seems to me that the dropping of events is completely random, which is unfortunate. I would have expected an alphabetic sort and truncation from either head or tail of the list.

In any case, you need to be mindful of this. If you want to process the event parameters in the App + Web reporting user interface, you need to make sure to send a maximum of 25 custom event parameters per hit.

Data processing - real time

When you send hits with custom parameters, you’ll be able to see the parameters in real time reports.

The DebugView is a great place to debug the custom parameters. If you’re using Google Tag Manager, entering GTM’s Preview mode will automatically flag App + Web hits as originating from a debug device.

DebugView in App + Web.jpg

Find your user agent in the Debug Devices list, and then click the event you want to analyze. The parameters will be displayed in one of the DebugView widgets.

You can also see the parameters in the Realtime report (StreamView in Firebase lingo).

Realtime.jpg

Choose Events as the filter, then click the Top Events widget, find your custom event, and expand its parameters.

You can also find the parameters in the All Events report, assuming the events have been collected long enough ago to actually appear in the report. After clicking the event name to enter its dashboard, you can see a Realtime widget where you can choose to filter by parameter name.

Realtime Widget

As noted before, these are all subject to the 25 parameter limit in data collection. All of the reports in the Google Analytics: App + Web reporting user interface will show you the truncated list.

Data processing - BigQuery export

Once again, I profess my love for Google BigQuery. Enabling the BigQuery export for your Google Analytics: App + Web data is the smartest thing you can do today, so don’t dally!

The BigQuery export gives you the raw data from your App + Web data collection.

It is subject to the same 25 custom parameter limitation per hit as the reporting interface, but you do not have to worry about enabling custom parameters for reporting in BigQuery - all the parameters and their values per hit are collected to BQ.

BigQuery Export

Data reporting - enabling custom parameters

And now we get to the meat of this article.

Google Analytics: App + Web gives you 50 text parameters and 50 number parameters that you can enable as custom parameters in your reports. That’s per event and per project.

This means that if you want to include your custom parameters in your reports as their own widgets, and if you want to utilize them in the Analysis reports (such as Exploration), you need to first enable these parameters for reporting.

Each time you enable a parameter for an event, you exhaust the quota available for your project. So if you want to use in your custom reports, you need to enable it for the event as a text parameter, and now you have 49 text parameters remaining to enable in your project.

Global parameters registered

The kicker is that if you enable for an event named , it will exhaust the quota by 1. Then, if you want to use with some other event, e.g. , you need to enable it for THAT, too, and it will again exhaust the quota by 1.

These quotas are pretty strict, and I hope they are lifted. If they aren’t, at least you’ll have the BigQuery export to fall back on.

Anyway, to enable custom parameters, you need to go to Events -> All events, and then click the little action menu at the end of the row with the event name.

Note! This means that you need to first collect the event before you can enable parameters for it. Hopefully it will be possible at some point to enable parameters for events that are yet to be collected.

Action menu

From that menu, choose Edit parameter reporting.

You can always click the Parameter reporting tab on top of the All events report to see a list of the events that have custom parameters enabled, and you can click the event name to edit the parameters.

Parameter reporting tab

Once you see the parameter selector, you can search for the parameters name in the list. The list will show all parameters that have been collected with the given event in the date range selected.

If you find the parameter, select it and click ADD.

Add parameter

You can also add a parameter that does not appear in the list. Just type its name in the search field and click Add.

Add missing parameter

Once you’ve added the parameter, you can set its type, which impacts what you can actually do with the parameter in the reports.

Parameter types

Once you’re happy, click Save to save the changes.

Remember, there is a quota - make your decisions carefully!

Archiving a parameter

When you edit parameters, you can also choose to archive a parameter to free up quota.

Note! If you DO archive a parameter, it is no longer available in the reports. So the change is retroactive - the data will not be recoverable.

Archive parameter

The BigQuery export is, again, your best friend, because archiving a parameter will not delete it from the BigQuery tables you have already collected.

Summary

I hope this guide has managed to shed light on how event parameters work in App + Web. The focus was specifically on custom parameters, as they seem to be the biggest source of confusion.

It’s important to rid yourself of the analogy with Custom Dimensions and Custom Metrics in Universal Analytics. Custom reporting in App + Web has fundamental differences to ye olde Google Analytics, particularly in how the same parameter name across different events is treated as a different entity each time, and how archiving a parameter removes it from your collected data, too.

Similarly to Universal Analytics, custom parameters are not retroactive, so they will start collecting data in reports only after being enabled per event.

I’m not sure what to think of custom parameters yet. In the reporting interface they are oddly handicapped with the quotas and the hard-and-fast removal process, but in the BigQuery export they are really valuable.

We’ll see how custom parameters evolve as the beta matures; I think they will play an important part in deciding whether to migrate from Universal Analytics to App + Web.

Sours: https://www.simoahava.com/analytics/custom-parameter-reporting-google-analytics-app-web/

How to view event parameters from Firebase console

Custom-parameter reporting Define custom parameters for your events.

Google Analytics for Firebase lets you specify up to 25 custom parameters per event (Android or iOS).

You can also identify up to 50 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 data card in each related event-detail report.

Each parameter that you specify counts toward the project limit of 50. For example, if you specify the same parameter for 3 different events, then that counts as 3 of your 50.

To register custom parameters for an event:

On the Events page, any event with registered parameters has a gray box next to the event name with the number of registered parameters for that event.

To edit registered parameters:

The per-app count for registered parameters appears at the bottom of the list of parameters. As you enter parameters, the count updates. When the quota has been reached (50), that number appears in red, indicating that you cannot register any more.

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.

Sours: https://stackoverflow.com/questions/37604275/how-to-view-event-parameters-from-firebase-console
  1. Quads warzone tournament
  2. History of febreze
  3. Finger puppet images
Question

Firebase custom event parameters not visible in console

*

9714visibility0arrow_circle_up0arrow_circle_down


I need help with custom parameters of Firebase event, don’t seem to be able to see or use any event parameter. Basically trying to use parameters to create Audience segmentation, but parameters seem to never arrive (on the other hand all custom events arrive correctly).

As you can see from the attached screenshot the parameters list is always empty for custom events. The only parameters we can correctly see are related to system events (like or ).

This is how we trigger custom events and parameters:

Any help would really be appreciated.

Firebase console Firebase console


Answer - 1

0arrow_circle_up0arrow_circle_down

My custom events did not display their parameters in the Firebase dashboard under Events until I installed the app on a bunch of different simulators in order to get my user count up to 12. Drove me nuts seeing all those empty graphs until I found this post with the answer from Dmila Ram, which appears to be correct - thresholds apply to custom parameter display.

by   *


Answer - 2

0arrow_circle_up0arrow_circle_down

According to the website https://firebase.google.com/docs/analytics/android/events,

Custom parameters: Custom parameters are not represented directly in your Analytics reports, but they can be used as filters in audience definitions that can be applied to every report. Custom parameters are also included in data exported to BigQuery if your app is linked to a BigQuery project.

Custom parameters should always arrive with your events. However, custom parameters are used in Audience in the SDK and if there is an audience that matches your definition, they will be reported to the server. You just cannot see them in the report for now.

by   *


Answer - 3

0arrow_circle_up0arrow_circle_down

Go to your event and click in the 3 points icon: event menu and click edit parameter reporting

and there you can select which parameters you want to see, so click on username and gameplayed and push "ADD" button and set the unit of measurement.

parameters

Note that it could take some time from your first events fired to be shown in console.

Also when you have a text parameter it take time to gather it's different values from fired events and to be shown correctly in console.

by   *


Answer - 4

0arrow_circle_up0arrow_circle_down

You can see your Custom Event in Analytics - Dashboard - StreamView - Events - Top Events - see picture. But I belive this is just for last 30 minutes.

enter image description here

I would recomment you to use Fabric Analytics - this will meet your needs. see https://docs.fabric.io/android/answers/answers-events.html

enter image description here

by   *


Answer - 5

0arrow_circle_up0arrow_circle_down

According to My understaning, there are 2 different things here.

  1. User Property: Which you map to a user session like group_id, city_id, plan_id he belongs to or has. This is what you use to create Audience. Same User Property you can use in other product such as Firebase remote config etc.., But you need to pre-define these keys under "USER PROPERTIES" tab you see in your screenshot you shared. As usual this will take couple of hours to take effect! BTW this is how you set a User Property

[FIRAnalytics setUserPropertyString:food forName:@"favorite_food"];

Link to read more here

  1. Event Parameters: These are extra info you pass in a Event you Log. Suppose you have a sample event called "detail_view" you can add "item_id", "timestamp", "session_id" etc.., as parameters. But you will need to wait for the custom event to appear for couple of hours and then manually you need to add parameters in the dashboard like this. And this operation too takes couple of hours to take effect! BTW this is how you set Event Parameters

    [FIRAnalytics logEventWithName:@"share_image" parameters:@{ @"name": name, @"full_text": text }];

Link to read more here

by   *


Source: https://stackoverflow.com/questions/40738448

Sours: https://www.titanwolf.org/Network/q/5d24fd77-b1f1-4f56-bfce-4c8b36367812/y
Getting started with Firebase Analytics, BigQuery - Firecasts

Firebase custom event parameters not showing in Firebase Analytics console

Firebase custom event, with parameters and not showing correctly in console.

I can see the firebase custom even, have tried the 'edit parameter reporting' button on the events firebase console, and setup reporting for and , but the string values I bundle with these keys does not show.

Am I missing any required parameters for custom events? I could not find any documentation requiring any.

I expect to see something in the console. However I see this

Edit parameter reportingCustom events coming throughitem_id and item_name params empty

Answer #1:

it's better to put extra info for the log in the bundle and use the firebase general event type for logEvent. when you use a custom event name for logEvent firebase will limit the length of the data's character you send. for example, if you want to send user clicks events to firebase its better to use this approach

the FireBase event is set to select_content. and also we defined a content type with the name "CLICKS". so whenever you open the firebase console if you filter SELECT_CONTENT tag you will see "CLICKS" content that holds all log that you send. the values are showing as ITEM_ID value in console. if you want to test you can use debug view with a device to test what your client sends to fireBase each time . hope this will helps you att all.

Answered By: mohammadReza Berenji

Answer #2:

With the example of Firebase.logEvent() you are registering a suggested Event, the value of the is always thats because you never see the changes on the console.

I suggest create a custom bundle events

I also recommend check this answer that shows you an example of how Firebase Events are organized in the Dashboard Console

Answered By: Martín Serrano

The answers/resolutions are collected from stackoverflow, are licensed under cc by-sa 2.5 , cc by-sa 3.0 and cc by-sa 4.0 .


Sours: https://www.py4u.net/discuss/662383

Event parameters firebase

How to view event parameters from Firebase console

Honestly, the answer here didn't help me at all. I finally figured out that you have to manually add custom parameter reporting to each event. Here's a link to the docs.

https://support.google.com/firebase/answer/7397304?hl=en&utm_id=ad&authuser=0

And I guess in case this link dies, I'll add the steps below. This is just copy paste from the link.

Custom-parameter reporting Define custom parameters for your events.

Google Analytics for Firebase lets you specify up to 25 custom parameters per event (Android or iOS).

You can also identify up to 50 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 data card in each related event-detail report.

Each parameter that you specify counts toward the project limit of 50. For example, if you specify the same parameter for 3 different events, then that counts as 3 of your 50.

To register custom parameters for an event:

On the Events page, any event with registered parameters has a gray box next to the event name with the number of registered parameters for that event.

To edit registered parameters:

The per-app count for registered parameters appears at the bottom of the list of parameters. As you enter parameters, the count updates. When the quota has been reached (50), that number appears in red, indicating that you cannot register any more.

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.


It looks like you're logging the correct event and parameters. It should produce a select_content report that looks like the attached. You don't need to create an audience to see this.

enter image description here


Right now to show parameters you need to configure metrics or dimensions like written here: https://support.google.com/analytics/answer/10075209

After you added it and waited for 24 hours you will see something like that: enter image description here Here is the main event, and is a parameter of this event

UPD: To add a parameter you need just use something like this:

Sours: https://newbedev.com/how-to-view-event-parameters-from-firebase-console
Firebase Analytics Tutorial - How to track Mobile Apps

.

Now discussing:

.



2547 2548 2549 2550 2551