Strava Analytics: The Numbers Your Activity Feed Doesn't Show You
Strava records every run, ride, and swim you do. But the feed stops at one activity at a time. Here's how a private analytics dashboard turns that history into trends you can actually read.
The gap between one activity and a training block
You finish a tempo run. You open Strava, check your splits, glance at the heart rate graph, maybe scroll through kudos. Then you close the app.
You just looked at one activity. What you actually want to know is how it fits: whether that tempo pace was right for where you are in your training cycle, whether your heart rate was higher than it was last week at the same pace, whether the last three weeks of mileage add up to a sensible ramp.
That is not a knock on Strava. Strava was built to record and share activities, and it does that well. But an activity feed is a list, and the useful signal in endurance training is longitudinal. It lives in the comparison between this month and the last three.
What shows up when you chart the whole history
When you connect Strava to athletedata.health, your activities are pulled in and displayed on your own analytics dashboard - the detailed data, not just the summary card. Here is what that surfaces.
Aerobic efficiency. The relationship between pace and heart rate at steady state is one of the better markers of fitness progress for endurance athletes. It moves slowly, over weeks and months, which is exactly why you cannot see it one activity at a time. Charted across a year, the trend is obvious.
Intensity distribution. Most self-coached athletes think they train polarized and actually train in the middle. Your dashboard buckets every activity by heart rate or power zone and shows you the real split, week by week. It is a common surprise.
Volume ramps. The 10% weekly increase rule is a rough guideline. Your dashboard tracks your actual acute-to-chronic workload ratio instead. Research by Tim Gabbett (British Journal of Sports Medicine, 2016) showed that keeping this ratio between 0.8 and 1.3 is associated with lower injury risk. The chart shows where you sit rather than leaving you to estimate.
Pacing patterns. Most runners start too fast, and it is one of the most consistent patterns in recreational running. Lined up across your longer efforts, split-by-split, your own pattern is easy to read.
Where your Strava data goes, precisely
This is worth being exact about, because "connect your accounts" usually hides a lot.
Your Strava data is used for two things on athletedata.health:
- It is displayed back to you on your own analytics dashboard. Only you can see it.
- With your consent, we add one short line to the description of new activities you record, noting that the activity was coached through athletedata.health. This is a single click to switch off in your profile settings, and switching it off stops every future write to your Strava account.
That is the whole list. Your Strava data is never provided to AI models, MCP servers, or third-party platforms and tools. It is never shared externally, and it is never used for model training. Disconnecting Strava from your integrations page revokes our access immediately.
Where the coaching data comes from instead
athletedata.health does offer an AI coach, and it is worth being clear that it does not read your Strava data.
The coach runs on your device and wearable connections - Garmin, Apple Health, WHOOP, Oura, COROS, Polar, Suunto, and others. Those sources carry the things coaching actually depends on and Strava does not have: sleep stages, overnight HRV, resting heart rate trends, readiness scores, and full multi-year history.
That separation is deliberate. Activity data shows what you did during a session. What happened between sessions is where adaptation occurs, and that is wearable territory.
What you need to get started
Connecting Strava takes about two minutes:
- Create an account on athletedata.health
- Connect Strava from the Strava integration page - you'll authorize access through Strava's standard OAuth flow
- Your activity history imports immediately. New activities sync automatically going forward.
If you also want coaching rather than only analytics, connect a device or wearable source alongside it.
Who this works well for
A Strava analytics dashboard is most useful for self-coached athletes who train consistently and have a couple of years of history sitting in Strava already. If you run or ride 4-6 days a week, the data is there. You are just seeing it one row at a time.
It is less useful if you already work with a human coach who reviews your training regularly, or if you have only been logging for a few weeks - trends need a bit of history before they say anything.
