Hi Serhat Aydin .. thanks for reporting!

It seems you did this "10 hours ago" from now. And this would be on the 23rd in UTC time. In our feature we support data from yesterday and back (as data needs to complete a day to report final numbers).

But here.. you were on the 23rd (in UTC time). You saw installs from the 22nd (data would be complete) and then returning users 1 day after (Day1) on the 23rd.

23rd was not complete yet, as you were looking on that date. So you were likely seeing realtime data on the 23rd and it was increasing as data streamed.

This is a mistake in our date-handling it seems where people in some timezones (like yours) start to see realtime data in that last date in their working hours.

Some more info would be great..

Thank you!

It would help if you reported this on our support page here..

We can keep track of your case in a better way to get attention on it.

Nikolaj Ahlberg-Pedersen: Hi Nikolay, game id is 170818, but it happens for all games. At the same time means, in same minutes just to explain there was no time difference for retention to change.

It was 10 hours ago but I think that's not important. This behavior is there for more than a year. It was always like that..

Serhat Aydin: Thank you for the information!

As I understand it from this information.. In this case you should not have been able to see the Day1 number for the 22nd (as this would be users returning on the 23rd and that was an incomplete date). You time would have been around UTC 21.30? Data should then have appeared around 2.5-3 hours later and not change.

We will look into it.

Nikolaj Ahlberg-Pedersen: Yes definitely it's imcomplete day, but the issue here is that why user count is shown different when I change date filtering?

Serhat Aydin: I see. But it only changed for that 22nd date right? We will look into it.

For now you should ignore any data reported on the current UTC day (like Day1 returning for yesterday). As it's not intended to be there.

Nikolaj Ahlberg-Pedersen: Yes the only problem is for 22nd which means today always. Actually it's nice feature to have and sometimes it shows correct value I guess.

Serhat Aydin: Indeed. We are discussing how to surface that number (realtime). But it needs to be clearly marked as realtime.. and we would likely need to predict the total for the day to calculate a predicted retention (like 8 users tracked in last 12 hours could mean 16 likely tracked in 24 hours).

Nikolaj Ahlberg-Pedersen: I realized one thing, when I do any change on the dates, sometimes I see a loading indicator before numbers are updated. Whenever I see it the results are correct. If there is no loading indicator, the results are like random. I guess this is a kind of bug.

Serhat Aydin: Hi again! I cannot seem to recreate sadly.

Would it be possible for you to record this via something like Loom? (free plugin to Chrome) and share the link with us directly on email?