Syncing Fitbit Devices
Keep Fitbit devices syncing so data reaches Fitabase: mobile app compatibility, keeping Bluetooth on during collection, and how to force a manual sync.
Understand Fitbit and Google Health data in Fitabase: syncing, data resolutions and availability, sleep stages, activity logs, Active Zone Minutes and accounts.
Keep Fitbit devices syncing so data reaches Fitabase: mobile app compatibility, keeping Bluetooth on during collection, and how to force a manual sync.
Use Google demo accounts to collect deidentified Fitbit data: account expiration, the research application and IRB requirement, client ID, and approval timing.
Create de-identified Google accounts for study participants during Fitbit app setup, skip phone verification, and add a study recovery email address.
Devices keep minute and second data for only 5-7 days. Learn how sync frequency and low battery affect high resolution data and what to tell participants.
Reduce the feedback participants see on Fitbit devices and the mobile app with PDF blinding tutorials for the Charge 2, Alta HR, and Alta.
Estimate how much mobile data Fitbit app syncing uses per participant, with daily and monthly figures for heart rate and non-heart rate devices.
Review which Fitbit data types Fitabase provides at second, minute, hour, and day resolution, plus timestamped logs like sleep, weight, ECG, and sync events.
Learn the five ways Fitbit activity logs are created, from SmartTrack to manual entry, and which duration, calorie, and heart rate details Fitabase collects.
Interpret Fitbit light, deep, REM, and wake data, how short awakenings split sleep stages, and how to read the Fitabase 30 Second Sleep Stages export.
See how Active Zone Minutes are earned from Fitbit heart rate zones and how Fitabase estimates them on the Heart Rate report, excluding swim workouts.