Total Users spike after change in screen_view event trigger
Aylen Micaela Monserrat
Hey all!
In one of my accounts we're seeing a spike of the users and sessions metrics after a trigger change in the screen_view event. [Attached images]
Why a change in the screen_view trigger could inversely affect the sessions and users metrics?
For note, the new users metric and active users metric has not been affected by this change.
There has been a change in the app sdk for the selected dates.
Joe Spiro
This question is a little beyond the scope of this group as it has more to do with Analytics's inner workings rather than how Firebase integrates with it. That said if you're interested in discussing it here please explain what precisely was changed about the trigger.
- "Total users" is the total number of people who visited your site or app in the specified date range.
- "Active users" (or just "Users") is the number of people who engaged with your site or app in the specified date range.
Viktoriia Kalyniuk
Could you clarify what you mean by "trigger change" related to the screen_view event? How was it implemented previously, and what changes have occurred? Is it iOS or Android, or both?
From the screenshot, it seems that screen_view events have dropped. Did you have both automatic and manual screen_view tracking enabled? This could potentially lead to duplicate screen views rather than affecting the user/session count.
In my experience, screen_view events themselves typically don’t inflate user counts. However, I've seen instances where user_id increases user counts, particularly when users log out during a session. This situation is specific to blended reporting identities. Firebase / GA44 uses the App Instance ID (client_id in app space) and user_id (if present) to determine user counts, so a highly unlikely screen_view tracking change was a culprit.
Could the issue you're seeing in your reports be related to changes in the App Instance ID within a session? I personally never see this happening often, unless you reset analytics data with resetAnalyticsData() that resets app instance id. I would check with app developers if this is not the case.
--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/29425e36-dfa2-4587-b188-c0a56cce8c73n%40googlegroups.com.