Continuous Glucose Monitors (CGMs) have transformed diabetes management by delivering real‑time glucose data directly to your smartphone, smartwatch, or dedicated receiver. But raw numbers alone aren’t enough—you need alerts that wake you up when your glucose is trending low, warn you before a high spike hits, and let you stay on top of every critical moment. Properly configured alerts are the difference between proactive control and constant reaction. In this guide, you’ll learn exactly how to set up, customize, and troubleshoot CGM alerts so you never miss a critical glucose event again.

Why CGM Alerts Matter

Alerts are your safety net. Clinical research shows that users who enable and personalize their alert thresholds experience fewer severe hypoglycemic events and significantly improve their Time‑in‑Range. A study published in Diabetes Technology & Therapeutics found that audible alarms for hypoglycemia reduced the duration of low episodes by nearly 50%. When your glucose drops quickly or climbs out of range, an alert buys you precious minutes to eat a snack, take a correction dose, or adjust your activity. Without alerts, you rely solely on sporadic checks or physical symptoms—symptoms that can be blunted by autonomic neuropathy, exercise, or sleep. Custom alerts empower you to live more freely while maintaining tight control.

Understanding the Different Types of CGM Alerts

Modern CGMs offer more than a single high/low alarm. Each alert type serves a distinct purpose. Knowing what each does—and how to adjust them—is the first step to building a personalized alert system.

High Glucose Alerts

This alert sounds when your glucose crosses a preset high threshold (e.g., 250 mg/dL). Most systems let you set a “red alert” for a hard target and an optional “warning” at a slightly lower level. For example, you might set a warning at 200 mg/dL and a critical alert at 300 mg/dL. Many CGMs now offer predictive alerts that sound based on slope rather than an absolute value, giving you even earlier warning.

Low Glucose Alerts

The most vital alert for safety. Default settings often trigger at 70 or 80 mg/dL. However, people who experience hypoglycemia unawareness may need a higher threshold (e.g., 90 mg/dL) to allow time to react. Some devices also include “Urgent Low Soon” alarms that predict when you’ll hit 55 mg/dL within the next 20 minutes using rate‑of‑change data.

Rate of Change Alerts

These warnings detect rapid rises or falls (e.g., >2–3 mg/dL per minute). A rate alert can catch a steep drop before your glucose actually reaches the low threshold. Similarly, a rapid rise may indicate a missed meal bolus or a failing infusion set. Enable these if your CGM supports them—they are extremely useful for exercise, illness, or after high‑carb meals.

Custom Alerts (Threshold vs. Predictive)

Beyond the basic types, most CGM apps let you create custom profiles. You can set different thresholds for different times of day (e.g., stricter overnight lows), for exercise mode, or for a “hypo‑awareness” override. Some apps also allow uploading profiles for specific activities like swimming, driving, or sleep. The more you customize, the fewer nuisance alarms you’ll get, which helps prevent alert fatigue.

Step‑by‑Step Guide to Setting Up Alerts on Your CGM

The exact menu names vary by device (Dexcom G7, Freestyle Libre 3, Medtronic Guardian, etc.), but the core workflow is identical. Follow these steps to configure alerts on any current system.

1. Access the Settings Menu

Open the CGM app on your smartphone or navigate the receiver’s interface. Look for a gear icon, a “Settings” tab, or a “Notifications” section. On the Freestyle Libre 3, head to the main menu and tap “Settings” then “Alarms.” On Dexcom G7, tap the bell icon on the home screen or go to “Settings > Alerts.” If you use a pump‑integrated system like the Tandem t:slim X2, you’ll find alert menus under “CGM Settings.”

2. Enable the Alerts You Need

Most systems show a list of toggles: “High Alert,” “Low Alert,” “Urgent Low Soon,” “Rise Rate,” “Fall Rate,” and so on. Turn on each alert you want by tapping the toggle or slider. For safety, always enable the low and urgent low soon alerts. You can safely disable high alerts temporarily if you find them overly distracting, but keep low alerts active at all times.

3. Set Your Thresholds

Tap on each alert to set its value. For high alerts: many clinicians recommend starting at 250 mg/dL (or 13.9 mmol/L) and adjusting based on your personal target range. For low alerts: start at 80 mg/dL (4.4 mmol/L). If you have hypoglycemia unawareness or are using an insulin pump, consider raising the low threshold to 90–100 mg/dL. For rate alerts: typical defaults are ±2 mg/dL/min for a “rise” or “fall” warning. You can tighten these to ±3 or loosen to ±1.5 depending on how sensitive you want the system to be.

4. Configure Sound, Vibration, and Repeat Intervals

Don’t stop at thresholds. For each alert you can usually choose a sound, a vibration pattern, or a silent notification. Some apps let you set “re‑alert” intervals—e.g., if your glucose stays above 250, the alarm repeats every 30 minutes. Choose a repeat interval that is helpful but not annoying. For overnight alerts, consider enabling “do not disturb” mode with exceptions for urgent low or high alerts (called “critical alerts” on iOS).

5. Test Your Alerts Immediately

After you finish, test the system. Try pressing a button on your CGM app that triggers a test alarm (often found in the “Support” or “About” menu). Alternatively, simulate a low glucose event by using a glucose simulator (if your app has one) or by waiting until your next real low event (but it’s safer to do a fingerstick test while verifying). On Dexcom G7 you can use the “Test Alarm” in the Alert Settings menu. Make sure the sound is loud enough and the vibration works. If you wear your phone in a different location, check that you can hear it in a noisy environment.

Advanced Alert Customization

Once you have the basics covered, explore the advanced features that make alerts truly intelligent.

Predictive Alerts

Many CGMs now use slope‑based prediction to give you a 10–20 minute warning before you actually cross a threshold. For example, Dexcom G6 and G7 offer “Urgent Low Soon” that predicts you’ll reach 55 mg/dL within 20 minutes. The Freestyle Libre 3 has a similar “Urgent Low Glucose” alarm. These are game‑changers for preventing severe hypos while you’re asleep or exercising.

Time‑Based Profiles

You can set different alert thresholds for night and day. For instance, during sleep you may want a higher low threshold (e.g., 90 mg/dL) because you can’t react as quickly. During daytime, you might lower it to 70 mg/dL to reduce false alarms. Some apps like Dexcom allow “custom alerts” with time ranges; for other CGMs you may need to manually adjust at bedtime. Consider using a smart automation app like IFTTT or Shortcuts to change profiles automatically with sunrise/sunset.

Pattern Alerts

Some systems (e.g., Medtronic Guardian with Look Back) can identify repeated patterns—like post‑meal spikes or overnight lows—and alert you proactively. For example, if your CGM detects three mornings where glucose dropped below 70 after breakfast, it can suggest adjusting your insulin‑to‑carb ratio. These pattern alerts are optional but very helpful for fine‑tuning your insulin plan. They reduce the number of one‑off false alarms while still catching recurring issues.

Sharing Alerts with Caregivers

Most CGM apps let you share live data with family members, roommates, or healthcare providers. On Dexcom Follow, caregivers can receive the same high, low, and urgent alerts on their own phones. Freestyle LibreLink has a similar feature via LibreLinkUp. Enable sharing for peace of mind—especially for children with diabetes, elderly users, or anyone living alone. When setting up sharing, ensure the caregiver’s device is set to receive critical alerts even if their phone is on silent (iOS allows critical alert bypass).

Integrating CGM Alerts with Other Devices

Your CGM’s built‑in app is excellent, but you can extend its reach to smartwatches, fitness bands, and even data‑sharing platforms.

Smartwatches (Apple Watch, Wear OS)

Many CGM apps have a watch companion. Dexcom G7’s watch face shows current glucose and a trend arrow. While the watch can alert you to high/low values, it may not support the “Urgent Low Soon” tone yet. For louder alarms, pair your phone with a Bluetooth speaker or use a smartwatch that can vibrate aggressively. Wear OS watches (Samsung Galaxy Watch, Fossil) with the Dexcom app work similarly. Note that watch alerts depend on the phone app; if the phone is out of Bluetooth range, the watch won’t get alerts.

Nightscout and DIY Integration

For advanced users, Nightscout (a crowd‑sourced, open‑source CGM data platform) allows you to set custom alerts via its web interface. You can create text‑message alerts, push notifications, or even SMS to multiple numbers. Nightscout also integrates with smart home devices like Google Home or Alexa. The setup requires technical know‑how (an Azure or Heroku deployment), but it offers the most flexible alert system available. Many users combine Nightscout with companion apps like xDrip+ to get even more granular control over alert thresholds and snooze durations. Learn more about Nightscout here.

Connecting to Insulin Pumps

If you use a hybrid closed‑loop system (Tandem Control‑IQ, Medtronic 780G, Omnipod 5), the pump itself can generate alerts based on CGM data—like “Auto‑Bolus Suspension” or “Basal Suspend.” These alerts often come directly from the pump’s screen or a separate app. Configure your pump’s alert settings in addition to your phone alerts to create a redundant safety net. Most important is the “suspend before low” feature that stops insulin delivery when hypoglycemia is imminent—this adds another layer of protection.

Best Practices for Managing Alert Fatigue

Too many alerts can become overwhelming, leading to “alert fatigue” where you start ignoring or disabling important warnings. Here’s how to strike the right balance.

  • Set realistic thresholds. If your high alert fires every time you finish a meal, your threshold is probably too tight. Increase it by 20–30 mg/dL to reduce false alarms while still catching genuine highs. Similarly, set your low threshold one or two notches above where you feel symptoms—don’t set it at 70 mg/dL if you always treat at 80.
  • Use silent mode for low‑priority alerts. Most CGMs allow you to make high alerts vibrate only while keeping low alerts as loud sound. Use this to differentiate urgency. Critical lows should always be loud; rate alerts can be vibrational.
  • Schedule “quiet hours” via do‑not‑disturb with exceptions. On iPhone, go to Settings > Focus > Sleep and allow time‑sensitive alerts from your CGM app. On Android, use Do Not Disturb and set the CGM app as a priority app. This allows critical alarms through while muting non‑urgent notifications during meetings or sleep.
  • Regularly review your alert history. Many apps show a log of triggered alerts. Check weekly to see if you’re getting too many of a specific type. Adjust thresholds accordingly—if you had ten low alarms this week but only treated three real lows, raise your low threshold to 90 mg/dL and see if false alarms decrease.
  • Use customization for exercise and illness. Create a temporary “Exercise” profile with a higher low threshold (e.g., 100 mg/dL) and a longer snooze for rate alerts. For illness, you might tighten high alerts to catch fevers or dehydration earlier. These quick changes prevent alert overkill on normal days.

Troubleshooting Common Alert Problems

Even with perfect settings, alerts can fail. Here are the most frequent issues and how to fix them.

Missed Alerts

If your CGM alarm doesn’t sound when expected, first check that your phone’s notification settings haven’t been changed. On iPhone, go to Settings > Notifications > [CGM App] and ensure “Allow Notifications” and “Sound” are on. Also verify that “Critical Alerts” is toggled on (this overrides silence and do‑not‑disturb). On Android, check “App notifications” for the CGM app and ensure “Wake screen” and “Sound” are enabled. If you use a receiver (not a phone), make sure the receiver’s volume isn’t muted and that its battery is charged.

A common cause of missed alerts is Bluetooth disconnection. If your phone is more than 30 feet from the CGM transmitter, the data stream breaks and the app may stop evaluating alert conditions. Keep your phone nearby, or use a receiver that lives on your belt. On some systems, an alert that would have triggered during a disconnection will fire when reconnected—but not all do. Test this by putting your phone in another room and checking if you miss a predicted low.

False Alarms / Frequent Nuisance Alerts

False positives usually happen because your thresholds are too tight or your sensor is giving a “compression low” at night (when you lie on the sensor). If you get repeated low alerts while sleeping but fingersticks show normal glucose, the sensor may be compressed. This disappears when you turn over. To avoid false lows, you can increase the low threshold temporarily at night, or enable “snooze” after a first alarm. Some CGMs (like Dexcom G7) now have “Compression Low” detection that suppresses false alarms.

For rapid rise/fall alerts, a single bad reading (e.g., from a pressure artifact) can cause a spike that triggers a false rate alert. If it happens rarely, just acknowledge it. If it happens often, loosen the rate threshold from ±2 to ±3 mg/dL/min. Also check that your sensor is well‑adhered and hasn’t been knocked.

Device Connectivity & Battery

If your phone or receiver loses connection to the transmitter frequently, try moving to a new location, restarting Bluetooth, or replacing the transmitter if it’s near end‑of‑life (most have a 10‑day sensor but a 90‑day transmitter). Keep your phone’s battery above 20%—some Android devices shut off Bluetooth at low battery to save power. Also update your CGM app to the latest version; firmware updates often fix connectivity bugs.

Hardware Failures

Occasionally a sensor wire breaks or the transmitter malfunctions. If you see repetitive “sensor error” alerts, contact the manufacturer for a replacement. Dexcom and Abbott have generous replacement policies. Don’t ignore a string of failed sensors—it could indicate a bad batch or a device update issue.

Future of CGM Alerts: Smarter, More Personalized

The generation of CGMs currently entering the market bring machine‑learning algorithms that learn your individual glucose patterns rather than relying on static thresholds. Next‑generation devices like the Dexcom G8 prototype are rumored to use AI to predict hyper/hypo events up to 60 minutes ahead with high accuracy. Closed‑loop systems already use CGM data to automate insulin delivery, and future systems will incorporate activity, food, and stress data from wearables to dynamically adjust alert thresholds. Already, Apple Watch and Garmin watches can display CGM data, and soon they may also transmit alerts to emergency contacts when a sensor detects a severe hypo during a fall. The ultimate goal is a system where you rarely hear an alert because the technology prevents the dangerous deviation in the first place. For now, mastering your current alert settings is the best way to enjoy that freedom in everyday life.

Setting up and fine‑tuning your CGM alerts is not a one‑and‑done task—it’s an ongoing process that evolves with your body, your routine, and new technology. Start by enabling the low and urgent low alarms, then progressively customize high thresholds, rate alerts, and time‑based profiles. Lean on sharing features to give caregivers peace of mind, and use common troubleshooting steps to fix noisy or missed alerts. With a well‑configured alert system, you can trust that your CGM will wake you when it matters most, giving you the confidence to live without constant worry. Learn more about CGM best practices from the American Diabetes Association or access Dexcom’s official support page for device‑specific walkthroughs.