#Flutter firebase analytics update
#Flutter firebase analytics android

If you’re looking for your most recent data in these reports, keep in mind that the default “Last 30 days” report doesn’t include any data from the current day - this is because the data for the current day is incomplete, and it would be misleading (not to mention a bummer) to see every graph end with a giant downturn in usage. So that’s the kind of delay you should expect after your client data is sent down to the server. This process typically runs every few hours.

#Flutter firebase analytics update

Now, moving on to the second case, there’s also the frequency at which Firebase Analytics grabs the latest batch of data it’s received from your client and uses that data to update the reports and graphs you see in the Firebase Console. The one corner case where analytics data would actually get lost on iOS would be if your app crashed and then your user immediately uninstalled it. So if a user tries your app for 20 minutes and then uninstalls it, that session data will still be received, because your app will have sent down the data the moment the user moved your app to the background. On iOS devices, Firebase will also send down data when your app moves into the background. Which means that even if your user deletes your app after an hour, that data will still get sent down because Google Play Services still has it.

#Flutter firebase analytics android

On most Android devices, it’s Google Play Services that manages sending down this data. “Hang on there - once an hour? What about my users who churn out sooner than that?” And on iOS devices, Firebase Analytics will also send down its data whenever your app goes into the background. In addition, Firebase Analytics will send down all of its data from the client if your user triggers a conversion event (like making an in-app purchase). But on Android devices with Play Services, this one hour timer is across all apps using Firebase Analytics. On iOS devices (and Android devices without Google Play Services), this one hour timer is per app. Instead, analytics data is batched up and sent down when the client library sees that there’s any local data that’s an hour old. That would be a serious battery drain, and we want to be respectful of your users’ battery life. Client-to-server latencyįirebase Analytics doesn’t constantly stream down data from the client device. The time it takes for Firebase Analytics data to be displayed to you in the Firebase console once it’s been received on the server.The time it takes for analytics data on the client to be sent over to the Firebase Analytics servers.To understand latency with Firebase Analytics, there are two potential delays you need to be aware of: So buckle in, kids! We’ve got some learning ahead of us… This is probably one of the most common questions we get around Firebase Analytics, and we thought it was worth taking some time to delve into this topic a little deeper. Update: Both DebugView and StreamView are available to all Firebase developers, so you can get access to your data a whole lot faster! Happy Analytics viewing!