Continuous Glucose Monitor (CGM) Insights for Triathletes: What the Data Shows Across Doubles, Bricks, and Race Day

Wear a continuous glucose monitor for a single big training week and here is roughly what the data will show you, and when. Within the first long ride, you will see your glucose hold or drift depending on whether your per-hour carbohydrate intake matches your output. On a brick, you will watch the run leg start either topped up or already sagging from the bike. Across a few days of doubles, you will see how overnight and between-session fuelling decides whether you start each session in the hole.

For an athlete carrying the highest weekly training hours of any sport — juggling swim, bike and run on one recovery budget — that visibility is genuinely interesting. But the data has a catch: it is laggy, noisy, and easy to over-read. This page lays out what a CGM can actually measure for a triathlete, what it can't, and how to use a short experiment to sharpen your fuelling without letting the graph run your nutrition.

1. What you can measure across a training week

The honest value of a CGM for a triathlete is execution feedback during long sessions. On a three-hour ride, a slow downward drift in your glucose is an early signal that intake is lagging behind expenditure — a useful nudge to eat before you dig a hole you cannot climb out of. Hold the line steady across the ride and you have confirmation, in your own data, that your per-hour fuelling is working at that intensity.

Bricks are where the data earns most of its keep. Coming off the bike, you can see whether you are handing your run leg a full tank or a sagging one, which is precisely the transition that wrecks age-group run splits. Over a few days of doubles, the curve also shows whether your between-session and overnight fuelling actually refills the tank, or whether you are quietly accumulating a deficit across the week — the chronic under-fuelling that high-volume triathletes slide into without noticing.

What it does not measure is just as important. The curve says nothing directly about your fat loss, your calorie balance, your insulin, or your long-term metabolic health. A larger glucose rise after a nutritious meal is not bad; it is just fuel. Glucose is one downstream signal, not a master metric for a body managing three sports — so use it to verify fuelling, not to rank foods.

2. The lag and noise: read trends, not race-pace numbers

Before you act on anything mid-session, respect how imperfect the signal is. A CGM samples interstitial fluid, not blood, and that introduces a 5 to 15 minute lag that widens whenever glucose moves fast — which describes most of a hard ride or a race start. The peak you see is late and slightly blunted versus your true blood value. Layer on measurement error, typically a mean absolute relative difference in the high single digits to low double digits of percent, plus warm-up periods, calibration drift, and the compression lows you can trigger lying on the sensor after a long day.

For a triathlete the practical rule is: the curve is excellent for trends over a session and patterns over a training block, and poor for a single instantaneous number at threshold. Do not chase a specific reading during a hard interval — by the time the sensor catches up, the effort has changed. Watch the direction and the shape across the hour, not the digit in the moment. And ignore single weird readings; one odd value after T1 or a sensor knocked in the swim is noise, not data.

3. A brick-and-double experiment, with real fuelling numbers

Run a focused 2-to-4-week experiment rather than wearing the sensor indefinitely. Test specific sessions, log everything, and pull a few personal patterns you can keep. The fuelling targets below are the established endurance consensus — the CGM personalizes them, it does not replace them.

Those numbers are the backbone: roughly 30-60 g of carbohydrate per hour for efforts beyond an hour or so, scaling toward 90 g/hr with multiple transportable carbohydrate types for the longest, hardest work, on a daily base of around 5-12 g/kg depending on your training load, with carbohydrate plus protein afterward to refill glycogen. Each sensor lasts 10-14 days and the kit is not cheap, so a few weeks usually delivers most of the learning. After you know your personal numbers, you do not need to keep wearing one.

4. Race day, honest limits, and the medical line

On race day, the rule every triathlete already knows applies double: nothing new. A CGM can confirm in training that your in-race carbohydrate strategy keeps glucose from sagging on the back half of a long-course bike or the late miles of an Ironman run, and that is a fair use. But the curve will not save a fuelling plan you only tried for the first time on the start line, and untested race nutrition is the classic route to GI distress regardless of what your sensor says. The metabolic flexibility that lets a trained athlete shift between fat and carbohydrate across intensities is built in training, not read off a screen on race morning.

Two honest caveats to close. The high-quality evidence that CGM-guided eating improves performance in healthy athletes is thin — these fuelling numbers rest on sports-nutrition consensus, not on CGM outcome trials, which barely exist for this group. And the medical line is firm: a consumer CGM is not a diagnostic device, so persistently high readings or symptoms like excessive thirst, frequent urination or unexplained weight loss mean a doctor and a real blood test, not the app. If you have diabetes or take glucose-lowering medication, this whole frame is off the table — use a CGM only under your clinician's direction. For the long-course athlete, also keep heat illness and hyponatremia front of mind on race day; those risks live well beyond anything your glucose curve will warn you about.

Multisport questions about glucose and fuelling

Which discipline does a CGM help most?

The bike and the run, and especially the brick between them. Steady cycling and running are where a slow downward glucose drift gives you early warning that fuelling is lagging output, and the bike-to-run transition is where you can see whether you're handing the run a full tank. The swim offers little — too short and too disrupted for clean data. Use it for the long aerobic work, not the pool.

How do I read it across doubles and brick days?

Watch the trend across each session and the recovery of your line between sessions, not single numbers. On a brick, check your starting glucose off the bike. Across a double, see whether between-session carbs and protein restore the tank before session two. The 5-15 minute lag means instantaneous readings at hard efforts are unreliable, so judge direction and shape over the hour instead.

What's the race-week and Ironman-day protocol?

Nothing new on race day — that rule overrides the sensor. Use the CGM in training to confirm your in-race carb plan keeps glucose from sagging late, then race the plan you rehearsed. It won't rescue untested nutrition, which is the main cause of race-day GI distress. On long course, heat illness and hyponatremia matter more than your glucose curve, so respect fluid and sodium too.

Will the curve tell me if I'm under-fuelling across my training?

It can hint at it. If your morning starting glucose trends low across a heavy block and sessions start sagging early, that's a flag to check your daily carbohydrate against the roughly 5-12 g/kg your volume demands. But glucose is one signal — performance, mood, sleep and weekly load tell you more about chronic under-fuelling. Treat a low trend as a prompt to audit intake, not as a diagnosis.

Disclaimer: This article is for educational purposes only and is not medical advice. Consult a qualified healthcare professional before starting any supplement, nutrition, or training protocol — especially if you are pregnant or breastfeeding, under 18, taking medication, or managing a health condition.