
This feature is currently undergoing testing and is only available to our beta testers at the moment. We plan to release this in the next few weeks and will send a broader e-mail about this migration.
You can read the following data types from Google Health Web (Beta):
You can write the following data types to Google Health Web (Beta):
The easiest way to get started is to follow our Getting Started Guide, which will walk you through how to exchange data between Google Health Web (Beta) and many other services!
Are you looking to get more out of our Google Health Web (Beta) integration? Check out our How It Works, which will walk you through how to unlock the full power of FitnessSyncer.
They share a name but work in completely different ways. Google Health Connect runs on your Android phone: our app reads the data already on your device and sends it to us. Google Health Web is a connection between our servers and Google’s, so it works without a phone and keeps syncing when your phone is off.
You can use either, or both. If you already sync through our Android app, you do not have to change anything.
Start the move to Google Health Web. It walks you through your Fitbit and Google Fit sources and destinations, shows what each one will be able to sync afterwards, and lets you choose which to move.
Everything that identifies a source is kept — your history, your name for it, your filters and your settings. Only the connection changes, and any Destination tasks using it keep working.
Your existing connections keep syncing until Google switches the old APIs off, so there is no rush, but moving sooner means nothing to do later.
Google Health does not offer blood pressure or cycle tracking at this time through the Google Health Web integration. Instead, you can use our Android app and Google Health Connect for this data.
Google Health’s web API lets us read your route but gives us no way to write one — there is no permission for it to ask you for. So an activity FitnessSyncer sends to Google Health arrives with its distance, duration, calories and heart rate, but without the map.
This is not something you can grant or change, and nothing is lost: the route is still on the activity in FitnessSyncer, and any other destination that supports routes still receives it.
The other direction is unaffected. An activity FitnessSyncer reads from Google Health keeps its route.
Google asks you to approve each kind of data separately, and you can approve some and decline others. Anything you declined simply will not appear; everything you approved keeps working normally.
To change what you approved, edit the source and choose to grant access again. You can also review what FitnessSyncer may see from your Google account permissions page.
Your daily summary can report either every calorie you burned including those your body uses at rest, or only the calories from activity. Which one you see is the ignore daily calories setting on the source, and moving to Google Health Web keeps whatever you had chosen.
If the number changed, check that setting on the source in question.
Nothing is deleted along the way, and you can return to the wizard whenever you like to move the rest.