How to: fitbit google health reconnect decision fork

Use this local guide before 2026-11-02+. Re-check official pages for authoritative dates. This site does not call vendor APIs or store your data on a server. Exports stay on your device.

1. Step 1. Note Nov 2 2026 legacy Fitbit Web API/OAuth turn-off returns 410 Gone on old endpoints
2. Step 2. Open Google Health and confirm recent data appears; use Needs Action / partner-apps guidance if listed
3. Step 3. For MyFitnessPal: Profile/More → Apps and Devices → Connected → Google Health → Connect; pick the same Gmail as Google Health
4. Step 4. Set Google Health as Primary Step Source under Steps (blue checkmark)
5. Step 5. If you already reauthorized with Google earlier, still complete MFP's own reconnect when prompted (double reauth)
6. Step 6. If steps/exercise missing GH→MFP while food MFP→GH works, treat as Known Issue (Investigating) per MFP Nov 4 update — not a missing reconnect alone
7. Step 7. For Strava: reconnect Google Health; expect forward-only sync; export TCX for historical activities if needed
8. Step 8. Verify at least one data type lands in the partner app after reconnect
9. Step 9. If Google Health itself has no data, contact Google — partner apps cannot invent missing device data

Related: FAQ · Use cases · Home tool. Always prefer official vendor documentation for authoritative dates.

Practical follow-along only — not an affiliate review, not medical advice, and not a replacement vendor console. Re-open official sources rather than trusting a cached screenshot.