🏠 Running Data Plan

Strava connection & CGM data

Why connect Strava to Running Data Plan?

Running Data Plan does not replace Strava. Athletes continue to use Strava to record, centralise and share their activities. Running Data Plan adds a personal, glucose-focused analysis by matching an authorised activity with measurements retrieved separately from the athlete’s compatible CGM source.

Strava

Record and share the activity

The watch or application records the workout. Strava centralises the activity and retains its own tracking and sharing features.

Running Data Plan

Add glucose context

The application separately synchronises CGM readings, aligns them with the workout timeline and creates complementary charts and indicators.

A complementary application, not a copy of Strava

Running Data Plan does not reproduce Strava’s social feed, segments, clubs, challenges or community features. Its purpose is to help a connected athlete review their own activities using context that Strava does not provide: CGM readings, glucose ranges and their timing relationship with elevation, pace, heart rate or power.

An athlete’s Strava data is displayed inside that athlete’s own Running Data Plan account. It is not used to display other athletes’ activities and is not sold to third parties.

Connection

How to connect a Strava account

  1. Create a Running Data Plan account and open Account.
  2. Select the official Connect with Strava button.
  3. Review and accept the permissions displayed by Strava.
  4. After returning to Running Data Plan, newly authorised activities can be processed automatically. Older workouts can be imported manually as GPX or FIT files.
  5. You can disconnect Strava from your Running Data Plan profile and manage authorised applications from your Strava account.

Data sources

What Strava provides—and what it does not

Strava activity dataSport type, timestamps, duration, distance, elevation and description, plus timeline, GPS, altitude, heart rate, cadence, speed, moving status, power, grade and temperature streams when available and authorised.
CGM dataGlucose readings and trends available from LibreLinkUp, Dexcom Share, CareLink or Nightscout. This information is retrieved separately and never comes from Strava.
Matching processRunning Data Plan uses the activity start time and timeline to associate available CGM readings with the corresponding moments in the workout. Missing readings are never invented.

If a field is absent—for example heart rate, power or GPS—the related indicator cannot be calculated.

Private analysis

Indicators created by matching Strava and CGM data

  • Glucose summary: start, finish, average, minimum and maximum glucose, plus time in the configured range.
  • Synchronised charts: glucose positioned on the workout timeline and, when possible, by distance.
  • Course profile × glucose: context during climbs, descents and flatter sections.
  • Pace × glucose and VAM × glucose: readings viewed alongside movement speed or vertical speed.
  • Heart rate × glucose: heart rate, intensity zones and observed average glucose by zone when enough data exists.
  • Terrain-adjusted cardiac drift and a personal history used to improve future race projections.
This is not a medical device. The analysis does not replace CGM alarms, treatment decisions or professional medical advice.

Optional update to Strava

What can be added to a Strava description?

Under Account → Enrich Strava, the athlete chooses whether Running Data Plan may supplement new activity descriptions. Depending on the sport and available data, the block may include glucose summary values, running pace and VAM, elevation gain, cycling speed, cadence or power, plus a link to the athlete’s private analysis.

Example of a Strava description enriched with average glucose, target range, start and finish values, best paces and longest climb
Illustrative example of the block added to a running activity. The screenshot is shown in French; the actual lines depend on the data available for that activity.

The athlete’s existing text is preserved. Running Data Plan replaces only its previous automatic block to prevent duplicates.

Privacy reminder. A Strava description may be visible according to the activity’s privacy settings. Athletes who do not want to publish a glucose summary can disable automatic description enrichment.

Permissions and control

Why are read and write permissions requested?

The connection requests activity:read_all to retrieve authorised activities and streams, and activity:write to update a description when enrichment is enabled. Running Data Plan does not use these permissions to replace Strava or publish a competing social activity.

Athletes can disable description enrichment, disconnect Strava and contact support about their data.

Strava references

Official documentation

Running Data Plan is an independent application using the Strava API. It is not developed, sponsored or endorsed by Strava.