user_first_touch_timestamp与first_open_time有何不同? [英] How is user_first_touch_timestamp different from first_open_time?
问题描述
第一个"是指在此应用程序的运行中首先运行(直到应用程序终止并重新启动),还是在运行过程中首先运行?
Does "first" mean first in this run of the app (until the app terminates and restarts), or first across runs?
我认为这些字段将只有一个值,但是它们通常具有两个值.当我运行此查询时:
I thought that these fields will have only one value, but they often have two. When I run this query:
SELECT
user_pseudo_id,
COUNT(*) AS the_count
FROM (
SELECT
DISTINCT user_pseudo_id,
user_first_touch_timestamp AS user_first_touch_timestamp
FROM
`noctacam.<my project>.events*`
WHERE
app_info.id = "<my bundle ID>"
ORDER BY
user_pseudo_id)
GROUP BY
user_pseudo_id
ORDER BY
the_count DESC
我发现0.6%的用户有两个不同的user_first_touch_timestamp值.这是Firebase中的错误吗?
I find that 0.6% of my users have two different values for user_first_touch_timestamp. Is this a bug in Firebase?
与first_open_time类似:
Likewise for first_open_time:
SELECT
user_pseudo_id,
COUNT(*) AS the_count
FROM (
SELECT
DISTINCT user_pseudo_id,
user_properties.value.int_value AS first_open_time
FROM
`noctacam.<my project>.events*`,
UNNEST(user_properties) AS user_properties
WHERE
app_info.id = "<my bundle ID>"
AND user_properties.key = "first_open_time"
ORDER BY
user_pseudo_id)
GROUP BY
user_pseudo_id
ORDER BY
the_count DESC
完全相同的0.6%的用户对此字段也有两个不同的值.
Exactly the same 0.6% of users have two different values for this field, too.
参考: https://support.google.com/firebase/answer/7029846?hl= en https://support.google.com/firebase/answer/6317486?hl=
推荐答案
我也开始想知道这两个参数之间的差异,并发现了这种差异.
I started wondering about the difference in these 2 params too and found this difference.
来自用户属性:
First Open Time
-用户首次打开应用的时间(以毫秒为单位,UTC),四舍五入到下一个小时.
First Open Time
- The time (in milliseconds, UTC) at which the user first opened the app, rounded up to the next hour.
从 BigQuery导出架构:
user_first_touch_timestamp
-用户首次打开应用的时间(以微秒为单位).
user_first_touch_timestamp
- The time (in microseconds) at which the user first opened the app.
就我而言,四舍五入就是差异.我认为Firebase出于某种原因需要将first_open_time
作为用户属性,因此它们只是四舍五入并复制了user_first_touch_timestamp
.
In my case, the rounding was the difference. I envision that Firebase needed to have first_open_time
as a User Property for some reason so they just rounded and copied user_first_touch_timestamp
.
我知道它仍然无法回答您的整个问题,也无法解释为什么0.6%的用户有2个不同的值.我仍然认为这可能会对这里的人有所帮助.
I know it still doesn't answer your whole question and doesn't explain why 0.6% of your users have 2 different values. I still thought that this may help someone here.
这篇关于user_first_touch_timestamp与first_open_time有何不同?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!