> 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 BMR calories, are not currently included.

**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, heart rate (average, minimum, maximum and a heart rate series), heart rate zones (`LIGHT`, `MODERATE`, `VIGOROUS`, `PEAK`) and elevation gain. Swimming workouts also carry laps and stroke counts. `metadata.name` carries Google's own exercise name, and `metadata.type` uses the same [activity types](https://docs.tryterra.co/reference/health-and-fitness-api/data-models#activitytype) as every other provider; names without a match, such as `WEIGHTS`, come through as `OTHER`. There is no GPS route, cadence, power or max speed.
* **Sleep:** start and end time, time asleep and awake, light, deep and REM durations, a hypnogram, heart rate (average, minimum, maximum and a heart rate series), HRV (`heart_rate_data.summary.avg_hrv_rmssd` and `heart_rate_data.detailed.hrv_samples_rmssd`), breathing rate and skin temperature deviation (`temperature_data.delta`), when the device recorded them.
* **Daily:** steps, distance, total and active calories (`net_activity_calories`), floors, elevation gain, active and inactive time, average, minimum, maximum and resting heart rate, HRV, oxygen saturation, VO2 max, intensity minutes, heart rate zones and activity levels, plus step, heart rate and calorie series. BMR calories are not currently included in Terra's Google Health payloads.
* **Body:** weight, body fat, height, heart rate (average, minimum and maximum), HRV, oxygen saturation, blood glucose, skin temperature and VO2 max.
* **Nutrition:** water intake only, with no meals or macros.
* **Athlete:** age only.

Blood pressure, 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 the user's local midnight with its UTC offset. When the user's offset isn't known, the day is stamped at midnight UTC. Treat it as a date. Converting it to another time zone shifts it onto the wrong day.
* **Activity and sleep times** are real instants, carrying the user's UTC offset when Google provides it.
* **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 %}
