I see there is an update in the last android sdk and they show, they log the parameter on every event is logged, but how can I add screen tracking?
There is a user engagement tab in the dashboard, but that does not expand to give some more insights.
However, I see messages like this while switching activities:
D/FA: Logging event (FE): _e, Bundle[{_o=auto, _et=4807, _sc=MainActivity, _si=-3289793799694080660}]
What does that mean? They are tracking activities? If yes, how can we see timings? If no, how can we track activity/screen timings with the help of custom events (this is possible, right?) ?
screen_view when a screen transition occurs and any of the following criteria are met: No screen was previously set. The new screen name differs from the previous screen name. The new screen-class name differs from the previous screen-class name.
To solve this, we need to use the RouteAware class and only set the current screen in case it's the top route: either our route is added to the stack or the previous top route was popped and we arrived onto the route. I created an enum to track the screens (and functions to turn the enum to screen names).
Screenview in Google Analytics represent content users are viewing within an app. The equivalent concept for a website is pageview . Measuring screen views allows you to see which content is being viewed most by your users, and how are they are navigating between different pieces of content.
Your reports should refresh approximately every 4 hours. Just a hunch -- default ranges such as "Last 30 Days", "Last 7 days", etc.
Automatic screen tracking was added in the Android and iOS SDKs in October of 2016. These events are recorded automatically when the library detects that you've changed Activities / ViewControllers.
That said, there might be times when you want to record your own screen tracking (a GameKit game for instance, tends to stay on a single ViewController and changes "screens" through new GameKit scenes), so you can manually make a call to setScreenName
if you want to track screens manually.
Right now, this screen reporting manifests itself on the Dashboard of the Firebase Analytics console in the "User Engagement" section -- you can break down your user engagement by screen name or screen class to see how long people spend on each screen. You can also get this report by looking at the specific screen_view
event in the console.
If you need more specific information than that, you'll probably need to start exporting your Google Analytics for Firebase data to BigQuery and run your queries there.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With