The Problem with Tracking Races in Strava (And What to Use Instead)

You’re scrolling through your Strava profile trying to find that half marathon you ran last spring. You remember it was a PR, but which activity was it? You scroll past dozens of training runs, tempo workouts, and easy days. Was it March? April? You keep scrolling.

Or someone asks about your marathon times, and you realize your race results are buried somewhere in 300+ activities per year. You could search by date if you remember when the race was, but otherwise you’re manually scanning through months of training runs.

Or you’re setting goals for an upcoming marathon and realize you have no easy way to see your past marathon results in one place. They’re scattered across your activity feed, mixed with every training run and recovery jog from the past three years.

Here’s the thing: Strava is brilliant for tracking daily training. It’s the gold standard for logging runs, analyzing pace and elevation, sharing with friends, and staying motivated through the social feed.

But Strava wasn’t built for tracking race history. And if you’re using it as your primary race log, you’re discovering the limitations.

Here’s why Strava falls short for race tracking—and what serious racers use alongside it.

Strava is Great—For What It Was Built For

Before diving into limitations, let’s acknowledge what Strava does brilliantly:

• Daily training tracking: Every run logged automatically via GPS watch sync
• Detailed analytics: Pace, elevation, heart rate, splits
• Social motivation: Kudos, comments, following friends
• Segment tracking: PRs on specific routes
• Training consistency: Weekly mileage, streaks, activity calendar

For daily training, Strava is unbeatable. Most serious runners should use it.

But Strava is a training log, not a race log. And the difference matters.

The Race Tracking Problems with Strava

1. Races Get Buried in Your Activity Feed

Your Strava profile shows a chronological feed of every activity. Training runs, races, bike rides, cross-training—all mixed together.

If you run 5 times per week, that’s 260 activities per year. Your 3-4 races per year are buried in that feed, indistinguishable from regular training runs unless you click into each activity.

Want to see your last five marathon results? You’re scrolling and clicking, scrolling and clicking.

The impact: Your race history is technically in Strava, but functionally invisible. You can’t see race progression at a glance.

2. No Dedicated Race View

Strava doesn’t have a “races only” filter or view. There’s no way to see just your race activities separated from training.

You can tag activities as “races,” but even then there’s no race-specific dashboard. Your tagged races are still buried in the main activity feed.

Compare this to any purpose-built race tracking tool, which shows races in a clean list or timeline view. In Strava, races are just activities that happen to be races.

The impact: You can’t easily see your race history timeline, compare races, or identify patterns across your racing career.

3. No Automatic PR Tracking Across Races

Strava tracks segment PRs brilliantly—fastest time on specific routes. But it doesn’t track race PRs across all your 10K races, half marathons, or marathons.

If you want to know your marathon PR, you need to:

• Remember it (risky)
• Manually check each marathon activity
• Keep a separate list outside Strava

When you finish a new 10K, Strava won’t tell you if that’s a PR compared to your other 10K races. You have to check manually.

The impact: You might set PRs without realizing it, or forget what your actual PRs are. Strava doesn’t give you this information automatically.

4. No Goal Setting Per Race

When you register for a marathon, you set goals: A goal (best case), B goal (realistic), C goal (minimum acceptable). This is standard race strategy.

Strava has no place to record these goals. You can’t attach pre-race goals to activities, compare them to actual results, or track whether you typically overshoot or undershoot your goals.

Your goals live in your head or a separate notes app—not integrated with your actual race data.

The impact: No way to learn from goal-setting patterns. Did you train for 3:30 but run 3:45? That’s valuable data, but Strava doesn’t capture the relationship between goals and results.

5. No DNS, DNF, or DQ Tracking

Did Not Start (DNS), Did Not Finish (DNF), and Disqualified (DQ) are part of every serious racer’s history. Sometimes you get injured before the race. Sometimes you drop out at mile 18. Sometimes you miss a cutoff.

These races matter—they’re part of your story and contain lessons. But there’s no good way to track them in Strava:

• DNS: No activity to log (you didn’t run)
• DNF: Activity shows partial distance, but no clear “DNF” status
• DQ: Looks like a completed race with no indication of disqualification

The impact: Your complete race history has gaps. The races you didn’t finish or didn’t start aren’t tracked anywhere, even though they’re important data points.

6. Race Notes Mixed with Training Notes

Strava lets you add descriptions to activities. You can write notes about your race—how you felt, what went wrong at mile 20, the weather conditions.

But these notes are the same as notes on any training run. There’s no race-specific structure or prompts. And race notes are mixed with training notes in your activity feed.

Want to look back at your marathon race notes from the past three years? You’re clicking through individual activities, hoping you wrote something meaningful.

The impact: Race memories fade because there’s no dedicated place to capture them. Your race notes compete with training run comments.

7. No Race-Specific Export or Sharing

Want to share your race history with a coach? With Strava, you either:

• Give them full Strava access (they see everything, not just races)
• Manually screenshot individual race activities
• Export all activities and manually filter for races

There’s no “export just my races” option. No way to create a race resume or race-specific data export.

The impact: Sharing your race history is awkward. Coaches and training partners can’t easily see race-specific progression.

8. Can’t See Race Progression Timeline

The best part of tracking races is seeing progression over years. Your first nervous marathon. The breakthrough race where you qualified for Boston. The comeback race after injury.

Strava shows you a chronological activity feed, but not a race-specific timeline. You can’t easily see:

• How your marathon times have improved over 5 years
• Your race frequency and patterns
• Which years you raced more or less
• Progression across different distances

The impact: You lose the narrative. Your race history exists in Strava but doesn’t tell a clear story.

The Solution: Strava + Race-Specific Tool

This isn’t an either/or choice. You don’t have to stop using Strava. In fact, you shouldn’t—it’s excellent for daily training tracking.

The solution is using both tools for different purposes:

• Strava: Daily training log (runs, workouts, cross-training)
• Dedicated race tracker: Race history, goals, PRs, progression

Think of it like using different tools in your kitchen. A chef’s knife is perfect for chopping vegetables, but you don’t use it to spread butter. Different tools, different jobs.

What a Purpose-Built Race Tracker Does

Race-Only View

See just your races in a clean list or timeline. No training runs cluttering the view. Just race history.

Automatic PR Tracking

The system knows your PRs across all distances instantly. When you log a new race, it tells you if it’s a PR. No manual checking.

Goal Tracking

Set A/B/C goals before each race. After the race, compare goals to actual results. Over time, see patterns in your goal-setting accuracy.

DNS/DNF/DQ Status

Track races you didn’t start, didn’t finish, or were disqualified from. These are part of your complete race story.

Race-Specific Notes

Dedicated space for race memories—weather, how you felt, what worked, what didn’t. Not mixed with training run notes.

Timeline and Progression View

See your race history as a story. Progression charts, frequency patterns, improvement over years.

Race-Specific Export

Export just your race data to share with coaches, include in applications, or back up separately from training data.

Integration with Strava

The best race tracking tools integrate with Strava—automatically import race activities so you’re not manually entering data twice.

Options for Race Tracking

Dedicated Race Tracking Apps

Tools built specifically for tracking race history:

• RunningLog: Built for serious racers—goal tracking, PR detection, Strava integration, A/B/C priorities, DNS/DNF/DQ status
• Athlinks: Aggregates race results from timing companies (free but limited to official race results)

Training Platforms with Race Tracking

These are more training-focused but include race logging:

• Final Surge: Training log + race calendar (more coach-oriented)
• TrainingPeaks: Comprehensive training platform (expensive for casual use)

Custom Solutions

Some runners build their own systems in Notion, Airtable, or other database tools. More work to set up but highly customizable.

Why I Built RunningLog as a Strava User

I’ve used Strava daily since 2017. Every run, every workout, every race automatically syncs from my Garmin to Strava. I love the platform.

But I kept hitting these exact frustrations when trying to track my race history in Strava:

• Couldn’t see just my races without scrolling through hundreds of training runs
• Had to manually check each race to remember my PRs
• No place to set race goals and compare them to results
• Race memories got lost in activity descriptions
• Couldn’t track DNS or DNF races

So I built RunningLog specifically for race tracking—designed to work alongside Strava, not replace it.

Key features:

• Strava integration: Automatically import race activities (no double entry)
• Race-only view: See just your races, not 300+ training runs
• Automatic PR tracking: Know your PRs across all distances instantly
• A/B/C goal priorities: Set multiple goals per race, track success rate
• DNS/DNF/DQ status: Track your complete race history
• Race notes: Dedicated space for memories and lessons
• Export anytime: CSV/Excel export of just race data

I still use Strava every day for training. But RunningLog is where my race history lives.

How to Use Both Tools Together

The Workflow

1. Training runs sync to Strava automatically (from GPS watch)
2. Races also sync to Strava automatically (same process)
3. Race activities import to RunningLog via Strava integration (automatic or one-click)
4. Add race-specific details in RunningLog: goals, notes, status
5. View training in Strava, races in RunningLog

What Lives Where

• Strava: Daily training runs, workouts, pace/elevation analysis, social activity, training consistency, segment PRs
• Race tracker: Race history, race goals, race PRs, race progression, race notes, DNS/DNF/DQ tracking

No Double Entry Required

The key is integration. You’re not manually entering races twice. The race data flows from your GPS watch → Strava → race tracker automatically.

You just add the race-specific context (goals, notes, status) that Strava doesn’t capture.

Common Questions About Using Both Tools

“Isn’t it redundant to use two tools?”

Only if the tools do the same thing. Strava and a race tracker serve different purposes. It’s like asking if it’s redundant to own both a refrigerator and a microwave—different tools for different jobs.

“Can’t I just tag races in Strava?”

You can tag activities as races in Strava, but that doesn’t give you race-specific views, PR tracking, goal comparison, DNS/DNF status, or any race-focused features. The tag exists, but the functionality doesn’t.

“What if I only race a few times per year?”

That’s exactly when race tracking matters most. If you only run 2-3 marathons per year, each race is significant. You want those races properly tracked and remembered—not buried in 260 training activities.

“Do I need to pay for both Strava and a race tracker?”

Strava’s free tier works fine for training tracking. Many race trackers (including RunningLog) offer free tiers covering recent race history. You can use both tools at zero cost.

The Bottom Line

Strava is the best tool for daily training tracking. Keep using it. Love it. Collect those kudos.

But Strava isn’t a race tracking tool. It’s a training log that happens to include races. And if you’re serious about racing—if you set goals, chase PRs, and want to see progression over years—you need something built specifically for race tracking.

The solution isn’t choosing between Strava and a race tracker. It’s using both:

• Strava for training (what it does brilliantly)
• Race tracker for races (what Strava wasn’t built for)

Your training runs belong in Strava. Your race history deserves something better.

Keep using Strava for training, add RunningLog for races. Connect your Strava account and automatically import race activities—track your complete race history with features Strava doesn’t offer. Start free.

---

How do you track your races? Still using Strava alone, or do you use a separate race tracker? Share your system on Instagram or Threads!