Strava and moving time implementation

[robintrum]

Dear all,

Used my fitbit for the first time during my long run. Strava is perfectly synced with Fitbit. Unfortunately Fitbit syncs the elapsed time instead of the moving time. The moving time is crucial in Strava because it calculates the exact average running speed. My moving time is about 4 minutes shorter than my elapsed time because I had to stop at a traffic light. Therefore my average page on Strava is a lot faster compared to Fitbit. This is the exact average speed which I have runned, not the one on Fitbit.

Is there a possibility to sync the moving time instead of the elapsed time with Fitbit from Strava? A feature I am really missing at the moment because my data and training progress is now inaccurate. 

Hoping that somebody could help me, thanks!

Greetings,

Robin

Moderator Edit: Updated Subject For Clarity.

[RobertoME · Accepted solution]

Hi there @robintrum, its nice to see new faces around. With third party integrations is a bit tricky, although I appreciate your suggestion and I will share this with our teams. Many of this integrations are not developed by our initiative, but by the third party service who use our open API to integrate Fitbit.

Strava and Fitbit at the moment only syncs the following:

• Exercises with GPS data recorded with Fitbit will be sent to Strava. Heart rate data will be included when it's available
• Exercises recorded with Fitbit's app or devices that do not include GPS data are NOT currently sent to Strava.

For more suggestions and details you can also visit http://strava.fitbit.com/

Hope to see you again and thank you for your feedback.