CGMs for Runners: Worth the Hype — or Is Your Watch Already Enough?

The Patch on Every Arm at the Starting Line

Walk through any marathon expo in 2026 and you will notice a small white disc on the back of every third runner's arm. It is a continuous glucose monitor — a CGM — and it has crossed over from diabetes management into endurance sport faster than anyone predicted.

Supersapiens launched the trend. Levels and NutriSense followed. Abbott's Lingo brought the price down to $49 a month. And when Sebastian Sawe smashed the two-hour marathon barrier in London fuelled by 115 grams of carbohydrate per hour, suddenly every recreational runner wanted to know: should I be tracking my glucose too?

The answer is more nuanced than the marketing suggests.

What a CGM Actually Measures

A CGM is a tiny sensor inserted just beneath the skin, usually on the upper arm. It samples interstitial fluid every few minutes and reports your blood glucose level as a continuous line on your phone.

During a run, that line tells you how your body is responding to the fuel you have taken in and the effort you are putting out. When glucose rises sharply after a gel, you can see it. When it crashes at mile 18, you can see that too.

This is genuinely useful information. But it is one data point — and endurance performance depends on several others that a CGM cannot see.

What CGM Data Can Tell You

There are three scenarios where a CGM earns its place on your arm.

Dialling in your pre-run meal. Most runners eat the same breakfast before every long run without knowing whether it actually delivers stable glucose by the time they start. A CGM shows you. If your go-to bagel-with-peanut-butter spikes you to 180 mg/dL and then crashes before you leave the house, you know to eat earlier or choose something with a slower absorption curve. Two weeks of pre-run meal testing can save months of inconsistent long runs.

Finding your fueling sweet spot. The 60-to-90 grams of carbs per hour guideline is a range, not a prescription. A CGM helps you see how your body handles 60 versus 75 versus 90 grams in real time, which makes it easier to find the dose that keeps glucose stable without overwhelming your gut.

Spotting the crash before you feel it. Glucose drops lag behind the subjective feeling of bonking by 10 to 15 minutes. If you can see the line trending down at mile 14, you can take a gel before the wall hits at mile 16. This is particularly valuable in training, where you are calibrating your plan for race day.

What CGM Data Cannot Tell You

Here is the gap that CGM marketing rarely acknowledges. Glucose is one input into a fueling plan. It is not the plan itself.

A CGM does not measure your sweat rate. Two runners side by side in 30-degree heat can lose vastly different amounts of fluid per hour — anywhere from 0.5 to 4.0 litres, according to research across 1,303 athletes. Glucose tells you nothing about how much you need to drink.

A CGM does not track sodium or electrolyte losses. Cramping at mile 18 is rarely a glucose problem. It is usually a sodium problem. Your sweat can contain anywhere from 200 to 2,000 milligrams of sodium per litre, and no glucose sensor in the world can measure that.

A CGM does not know the conditions. The same fueling plan that works perfectly in a 15-degree April training run can fail catastrophically in a 32-degree July long run. Glucose responds to exercise intensity and carbohydrate intake, but it does not factor in ambient temperature, humidity, or altitude — all of which change your hydration and fueling needs dramatically.

A CGM does not build a race-day plan. It shows you what is happening right now. It does not calculate how many grams of carbohydrate per hour you need based on your body weight and finishing time. It does not schedule your gel timing around aid stations. It does not adjust your fluid intake for the forecast temperature on race morning.

A CGM does not connect to your training load. A runner doing 80-kilometre weeks needs a fundamentally different daily nutrition strategy than the same runner doing 50-kilometre weeks in taper. Glucose snapshots do not see the bigger picture of accumulated training stress and recovery demand.

The Real Question: Do You Need Another Sensor?

The CGM trend is part of a broader pattern in endurance sport: more data, more sensors, more numbers on the screen. But more data does not automatically mean better decisions.

Most runners already carry a device that collects the data they need. A Garmin or Apple Watch tracks heart rate, pace, training load, estimated calorie burn, workout duration, and — on newer models — estimated sweat loss. Strava logs every session. The problem is not a shortage of data. The problem is that nobody connects the data to an actionable fueling and hydration plan.

Garmin's Connect+ added food logging in January 2026, but it works like MyFitnessPal — it tracks what you ate, not what you should eat during your next long run. TrainingPeaks launched Fueling Insights, but it only works with cycling power data and tells you what happened after the ride, not what to do during it. Nix makes a sweat sensor that measures sodium loss in real time, but the patches cost $6 each and the data lives in its own silo.

The gap in the market is not another sensor. It is intelligence — software that takes the data your watch already collects and turns it into a plan you can follow.

When a CGM Is Worth It

If you are in the performance-obsessive category — training 10 or more hours per week, racing competitively, willing to spend $50 to $200 per month on a marginal edge — a CGM can sharpen your fueling by about 5 to 10 per cent. Use it for a focused two-to-four-week block to test pre-run meals, calibrate gel timing, and find your personal carbohydrate ceiling. Then take the sensor off. The insights compound; the data subscription does not need to be permanent.

If you are training for your first or second marathon, or you race three to six times a year, the honest recommendation is this: skip the CGM. The same outcomes — a stable fueling plan, the right gel timing, the right hydration volume — can be achieved by combining your existing wearable data with a structured plan that adapts to your body and conditions.

The Smarter Play

Your Apple Watch or Garmin already knows your heart rate zones, your training load trend, your workout history, and your estimated calorie burn. What is missing is the layer that translates all of that into "drink 400 millilitres now" and "take a gel at the 45-minute mark."

That is what Sweatr does. It pulls your data from Apple Watch, Garmin, and Strava, combines it with your body metrics and the conditions you are training in, and builds a personalised hydration and fueling plan that adapts as your training changes. No patches. No subscriptions to disposable sensors. No separate app for each data stream.

The goal is not to stack more wearables on your body. It is to make the wearable you already own actually useful for the question every runner asks before a long run: what do I drink, what do I eat, and when?

The Bottom Line

CGMs are a legitimate tool for a narrow use case: short-term fueling calibration for serious athletes. They measure one important variable well. But they do not measure the other variables that determine whether your race-day nutrition plan succeeds or fails — and they do not build the plan itself.

Before you spend $200 on a glucose sensor, ask yourself whether you have a fueling and hydration plan at all. If the answer is no, the sensor is not what you need. The plan is.