Google has retired the Fitbit Web API and required all third-party apps, Fitabase included, to migrate to the Google Health API. This means that your study participants will need to grant permission again for Fitabase to access their data so that it continues to sync. While we previously advised connecting only new / actively syncing participants, we now recommend that all currently-running studies have participants re-authorize to the Google Health API even if they have completed their data collection period.
While not required, reauthorizing participants with completed observation periods will allow Fitabase to backpull data for them via the new Google Health API. That way, every participant’s data is processed with the same methods and algorithms and your dataset is consistent. Backpulling past observation dates through the Google Health API may also give you improved data, since it’s processed with Google’s updated methods.
You may see updates or improvements to:
- Step counts
- Intraday calories
- Activity logs
- Intensity minutes are currently only available in intensity exports. We’ll soon have these in activity logs, as well.
- Activity minutes may also look different. We’ve outlined those changes here.
- Sleep
- Google has made updates to short wakes within sleep records now returning only values reflecting high confidence levels.
- SpO2 accuracy
- Skin temperature
- Pixel Watch or a Fitbit Edge can return all-day skin temperature
We strongly urge studies to reauthorize study Google accounts or get in touch with past participants and have them go through the re-authorization process outlined here. If you have any questions, please reach out to hello@fitabase.com or explore our migration guide here. Fitabase will soon be scheduling backpulling historical data using the new Google Health API for certain key datasets. Please keep an eye out for announcements and more information.