Starting May 2026, Google moved all Fitbit app users to Google Health and began enforcing a requirement to use a Google account to sync data from their Fitbit device. On September 30, 2026, Google will shut down the Fitbit API which MyDataHelps uses to collect data from Fitbit device users including through the Google Health mobile app in favor of a newly released Google Health API.
In order to continue collecting data from Fitbit device users in the new Google Health API, Google requires distinct user authorization through a new secure connection. This means all MyDataHelps projects & participants with Fitbit device connections must take action to continue gathering data from participants. If your project collects Fitbit data, this guide covers the steps needed to migrate to the new Google Health connection.
Sensor & EHR Settings
Google Health has been added as a new sensor data source in MyDataHelps, found in Sensor & EHR Settings. If your project was in Production Mode and not Paused on August 10, 2026, this has been automatically enabled in your project. For all other projects, you will need to enable this setting to start collecting data from Google Health.
Participant Re-Connection
Since Google Health is a distinct data data provider from Fitbit, Google requires all participants to specifically authorize MyDataHelps to collect data from the Google Health API. There are some automatic updates to app designer in place to support connection; however, you may wish to optionally nudge participants as well.
App Designer Updates
Any projects collecting Fitbit data and using the View Builder "Connect Devices Menu" or View Library views with device connections on that date will also have Google Health automatically enabled for connection, as shown:
Additionally, the "Connect Fitbit" component will show "Connect Google Health" after a participant has connected their Fitbit account. Until the Fitbit API is shut down, it is recommended to have participants connect both Fitbit and Google Health in this sequence to prevent gaps in data.
Participant Notifications
You may want to reach out to participants who have previously enabled Fitbit but have not yet enabled Google Health. For example, the following segment logic will filter for participants who have shared Fitbit data but have not yet shared any Google Health data.
Once you've published the notification you wish to send, you can create a Based on Participant Events schedule to nudge these participants at a set frequency until they've connected.
Schedules & Segments
Since Google Health is a distinct data connection, all logic actively used in Schedules and Segments using Fitbit will need to be updated to include Google Health as needed. Criteria such as Sensor Data Received now has a "Google Health" option. Similar to Fitbit, Google Health is added as a "Linked Account" with a category of "Device Manufacturer". You should review all segments and schedule logic and adjust or configure new ones as necessary depending on your project.
Consider updating any logic using the "Fitbit Device" criteria, as this only includes Fitbit and not Google Health connections.
Data Visualization
All projects using built-in visualizations, including "View Library" tabs such as the "Fitbit" and "Device Data" tabs as well as View Builder components, will seamlessly display data from Google Health with no required updates.
If your project uses custom hosted views which display or access Fitbit data, you will need to update your views to incorporate Google Health data since it is a distinct provider.
Intraday
The Google Health API will expose data with similar granularity to Intraday data for all users, without special access permissions. If your project collects Fitbit Intraday data, nothing additional is needed to continue to collect this fine-grained data through Google Health.
Data Exports
Fitbit exports will remain active until the Fitbit API is shut down by Google. Google Health exports will be released soon for you to enable. Once enabled, your first Google Health export will contain all historical data from when participants first connect their account as described above.
API Integration
If you access Fitbit data through the DeviceData V2 API, you should incorporate the new Google Health Namespace into your API data flow(s).
The Device Data V1 API does not support Google Health data. If you rely on this endpoint for Fitbit data, you will need to migrate to the Device Data V2 endpoint to continue accessing Google Health data.
Frequently Asked Questions
Q: Didn't Google already change Fitbit to Google Health?
A: In May 2026, Google shut down the Fitbit mobile app and replaced it with the Google Health app. Fitbit users since this date were required to use a Google account to sync their data to their phone/Google Health app, but data was still sent to third parties like MyDataHelps using the existing Fitbit API. This action by Google ends that connection for a new Google Health API.
Q: Is Google Health the same as Google Health Connect?
A: No, Google Health is a mobile app available on both Android and iOS to collect data from Fitbit and other devices, and is distinct from Google Health Connect. Health Connect is built in to the Android operating system and allows users to connect health and fitness data from many sources including other mobile apps and their personal health records similar to Apple Health on iOS devices.