If your Fitbit is missing from Google Health, check four things in order: the account you signed into, the connected-device list, whether new data is syncing, and the date or metric you are viewing. An empty screen does not by itself mean your records are deleted. Keep the tracker and existing account intact while you establish where the connection stops.
A device can still count steps on your wrist while the phone displays yesterday's information. That difference is useful evidence. It tells you to investigate the path from the tracker to the account before treating the screen as the complete record.
Think of the connection as four stages
The practical sequence is device, account, sync, then display. The device records supported activity. The correct account needs to recognize the device. A connection must transfer the data. Finally, the app has to display the right metric and period.
Check the simplest visible evidence at each stage. Is the tracker charged and showing recent activity? Does the account name look familiar? Does the device appear in Connections? Are you looking at today, last week, or a different metric?
Do not skip straight from "I cannot see my steps" to "I need a new tracker." A purchase cannot correct a mistaken sign-in or a hidden date filter. Equally, an active screen on the tracker does not prove every connection is healthy.
Confirm the account before pairing again
Inspect the profile in Google Health and compare it with the account you used previously. If you have several Google accounts on the phone, write down which one is currently selected. Use your own account records to establish the correct identity rather than trying unrelated accounts at random.
Google's current app guide directs users to Connections, then the device. Open that list and look for your exact model. A similarly named device or an old watch you no longer use is not confirmation that the tracker on your wrist is connected.
If the device is absent, use the current setup guidance for that model. Record any message saying that it is linked elsewhere or that setup cannot finish. Do not erase the tracker to get past a message you have not understood.
Separate missing history from failed new sync
| What you observe | What to check next |
|---|---|
| Device absent, history present | Device setup and ownership under the current account |
| Device present, today's data stale | Connection, permissions, power, and sync status |
| New data present, older dates empty | Account identity, metric, date range, and data source |
| Some metrics update, others do not | Whether the device supports and recorded the missing metric |
This is a troubleshooting worksheet, not a diagnosis. More than one issue can be present. Its purpose is to identify the next useful check instead of repeating the same restart after every symptom.
For a simple test, note the time and the step total shown on the tracker. Keep the charged device near the phone, open the app, and follow its normal sync process. Compare the same metric and date afterward. Record what changed and what stayed the same.
Check the phone-side connection
Google publishes separate syncing instructions for Android and iPhone, with model-specific branches. Start with the common reversible checks: Bluetooth enabled, a usable internet connection, adequate device charge, an updated app, and the tracker near the phone. Restart the phone or app if the appropriate official instructions call for it.
On Android, inspect Google Health's requested permissions and the model-specific guidance for Bluetooth or nearby-device access. On iPhone, inspect the Bluetooth permission and relevant app settings. Permission labels depend on the operating system. Do not grant unrelated access merely because a forum comment says to enable everything.
A Pixel Watch can also involve the companion Pixel Watch app, while a Fitbit tracker follows its own setup. Use the branch for the device you own. Instructions for an Aria scale or another model should not be treated as interchangeable tracker instructions.
Protect records before bigger changes
If basic checks fail, pause before uninstalling software, removing devices, or resetting hardware. Find out which records have synced and which may exist only on the device. Ask support about preservation when that distinction is unclear.
Review Google's current export guidance for your account if historical records are important to you. An exported archive is useful only if you can locate and open it. Keep a private copy of the support case and any dates that are missing.
Never share a full health-history screenshot publicly to prove that a chart is blank. A cropped view showing the relevant date, empty metric, and app version is usually a better starting point. Share sensitive details only through the provider's official support process when needed.
Send support a report they can follow
Prepare the device model, phone model, operating system, app version, last successful sync date, and the exact symptom. Add the steps you already tried and their results. Separate "device not listed" from "device listed but no new data."
A useful message is: "My tracker appears in Connections, but today's steps have not updated since [time]. The tracker shows [amount]. I checked the selected account, Bluetooth, power, and date range. The app version is [version]. What should I check next without losing unsynced records?"
If support confirms a compatibility limit, then compare replacement devices. Check phone compatibility, the metrics you need, historical-data export, and any continuing subscription cost. Replacing hardware should answer a confirmed limitation, not just the frustration of an unfamiliar screen.
FAQ
Does seeing my Fitbit in the phone's Bluetooth list prove it is set up?
No. Check the device inside Google Health as well. A Bluetooth listing alone does not demonstrate that the correct account is receiving and displaying current activity. Compare a recent metric after the documented sync process.
Should I factory-reset the tracker first?
Start with account, connection, and display checks. Before any reset, establish what happens to unsynced information for your specific model. If you cannot confirm that, ask official support rather than using a reset as a guess.
Can a new tracker bring back missing history?
A new device does not automatically resolve an account or historical-data problem. Investigate the existing records separately. Consider a replacement when a supported check establishes incompatibility or hardware failure, and review export and ongoing costs first.
