> For the complete documentation index, see [llms.txt](https://docs.tryterra.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryterra.co/help-center/help-topics/data-api-sdk/provider-coverage-and-per-provider-data-availability/google-health-data-coverage.md).

# What data does Google Health deliver, and how does it differ from Fitbit?

Google Health delivers activity, sleep, daily, body and nutrition payloads, but some fields Fitbit fills, such as workout heart rate series, sleep heart rate and BMR calories, are not currently includ

**Google Health (`GOOGLE_HEALTH`) delivers activity, sleep, daily, body and nutrition payloads, but some fields Fitbit fills are not available.** On connect, Terra fetches up to the last 12 months, depending on what Google holds for the account. That history is returned by the REST API but isn't sent to your destination.

By payload:

* **Activity:** start and end time, duration, activity type, distance, average speed and pace, calories, steps, average heart rate and elevation gain. `metadata.name` carries Google's own exercise name, and `metadata.type` uses the same [activity types](https://docs.tryterra.co/unified-api/activity-types) as every other provider. There is no max heart rate, heart rate series or GPS route.
* **Sleep:** start and end time, time asleep and awake, light, deep and REM durations, a hypnogram and skin temperature deviation. There is no sleep heart rate or HRV.
* **Daily:** steps, distance, calories, floors, active minutes, resting heart rate, HRV, VO2 max, intensity minutes, heart rate zones and activity levels. There is no average, max or min heart rate and no step, heart rate or calorie series. BMR calories are not currently included in Terra's Google Health payloads.
* **Body:** weight, body fat, height, HRV, skin temperature and VO2 max.
* **Nutrition:** water intake only, with no meals or macros.

Blood pressure, blood glucose, body temperature and menstruation data are not currently included in Terra's Google Health payloads.

Things to handle in your integration:

* **Daily dates:** a daily payload covers a local calendar date from Google, stamped at midnight UTC with no offset. Treat it as a date. Converting it to another time zone shifts it onto the wrong day.
* **Activity and sleep times** are real instants in UTC.
* **Daily totals:** each daily payload carries the whole day's total so far. Replace the stored day rather than adding payloads together.

{% hint style="info" %}
If you pull data by API instead of receiving webhooks, request a window of several days each time rather than a single day. Workouts written into Google Health by other apps can arrive there days after they happened.
{% endhint %}