Skip to main content

Support

Knowledge base

Plain-language explanations for the stats on your runs, dashboard, and behavioral profiles.

On an activity run page, tap the ? in the top-right corner of a stat card for a quick definition. This page collects everything in one place.

Glossary

Terms you will see across runs, stats, and the dashboard.

Behavioral profile

A label for how you paced the run — not how fast you ran.

RunPattern assigns one of eleven archetypes (such as Negative Splitter or Diesel) based on pace shape, heart-rate trend, and variability across the workout.

Pace drift

Second-half pace vs first-half pace, as a percentage.

Calculated from smoothed Strava pace streams. +2% means the second half was about 2% slower than the first; negative values indicate a negative split.

Start vs middle

Opening quarter compared to the middle block of the run.

Highlights fast starts or cautious openings before fatigue sets in. Used to detect sprinter-starter and understarter patterns.

Late drop

Final third compared to the middle block.

Shows whether you held pace into the finish or faded. A key signal for breakpoint and positive-split patterns.

Variability

Pace consistency across the full run.

Derived from minute-to-minute pace movement. Even splitters score low; surge runners score higher.

Early variability

Variability in the first two-thirds of the run.

Isolates uneven effort before a late fade — helpful when distinguishing a controlled start from mid-run surging.

Pace surges

Count of meaningful pace direction changes.

Each surge is a sustained shift faster or slower. Many changes suggest a surge-runner pattern rather than steady pacing.

HR trend

Second-half heart rate vs first half.

When pace stays similar but HR rises, you may be working harder for the same speed — a cardio-drift signal.

Stream samples

Strava pace points used in analysis.

Runs need enough stream data to classify. Very short runs or activities without GPS pace streams may show as unclassified.

Dominant profile

Your most common pacing pattern over recent runs.

Shown on the dashboard when you have enough classified activities. It reflects frequency, not your fastest run.

Confidence

How reliable the profile assignment is for that run.

Based on sample count and metric clarity. Low confidence often means a short run or noisy GPS pace data.

Calibration

Thresholds personalized to your recent Strava history.

After four or more synced runs, RunPattern derives four threshold bands from your recent efficiency and pace trends. They replace population defaults on the next sync so Sprinter Starter, Drifter, Plateau, and similar labels match how you actually pace — not a generic runner.

Drift sensitivity

Positive pace-drift percentage before overpacing patterns kick in.

Also called overpacing drift threshold. If your second half is slower than your first by at least this percentage, RunPattern is more likely to assign Sprinter Starter, Positive Splitter, or related fade patterns. A lower number (for example 5.3 vs 8.5) means you are held to a tighter line — small slowdowns count as meaningful drift for you.

Fatigue (heart rate)

HR rise across halves that signals accumulating fatigue.

Computed as (second-half average HR − first-half average HR) ÷ first-half HR. The calibration value is the minimum rise that counts toward a Drifter classification when pace is also slowing. Runners with improving efficiency often get a slightly lower threshold; declining efficiency raises it.

Fatigue (pace)

Pace slowdown across halves that signals fatigue drift.

Computed as the fractional pace change from the first half to the second (positive means slowing). Together with Fatigue (heart rate), this gates the Drifter profile — both metrics must cross their calibrated lines. Derived from whether your recent runs trend faster or slower in the back half.

Stable pace band

How flat your half-to-half pacing must be to read as very steady.

A tight band for judging plateau-like consistency. Smaller values mean RunPattern expects you to hold a flatter effort profile before labeling a run as highly stable. Adjusts with your recent efficiency trend — steadier histories can narrow the band.

FAQ

Common questions about profiles, sync, and metrics.

How does RunPattern choose my profile?

Each run is scored on pace drift, start vs middle, late drop, variability, surges, and heart-rate trend. Those metrics are compared to your calibrated thresholds (or defaults when you're new) to pick the best-matching archetype.

Why is a run unclassified?

Usually the activity lacks enough Strava pace stream data — for example a treadmill run without a footpod, a very short effort, or GPS gaps. Sync again after Strava processes streams, or check that the activity recorded pace.

What does positive or negative drift mean?

Positive drift means you slowed from the first half to the second (positive split). Negative drift means you ran the second half faster (negative split). Zero is an even split.

Related terms

What's the difference between dashboard stats and run metrics?

Dashboard quick stats summarize your synced library (volume, analyzed count, average pace). Run detail metrics describe how that single workout unfolded — those drive the behavioral profile.

Related terms

How often should I sync?

After new Strava activities, use Sync on the dashboard. RunPattern reads your recent runs and recomputes profiles, trends, and calibration thresholds.

Related terms

Do I need to memorize every metric?

No. The profile name and insight line are the main takeaway. Metrics are there when you want to understand why a label was assigned — tap the ? on stat cards on an activity run page for a quick explanation.

What if heart rate is missing?

HR trend is skipped when Strava has no HR stream. Pace-only metrics still classify the run; cardio-related patterns need a chest strap or optical HR recorded in Strava.

Related terms

Can I change miles vs kilometers?

Yes — open Settings and switch units. Distances and paces update across the app; percentage metrics stay the same.

What do the calibration numbers on my dashboard mean?

After four or more Strava runs, the dashboard shows four personalized thresholds. Drift sensitivity is a percentage — how much second-half slowdown counts as overpacing. Fatigue (heart rate) and Fatigue (pace) are decimal rates (multiply by 100 for an approximate percent) used together to detect Drifter patterns. Stable pace band is how flat your half-to-half pacing must be to count as very steady. Lower numbers are stricter for you; values shift when you sync new runs.

Related guides

Knowledge base — RunPattern