In Google Analytics: App + Web, Pool Events. An event that differs from another event by Noun Uses. event by name
page_view It differs, for example, from an event with the name
These are all normal things. You know this.
However, the primary change that App + Web brings, when compared to Universal Analytics, is the way event parameters It is collected and processed.
This becomes more complicated than it should be. The complexity arises from the fact that there are many components to how app+web handles event parameters, including:
- Data collection time – Limitations on the number of parameters that can be Collected with the blow.
- data processing time – Events are processed, parameters and their values appear in real-time streaming displays. A maximum 25 custom parameters Included in the results are available for reports and BigQuery Export (Assuming you have enabled it for your app and website).
- 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.
Simmer . Newsletter
Subscribe to the Simmer newsletter to get the latest news and content from Simo Ahava right in your inbox!
Data collection – parameter limit
Google Analytics: App + Web has the same limitations as Google Analytics for Firebase (which makes sense, since they share the same technical infrastructure) – you can just Sends reach to 25 custom event parameters for each hit. This is it In addition to Automatically collected parameters (such as
For example, here I have a custom event with 26 custom parameters:
When this tag is run on a web page, all 26 custom parameters are I sent with the blow.
In the application and web reporting interface, only 25 custom parameters are available. What makes it even worse is that there doesn’t seem to be a recognizable pattern for which the parameter is dropped. In the example below, the parameter
param21 It is he who was dropped.
The next time I sent the event, it was
param04 It was dropped. It seems to me that dropping events is completely random, which is unfortunate. I was expecting an alphabetical and syllable type from the header or footer of the list.
Anyway, you have to keep this in mind. If you want to process event parameters in the application + web reports UI, you need to make sure that you submit Max 25 custom event parameters per hit.
Data processing – in real time
When you submit results with custom parameters, you will be able to see the parameters in real time reports.
The DebugView A great place to debug custom parameters. If you are using Google Tag Manager, it will be entering GTM preview mode automatically Mark app+web results as coming from the debugging device.
Find your user agent in the Debug Devices list, then click the event you want to analyze. The parameters will be displayed in one of the DebugView tools.
You can also see the parameters in a file At present Report (StreamView in Firebase).
Choose Events as a filter, then tap the most important events widget, find your custom event, and expand its parameters.
You can also find the parameters in the file All events A report, assuming the events were collected long enough ago to actually appear in the report. After clicking on the name of the event to enter its control panel, you can see a file At present Widget where you can choose to filter by parameter name.
As noted before, All of these are subject to a limit of 25 parameters in data collection. All reports in Google Analytics: The app and web reports UI will show you the cut list.
Data processing – BigQuery export
Once again, I declare my love for Google BigQuery. Enable BigQuery Export for Google Analytics: App + Web data is the smartest thing you can do today, so don’t get lost!
A BigQuery export gives you the raw data from the app + web dataset.
He is subject to himself 25 custom parameter limits per result As a front for reporting, but not to worry Empowerment Custom parameters reporting in BigQuery – All parameters and their values for each result are collected to BQ.
Data reporting – enable custom parameters
Now we get to the meat of this article.
Google Analytics: App + Web Gives You 50 text parameters And 50 number of parameters which you can enable as custom parameters in your reports. This for every event And for each project.
This means that if you want to include your custom parameters in your reports as their own tools, and if you want to use them in analysis reports (such as exploration), you first need to Maybe These parameters are 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
page_location In your custom reports, you need to enable it for
page_view event as a text parameter, and now you have 49 The remaining text parameters to enable in your project.
The kicker is that if you enable
custom_parameter_01 for an event named
my_custom_event, will deplete the quota by 1. Then, if you want to use
custom_parameter_01 With some other event, for example
my_other_event, you need to enable it for that too, and it will exhaust the quota again by 1.
These quotas are very strict, I hope they will be canceled. If you don’t, then at least you’ll have a BigQuery export for reference.
Anyway, l Maybe Custom parameters, you have to go to Events -> All events, then click the small actions menu at the end of the row containing the event name.
Noticeable! This means that you need to collect the event first before you can enable parameters for it. Hopefully at some point it will be possible to enable parameters for events that haven’t yet been collected.
From that menu, choose Edit parameter reports.
You can always click Report parameters Above the All events report to display a list of events for which custom parameters are enabled, and you can click on the event name to modify the parameters.
Once you see the parameter selector, you can search for the parameters name in the list. The list will display all parameters Collected with the specified event in the specified time range.
If you find the parameter, select it and click Add.
You can also add a parameter that does not appear in the list. Just type his name in the search field and click Add.
Once you add the parameter, you can set it Type, which affects what you can actually do with the parameter in reports.
Once you are happy, tap Memorizes to save the changes.
Remember, there Period – Make your decisions carefully!
When you are editing parameters, you can also choose Archives Parameter to edit share.
Noticeable! If you archive a parameter, it is No longer available in reports. So the change is retroactive – the data will Not be refundable.
BigQuery export is, again, your best friend, because archiving a parameter won’t delete it from the BigQuery tables you’ve already collected.
I hope this guide succeeded in shedding light on how event parameters work in app+web. The focus was specifically custom parametersThey seem to be the biggest source of confusion.
It’s important to get rid of the similarity with custom dimensions and custom metrics in Universal Analytics. Custom reports in the app + web have fundamental differences with legacy Google Analytics, particularly in how you treat the same parameter name across different events as a different entity each time, and how archiving the parameter removes it from your aggregate data as well.
Similar to Universal Analytics, custom parameters are not retroactive, so you won’t start collecting data in reports until you enable them for each event.
Not sure what to think about custom parameters yet. In the reporting interface, they are oddly hampered with quotas and a hard and fast removal process, but in BigQuery Export these are really valuable.
We’ll see how custom parameters evolve as beta matures; I think they will play an important role in deciding whether to migrate from Universal Analytics to App + Web.