Athlete Glycemic Optimization: Your CGM Race Day Fueling Protocol for Peak Performance

The 17-Mile Wall I Hit at Ironman Arizona

My legs were fine. My lungs were fine. But somewhere around mile 17 of the marathon, my brain went foggy and my pace dropped from 7:45 to 9:30 per mile—and I had no idea why until I looked at my CGM data afterward. My glucose had crashed to 62 mg/dL while I was robotically consuming the same gel every 45 minutes that had "worked" in training.

That race taught me something that changed everything: fueling by feel is gambling. Fueling by glucose data is strategy.

Why Your Current Fueling Plan Is Probably Wrong

Here's the uncomfortable truth about most race nutrition plans. They're based on generic recommendations—take 60-90 grams of carbs per hour, consume a gel every 30-45 minutes, drink to thirst. These guidelines work for the "average" athlete, but you're not average. Nobody is.

Your glucose response to a banana before a race is different from mine. Wildly different, actually. One study published in Sports Medicine in 2024 tracked 847 endurance athletes using CGM during training and found glucose variability of up to 89 mg/dL between individuals consuming identical pre-race meals. Same food, same timing, completely different metabolic responses.

The athlete who spikes to 180 mg/dL after oatmeal and then crashes mid-race needs a totally different strategy than the one who maintains steady glucose at 130 mg/dL. Without CGM data, you're just guessing which one you are.

The Glucose Sweet Spot: What the Data Actually Shows

So what glucose range should you target during a race? The Supersapiens Elite Athlete database—which now includes over 2.3 million hours of training and racing data—points to a surprisingly narrow window.

For most endurance athletes, performance peaks when glucose stays between 120-160 mg/dL during competition. Drop below 100 and cognitive function starts declining before your muscles even feel it. Climb above 180 and you'll often see a reactive crash within 45-60 minutes.

But here's where it gets interesting. That optimal zone isn't static throughout a race. During the first hour, staying closer to 140-160 mg/dL gives you a buffer. In the final third of a long event, many athletes perform better slightly lower—around 110-130 mg/dL—because they've become more fat-adapted as glycogen depletes.

I've seen this pattern in my own data across 14 half-ironman races. My best performances cluster around an average glucose of 142 mg/dL for the first two hours, dropping to 127 mg/dL in the final hour.

Pre-Race Carb Timing: The 3-Hour Protocol

Forget the old advice about eating 3-4 hours before race start and hoping for the best. CGM data lets you build a precise pre-race protocol based on your actual glucose response.

Start with your pre-race meal 3 hours out. For most athletes, this means 100-150 grams of carbohydrates—oatmeal, banana, toast, whatever sits well in your stomach. Then watch your CGM.

The goal is to see glucose peak somewhere between 150-170 mg/dL about 60-90 minutes after eating, then settle back to 100-120 mg/dL by race start. If you're still above 140 at the start line, you've eaten too much or too close to race time. If you're below 90, you've either eaten too little or waited too long.

One triathlete I coach discovered through CGM that her glucose peaked at 45 minutes post-meal, not 90 minutes like the textbooks suggest. She was starting races at 165 mg/dL and crashing by mile 10 of the bike. Moving her pre-race meal back by 30 minutes solved a problem she'd blamed on "race nerves" for three seasons.

Real-Time Race Fueling: The Glucose Targeting Method

This is where CGM transforms from a training tool into a race-day advantage. Instead of eating on a fixed schedule, you fuel based on glucose trends.

The basic framework works like this. When glucose drops below 130 mg/dL and shows a downward arrow, consume 20-30 grams of fast-acting carbs. When glucose is stable between 130-150 mg/dL, maintain with smaller doses of 15-20 grams every 30-40 minutes. When glucose is above 160 mg/dL and rising, skip the next planned intake and let it settle.

The ATTD 2024 conference presented data on 156 competitive cyclists using this glucose-targeting approach versus fixed-schedule fueling. The glucose-targeting group had 67% fewer episodes of glucose below 80 mg/dL and reported significantly lower perceived exertion in the final third of their events.

But there's a catch. Glucose data has a 10-15 minute lag from actual blood glucose, and an even longer lag from what's happening in your working muscles. You need to fuel proactively, not reactively. If your CGM shows 125 mg/dL with a downward trend, that gel you eat now won't hit your bloodstream for another 15-20 minutes. Start fueling before you need it.

The Pre-Race Testing Protocol: 4 Workouts That Dial In Your Strategy

You can't figure this out on race day. You need to test your glucose response in training, under race-like conditions. Here's the protocol I use with athletes.

Workout one: the breakfast test. Do a moderate 90-minute session after your planned race-day breakfast, eaten at the same pre-race timing. Track when glucose peaks, how fast it falls, and where it settles during exercise. Repeat this three times with the same meal to establish your pattern.

Workout two: the fuel comparison. During a long session, alternate between your planned race fuels—gels, chews, drink mix, real food—and note the glucose response to each. Some athletes spike 40 mg/dL from one gel brand and only 20 mg/dL from another. The difference matters.

Workout three: the intensity test. Your glucose response changes dramatically with intensity. A tempo run might keep glucose stable at 135 mg/dL, while threshold intervals could spike you to 175 mg/dL from stress hormones alone—without eating anything. Map these patterns so race-day intensity doesn't surprise you.

Workout four: the full dress rehearsal. Six to eight weeks before your goal race, do a race-simulation workout with full race nutrition. This is your data collection day. Every 15 minutes, note your glucose, what you consumed, and how you feel. This becomes your race-day playbook.

Supersapiens vs. Dexcom: Which CGM for Athletes?

Both platforms work for athletic glucose tracking, but they're optimized for different use cases. Supersapiens (using Abbott Libre Sense technology) was built specifically for athletic performance. The app shows glucose zones designed for exercise, trend predictions during workouts, and post-workout analysis of fueling effectiveness.

Dexcom G7, while designed primarily for diabetes management, offers advantages in real-time accuracy and integration with sports watches. The 30-second update frequency means you see trends faster than Libre's 1-minute readings—which matters when you're making fueling decisions mid-race.

The practical difference? Supersapiens gives you better post-workout analysis and sport-specific features. Dexcom gives you slightly faster real-time data and broader device compatibility. Most serious athletes I work with have tried both and settled on whichever integrates better with their existing tech setup.

One important note: sensor accuracy decreases during heavy sweating and extreme temperatures. Both platforms show more noise in hot-weather racing. Don't make dramatic fueling changes based on a single reading—look for trends over 10-15 minutes.

The Bonk Prevention Checklist

After analyzing glucose data from over 200 race files, I've identified the patterns that predict bonking before it happens. Here's what to watch for.

Glucose below 110 mg/dL with a downward trend in the first half of a race: you're already behind on fueling. Glucose above 170 mg/dL after an hour of racing: you've over-fueled and a crash is likely coming. Glucose variability greater than 50 mg/dL in any 30-minute window: your fueling is too inconsistent, causing energy swings.

The athletes who race well show remarkably flat glucose curves. Not perfectly flat—that's impossible—but steady oscillations between 120-150 mg/dL rather than dramatic spikes and crashes.

What I Wish I'd Known Before Ironman Arizona

Looking back at that 17-mile wall, the CGM data told the whole story. I'd eaten my pre-race meal at 4am for a 7am start—too early, leaving me at 95 mg/dL at race start. I'd fueled identically on the bike and run, ignoring that running spikes my glucose 25 mg/dL higher than cycling at the same effort. And I'd stuck to my 45-minute gel schedule even when my glucose was already at 155 mg/dL and rising.

Every mistake was preventable with data I now have for every race.

The technology isn't magic. You still have to do the training, manage the pacing, handle the mental game. But fueling? That's a solved problem now. The athletes still bonking in 2026 are the ones who haven't looked at their glucose data yet.