User Engagement Table timestamps

@Sanskrity Got it. Thanks.

For the user engagement table, the timestamps increase everytime by 30 mins. What is the reason for that?

Also, @Sanskrity Given that for each session, there will only be one user-session event passed. So ideally in the following query that I attached, the number of distinct Session Id and the total count should be same.

@Shraeyas On the user engagement events table, similar records are rolled up at 30 mins interval. You can refer to the Count column to check how many records are rolled up for a particular row event.

The distinct count functionality uses hyperloglog algorithm which gives an approximate number and not the exact count. Hence, the difference in number.