What Strava's Advanced Analysis Does That You're Not Looking At
Strava has more data than most users ever look at. Most people open the app, see the map, confirm their average pace, and close it. But beneath that surface layer lies a level of analysis that can completely change how you understand your training.
In this article I'll explain what advanced metrics Strava has, how to interpret them, and what information you can extract from your history to make better training decisions.
Heart Rate Zones: The Distribution Nobody Looks At
Every activity with HR data has a breakdown of time spent in heart rate zones. This distribution is far more informative than average pace or total distance.
What to look for in each session:
- How much time did I spend in zone 2 vs. zone 3?
- Was the time in the high zone intentional (intervals) or from accumulated fatigue?
- Was there cardiac drift (HR rising while pace stayed constant)?
Cardiac drift is especially revealing: if your HR rises 10–15 bpm over the course of an "easy" run without you changing pace, it means your cardiovascular system is under recovery stress, or the intensity was higher than appropriate for a base session.
Relative Effort: The Suffer Score in Context
Strava's Relative Effort is the modernized version of the Suffer Score. It combines time in HR zones with the athlete's recent history to produce a number that contextualizes the effort of the session.
The difference from the classic Suffer Score is that Relative Effort is compared against your personal history: a Relative Effort of 80 means something very different for someone whose sessions usually score 40–60 versus someone whose sessions typically come in at 100–120.
Strava also aggregates weekly Relative Effort and compares it to previous weeks, letting you see at a glance whether you're in a load week, a recovery week, or within your normal range.
Best Efforts: Your Real Performance Benchmarks
Strava automatically calculates your best times over standard distances (400m, 1km, 1 mile, 5K, 10K, half marathon, marathon) from all your activities, even if you've never raced those distances in an official event.
This is extremely useful because:
- You have a real performance reference without needing dedicated tests.
- You can see whether your Best Efforts are improving over time.
- You can detect which distances you're improving at fastest (which reveals something about your physiological profile).
If your 5K Best Effort hasn't improved in 3 months despite consistent training, that's an objective stagnation signal worth analyzing.
Segments: Much More Than Competing with Others
Strava segments are route sections where you can compare your times. Most people use them to compete with other athletes (KOM/QOM). But there's a far more valuable use: comparing your own times on the same segment over time.
If you have a climb segment on your regular route, your time progression on that segment is a free, contextualized performance test. Much more representative than an artificial test because you do it in real training conditions.
Training Load and Fitness: Strava's Fitness Model
With Strava Summit (paid version), you get access to the Fitness and Fatigue charts. These are equivalent to CTL and ATL from the TrainingPeaks model:
- Fitness: long-term average of Relative Effort (similar to CTL). Represents your accumulated fitness level.
- Fatigue: short-term average of Relative Effort (similar to ATL). Represents recent fatigue.
- Form: difference between Fitness and Fatigue (similar to TSB). Represents whether you're fresh or tired.
These charts let you see at a glance whether you're heading into a race week in good shape, whether you're accumulating too much fatigue, or whether you've been underloading for too long to maintain fitness.
External Analysis Tools That Integrate with Strava
Strava integrates with several more powerful analysis tools:
| Herramienta | Strength | Best for |
|---|---|---|
| TrainingPeaks | Full TSS/CTL/ATL model | Serious triathletes and cyclists |
| Intervals.icu | Very powerful free analysis | All levels |
| Garmin Connect | HRV, sleep, body battery | Garmin users |
| Iron Buddy | AI analysis + personalized plan | Athletes who want concrete recommendations |
The Problem of Data Without Interpretation
Strava has all this data. The problem is it shows it to you but doesn't tell you what to do with it. You can see your weekly Relative Effort was 350, but you don't know if that's too much, too little, or exactly what you needed for your goal.
The difference between having data and having useful information lies in contextualized interpretation: what weeks of training you've accumulated, what your goal is, what phase of the season it is, how you've responded to similar loads in the past.
That's exactly what Iron Buddy does with your Strava history: it connects the data, puts it in context, and gives you concrete recommendations. Not "train harder." But rather "this week you can fit in a threshold session on Tuesday because your Relative Effort over the last 7 days is below your average and you have 4 recovery days before your next long run."
Connect your Strava to Iron Buddy and turn your data into a concrete action plan.