Getting started with Google Analytics for Firebase with Kotlin and Android - Firecasts

[@Sarev_]

I really hope you guys also use analytics on your own platform. I feel like for people who has never used any tools like this it's very unintuitive. Unfortunately even after watching this video I still don't fully understand. Since all these changes work only for the future data and require time to see if what I've done is what I wanted it's very hard to set it up for the first time. :/

[@Sarev_]

Also, it looks like the dashboard changes quite often as this video is still pretty new (only 1 year old) and it already doesn't show all options and fields available.

[@benstheweatherdog]

Use his debugging method that he goes over in the testing part of the video

[@whatthewaew]

wth I did before... Stuck in the middle for a month just for one second! Thanks god!

[@MrDannNamesake]

Thanks a lot for the video! Really clear explanation!

[@Firebase]

Glad you enjoyed it!

[@CL-08]

But what if we have a parameter name that is used across multiple events? Let's say we have two events, level_complete and level_failed. Both events have a "car used" parameter (ex: level_complete: { car_used} and level_failed: {car_used}). Does the custom metric aggregate across all of the events? Would we simply see a count of car_used for all events? If so, that seems...wrong. If so, we would have to make parameter names specific to the event to track counts per event AND parameter (ex: level_complete: {level_complete_car_used} and level_failed: {level_failed_car_used}). Hopefully I am misunderstanding or FB Analytics will show the related event for the custom metric.

[@GG9K71]

Unfortunately I don't see my custom parameters in the console, even after 24 hours..

[@dev-c6905]

can we use same firebase project for 2 different projects and store log via analytics having same bundle id?

[@GG9K71]

Very nicely explained!

[@joseph_pokemon]

nice vid thanks, I got 2 questions...if you don't mind... - what is the difference between "select_item" and "select_content" events? - also, can you add parameters of an event to another event for example I think that the "select_content" make more sense but I like to send the "type" param from "select_content" with it (I know I can send it but will it show in the reports and will I be able to aggregate a "type" count across all events?)

[@ProfessionalTycoons]

very cool functionality

[@IAmSamuelCharpentier]

Wouldn't it make more sense to make a test for the function that will roll 1000 dices and check for average and doubles and evaluate the behavior. Then you have to run that test pre build and you end up with a safer workflow and pushing something bug-free instead of debugging with analytics. Analytics should be used to monitor things like user behavior, not function results... anyways I guess it was a simple example to keep the video understandable and short.

[@pux0r3]

I totally agree -- it's always good to unit test critical paths and you'd ideally want to iron out these issues before shipping. But two funny things about this video: 1) I actually ran through this process working on an actual digital board game. Our testing didn't show cheating, but users kept claiming that it was. I deployed a solution similar to this (including the heat map!) to see if the dice were random in the wild (they were). 2) The typo/results actually happened when I went and coded up the sample (I forgot to add 1 for the int range). Talking about it during the editing process, folks said that I should leave it in since it hammered the point home 😃. And to be honest, I wouldn't necessarily think to unit test something "as simple as dice", but here I am ¯\_(ツ)_/¯.

[@caprameats4231]

super

[@balazsbalogh6792]

This method is terrible, you can see in the video that it is completely overcomplicated. The parameters are not related to events in any way on the interface ... impossible to maintain even for a medium-sized application. And absolutely impossible to see through the data or filter it. The debug view is absolutely fine, but the production version is unusable. :(

[@imagetag4618]

wow