To get started, go to Smashrun - Stats for runners, select the app or device you’re testing, enter your account credentials, and click on “Connect” to give Smashrun permission to import your runs.
Test and make sure that:
- you can authenticate your account without any issues
- only running activities are imported
- if applicable, the running segment of a multi-sport activity shows up
- pauses don’t show up for runs w/o pauses
- details are imported for GPS runs (includes map and pace graph)
- the timestamp/timezone of the run is correct
A few things to keep in mind:
- Duplicate runs: If your runs for any of these apps/devices were already previously imported through Garmin, TomTom, or were manually uploaded, you’ll need to set a minimum import date to avoid duplicating your runs.
- Elevation correction (for Pro users): By default, newly imported runs are not corrected for elevation. If you’re wearing a device with a barometric altimeter, then we’ll use the elevation data from the device. If you’re using an app, make sure you enable elevation correction before syncing your runs.
For all integrations, Smashrun will only import running activity types. Depending on the app or the device, you can expect the following once you’re authenticated:
-
MapMyRun
- Note that only running activities will be imported into Smashrun.
- Pay particular attention to the way pauses are handled. This code was tricky and their may be issues.
-
Suunto
- The Suunto Workout API will retrieve your running activities from the Suunto app, but not the Movescount website. If you need to migrate your runs from Movescount to the Suunto app, you should check out Suunto’s Digital Service Transition.
-
Polar
- If you marked an activity as “running” but it doesn’t have any pace data or a map, we’ll only show the summary details of the activity.
-
Fitbit
- You will need to check “location and GPS” in order to import your run details from Fitbit.
- If you marked an activity as “running” but it doesn’t have any pace data or a map, we’ll only show the summary details of the activity.
- Note that Fitbit has a rate limit of 150 API requests per hour per user, so if you have more than 150 runs (and you’re also tracking other activity types), it could take more than an hour to sync the details of your entire running history.
-
Strava
- If you only have Garmin runs in Strava, you should set today as your minimum import date. This will prevent you from accidentally reimporting any runs you may have already deleted on Smashrun, but are still on Strava.
- By design, Strava’s API does not delineate where pauses occur, only that they occurred. So Smashrun uses a pause detection algorithm, which could result in a slightly different distance, duration, and/or pace.
** To submit a bug, please provide a detailed description of the issue.**
- Always search before submitting a bug to avoid duplicates
- Create a topic under Testing New Integrations
- Mention which app or device you’re using
- Include screenshots, when applicable
- Attach the original file export, if it’s a data issue for a specific run
- Always note if there are any known pauses during your run