Skip to main content
Question

Activity duration getting cut when syncing from Google Health/Fitbit to Strava

  • June 1, 2026
  • 1 reply
  • 41 views

Forum|alt.badge.img

Recently, the Fitbit app was rebranded and changed to the new Google Health app. Since this change, the activities I have recorded on these third-party apps have had the activity distance cut/reduced when syncing into the Strava app. *NOTE: title should say distance*

I am wondering if this is some sort of parsing issue which needs to be resolved, is a result of the app rebrand, or is a user-related issue I need to address. I have attached four runs, two during the Fitbit app (before the rebrand/change), and two during the Google Health app (after the rebrand/change). Run 1 and Run 2 respectively are essentially identical between the platforms with differences of 0.01 km, which I’m not fussed about. Run 3 is different by 340 metres and you can see the difference in start location on the Google Health map compared to the Strava map. Run 4 is different by 270 metres but the start locations are both correct. The activity durations between the platforms are only different due to how Strava handles elapsed time vs. moving time.

 

1 reply

Forum|alt.badge.img
  • Hub Starter
  • June 3, 2026

Just want to chime in I'm having similar issues after the Fitbit>GHealth change. 

My distance is correct but the GPS tracking is selective or starts at random places on my route. 

 

It also isn't smooth aka, it looks like I'm zig-zagging the whole time on a sidewalk.