"lastSyncTime" not accurate and system latency

[Triplennn]

Hi all,

We are conducting a real-time intervention study that utilizes Fitbit to track user activity. It is a server application. We extract daily summaries from users and provide timely interventions. However, we are currently encountering two issues:

(1) The "lastSyncTime" provided by the Fitbit API does not consistently align with the sync time reported by users. On occasions, users claim to have synced their devices, but the "lastSyncTime" does not reflect the update.

(2) After users sync their devices, there is a delay before their data is uploaded to the server. Unfortunately, we lack visibility on when the upload process is completed. As a result, some data is uploaded after the daily summary extraction, leading to inconsistencies.

In essence, we are seeking a solution to accurately determine when users' data has been successfully synced to the server. Any suggestions or insights regarding this matter would be greatly appreciated. Thanks.

[JohnFitbit]

Hi @Triplennn,

Welcome to the forums!

1. Do you have any examples of lastSyncTime discrepancies? Such as screenshots of the user's app/web dashboard indicating last sync time vs the lastSyncTime value on the APIs?
2. You can use the Subscriptions API to be notified real time when there is new data on the Fitbit account. You can subscribe to certain collection types from the user, and when the user syncs new data of that collection type to their account, Fitbit will send your application a webhook notification letting you know that there is new data for you to pull.

Hope to hear form you soon!