Analytics如何定义会话

Analytics如何定义会话

本文介绍了Firebase Analytics如何定义会话?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

Firebase Analytics在会话"(如每个用户的会话"和平均会话长度")方面有许多统计信息,但是Firebase Analytics如何准确地定义会话?

Firebase Analytics has a number of stats around "Sessions" (like "Sessions per user" and "Average session length"), but how exactly does Firebase Analytics define a session?

推荐答案

我会回答我的问题,说Firebase Analytics将会话定义为用户与您的应用互动最少的时间(默认为10秒) ),然后您的用户在一定时间内(默认为30分钟)不与您的应用互动.但是,如果您希望有所不同,可以更改这些时间.

And I'll answer my question by saying that Firebase Analytics defines a session as a user engaging with your app for a minimum amount of time (10 seconds by default) followed by your user not engaging with your app for a certain amount of time (30 minutes by default). But you can change those times if you'd like something different.

因此,如果用户开始使用您的应用程序,切换到消息传递以发送消息,然后再返回到您的应用程序,再次切换到消息传递以发送快速自拍照,然后再返回到您的应用程序,这全部被认为只是一个会话.

So if a user starts using your app, switches to messaging to send a message, goes back to your app, switches to messaging again to send a quick selfie, then goes back to your app, that's all considered just one session.

类似地,如果用户不小心点击了您的应用程序图标,然后迅速转开以打开他们真正打算打开的应用程序,则不会记录为会话.

Similarly if a user accidentally taps on your app icon and then quickly switches away to open up the app they actually meant to open, that won't get recorded as a session.

这篇关于Firebase Analytics如何定义会话?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

09-02 14:30