How to set up Strava for training: the one-time configuration that makes every metric honest
Setting up Strava for training is a four-step configuration you do once: enter a real FTP and a measured max heart rate instead of formula estimates, anchor your zones to those numbers, commit to one consistent sensor stack so your load data is comparable, and set the feed and privacy so they protect your training instead of steering it. Strava syncs your data faithfully but does not audit whether the inputs are right [Meyer 2018]. The thirty minutes you spend on these settings is what keeps every downstream number — time-in-zone, Relative Effort, the Fitness curve — describing your physiology rather than an arithmetic guess.
By Jim Camut · Former pro & ex-Bruyneel Academy racer
Updated Jun 1, 20264 chapters7 citations
Enter a real FTP and max HR, not a formula estimate
The two anchor numbers Strava scales everything else to are your FTP and your max heart rate. Both default to estimates — max HR from the 220-age formula, which carries a standard error near 10 bpm and can miss an individual by 10-20 [Tanaka et al. 2001]. Replace both with observed values before you trust a single downstream metric.
Functional Threshold Power is the highest power you can hold in a quasi-steady state for roughly an hour, the boundary Andrew Coggan defined between heavy and severe intensity [Allen et al. 2019]. It is the denominator of intensity factor and the reference your power zones scale to, so a wrong FTP miscalibrates every workout. You do not need a formal test to seed it honestly — your last 90 days of power files already contain a best 20-minute and best 60-minute effort to anchor a defensible estimate. The point here is not which test to run; it is to put a real number in the field rather than leaving a placeholder.
Max heart rate is the other master input, and its default is statistically weak. Tanaka and colleagues analyzed 351 studies covering 18,712 subjects and found 220-age systematically underestimates max HR in older adults; even their improved 208 minus 0.7-times-age equation carries a standard error near 10 bpm [Tanaka et al. 2001]. For any one rider, a formula-derived max can sit 10-20 bpm from the true ceiling. Set it instead from the highest heart rate you have actually seen in a hard, warmed-up effort over the last few months — the top of a 5-minute climb or the final seconds of a maximal sprint.
Enter both before your first structured week, not after. Every ride Strava processes is scored against whatever anchors are in place at upload time, and correcting them later generally does not rewrite scores already sitting on past activities [Meyer 2018]. A few minutes spent on two fields up front saves you a Fitness curve with a seam in it three months from now.
Set your zones so every downstream metric is honest
Once the anchors are real, decide how your zones derive from them. Strava builds heart-rate zones as percentages of max HR by default; the more individualized option anchors the threshold zones to lactate threshold heart rate, which Joe Friel's framework treats as the better reference because it tracks a metabolic event rather than an age-based ceiling [Friel 2018].
Power zones scale off FTP and heart-rate zones scale off the max or threshold anchor, so the zones are only as honest as the numbers from the previous step. If your max HR is 15 bpm low, an endurance effort that should read mid-zone-2 logs as low zone 3, and your time-in-zone splits misreport where you actually trained. That distortion then propagates: Relative Effort sums weighted time-in-zone with higher zones counting for far more per minute [Meyer 2018], so a shifted boundary mechanically inflates or deflates the score, and that score feeds the Fitness curve when you ride without power. We walk through that full cascade in our companion piece on what happens when your Strava heart-rate zones are misconfigured.
For the configuration itself, two defensible paths exist. The simpler one: correct the max HR in settings and let Strava regenerate its percentage-based zones — most of the accuracy gain for a few minutes of work. The more precise one, if you have done a threshold field test, is to enter custom boundaries from your lactate threshold heart rate using Strava's draggable zone editor [Friel 2018]. Either beats the default. Do not blend them across the season — pick one zone model and hold it, so a ride from March and a ride from August are measured against the same ruler.
Heart-rate zones are not a substitute for what power measures, either. Heart rate lags intensity and drifts with heat, fatigue, and caffeine; power records mechanical work directly. If you have a meter, treat power zones as your primary reference and heart-rate zones as the backup for outdoor rides — but configure both, because Strava scores whatever stream a ride carries.
Commit to one sensor stack so your load data is comparable
Load data is only comparable if it comes from the same instruments. Two validated power meters can disagree by a couple of percent in steady work and far more in sprints [Nimmerichter et al. 2017], so switching stacks mid-season introduces an offset that can rival a real fitness change. Pick one primary stack and hold it.
Nimmerichter and colleagues compared a Garmin Vector against the SRM laboratory standard and found no significant difference in steady power output, with both showing good reliability at a coefficient of variation under 3% — but 1-second peak power differed by limits of agreement near 19 W, and sprint agreement was meaningfully lower [Nimmerichter et al. 2017]. The lesson for a self-coached rider is not that one meter is wrong; it is that even two accurate devices are not perfectly interchangeable, and the discrepancy lands hardest on the short, sharp efforts.
The practical failure mode is mixing data types, not just devices. If you train indoors on a smart trainer's power and outdoors on heart rate only, your Strava load looks like two different athletes — the chart shows a discontinuity that reflects the sensor switch, not your body. Decide on one primary load metric: power-based TSS-equivalent if you have a meter on every ride, or Relative Effort scored against correct HR zones if you do not. Hold it across the block so the Fitness curve measures training, not instrumentation.
Reading both streams correctly is exactly the gap between syncing data and using it, the broader case our pillar on training with Strava keeps returning to. Strava records faithfully but does not reconcile a power ride against a heart-rate ride. AdaptCycling reads both streams from your full Strava history and computes an internal load estimate that does not whipsaw when the sensor stack changes, so one indoor-power block followed by an outdoor-HR block reads as continuous training rather than a fictional fitness jump.
Set the feed and privacy so they protect your training
The last configuration step is social, and it is load-bearing. Strava's feed uses the same variable-reward design that makes social apps compulsive [Strava 2024], which steers self-coached riders toward matching the feed instead of their plan — quietly inverting the roughly 80/20 easy-hard balance endurance training is built on [Seiler 2010].
The mechanism is behavioral, not physiological. A 90-minute zone 2 ride at 165 watts is correct training that earns fewer kudos than a 230-watt group ride, so riders who structure around the feed drift toward one intensity: hard enough to look like work, never easy enough to count as recovery. Stephen Seiler's intensity-distribution research is clear that well-trained endurance athletes spend roughly 80% of training time easy [Seiler 2010]; matching the feed inverts that ratio one ride at a time.
Configure against it once. Strava's privacy controls let you set activity visibility — followers-only or no-feed-post — without losing any data on your own dashboard. If seeing the kudos count on a slow ride pushes you to ride harder than the plan calls for, hide those rides from the feed by default. The data stays; only the social proof goes. Some riders disable the activity feed in the app entirely and report the behavioral pull drops within about two weeks.
Quick answers
What should I configure in Strava before I start training with it?
Do I have to take an FTP test to set up Strava properly?
Why does Strava ask me to pick max HR or lactate threshold for zones?
Does it matter if I switch power meters or use HR sometimes and power other times?
Should I make my training rides private?
Sources cited in this guide
- 01
- 02Tanaka et al. 2001. Age-predicted maximal heart rate revisited. Journal of the American College of Cardiology.
- 03
- 04
- 05Nimmerichter et al. 2017. Validity and Reliability of the Garmin Vector Power Meter in Laboratory and Field Cycling. International Journal of Sports Medicine.
- 06Seiler 2010. What is best practice for training intensity and duration distribution in endurance athletes?. International Journal of Sports Physiology and Performance.
- 07
More inside Training with Strava
Start here · Foundational guide
Training with Strava: a self-coached cyclist's guide
How to use Strava as a training tool — what its metrics actually tell you, where it fails, and how to structure training around it without a coach.
Read the full guide
Other articles in this series
- 01
What your Strava Fitness number means (and if yours is good)
Strava Fitness is CTL — a 42-day weighted load average. What the number means, why it is personal, and the decisions to make from it.
- 02
Apps that connect to Strava: read vs display
How to tell which training apps actually read your Strava data and adapt versus the ones that only display your rides.
- 03
Is Strava Premium worth it for a self-coached cyclist?
What Strava Premium gives a training-focused rider, what it doesn't (no coaching), and when the free Intervals.icu chart beats paying.
- 04
Relative Effort vs TSS: which to trust by workout
A per-workout-type rule for when to trust Strava Relative Effort vs power-based TSS, and why they are not the same units.
- 05
Strava segments as fitness tests: map efforts to tests
Use Strava segments as scheduled benchmark tests: which profiles map to which test, how to schedule every 4-6 weeks, and controlling variables.
- 06
What to look at on Strava after a ride: 4 metrics
A 30-second post-ride routine: the four Strava metrics that matter after every ride, the ones to ignore, and why.
- 07
Strava Fitness going down while training hard: the decay math
Why your Strava Fitness (CTL) drops even when you train hard: the 42-day EWMA decay math, the real causes, and when a falling line is correct.
- 08
Strava indoor power vs outdoor HR: Fitness chart jumps
Mixing power-based TSS and HR-based Relative Effort splices incompatible units into your Strava Fitness chart. Why it jumps and how to fix it.
- 09
Heart rate drift on long rides at same power: what it means
Why heart rate climbs at flat power on long rides — cardiovascular drift, aerobic decoupling (Pw:HR) as a durability signal, and what to do.
- 10
Strava heart rate zones wrong: the whole-dashboard cascade
How a wrong max HR in Strava cascades into bad zones, Relative Effort, and Fitness — and how to set zones from real data.
- 11
Why your Strava Relative Effort is high on easy rides
Relative Effort can spike on a genuinely easy ride — usually a mis-set max HR, not lost fitness. What inflates it on Strava and what to do.
Free 14-day trial · No card · ~3 minutes
Try the adaptive coach yourself.
Connect Strava, tell us your goal and weekly hours, and your first training week is ready in minutes.
Free 14-day trial. No credit card required.