关于Firebase Bigquery在屏幕上花费的平均时间

本文介绍了关于Firebase Bigquery在屏幕上花费的平均时间的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

关于平均在屏幕上花费的时间.下面的查询正在工作.但是结果没有到来

Regarding Avg. time spent on screen. Below query is working. But result is not coming

select event_name, param1.value.string_value as firebase_previous_screen, param2.value.int_value as engagement_time_msec From `<table>', UNNEST(event_params) as param1, UNNEST(event_params) as param2 where event_name = 'user_engagement' and param1.key='firebase_previous_screen' and param2.key='engagement_time_msec' group by 1, 2, 3 order by engagement_time_msec desc

请.查找随附的界面屏幕快照，以供您参考.请帮助

Pls. find attached the interface screenshot for your kind reference. Pls. help

推荐答案

花费的时间:user_engagement事件带有参数，这些参数指示在前一个屏幕上发生了多少用户参与时间.

Time Spent: The user_engagement event carries with it parameters that indicate how much user engagement time occurred on the previous screen.

engagement_time_msec:参与时间(以毫秒为单位) firebase_screen_class，firebase_screen:上一个屏幕的屏幕类和屏幕名称.

engagement_time_msec: The amount of engagement time (in milliseconds) firebase_screen_class, firebase_screen: The screen class and screen name, respectively, of the previous screen.

您可以使用此事件汇总每个屏幕的用户参与时间.

You can aggregate user engagement time per screen using this event.

在不久的将来，我们计划在screen_view事件本身中捕获此参与时间，因此此时的建议将略有变化，以更加专注于screen_view事件而不是user_engagement事件.

In the near future, we plan to capture this engagement time in the screen_view event itself, so the advice at that point would slightly change to be more focused on the screen_view event instead of the user_engagement event.

唯一的屏幕视图/用户:这些基于screen_view事件；即screen_view事件的计数是屏幕浏览的计数.记录screen_view的非重复user_pseudo_id数是唯一的用户数.

Unique Screen Views/Users: These are based on screen_view event; i.e. the count of screen_view events is the count of screen views. The count distinct user_pseudo_id that logged a screen_view is the unique count of users.