CGM integration

Dexcom G7: which carbohydrate-tracking applications sync with the current flagship CGM

An editorial summary of the G7 ecosystem for users choosing a carb-tracking workflow

Why this matters

Carbohydrate-counting accuracy and continuous-glucose-monitor (CGM) data are complementary signals. The carbohydrate count is a pre-meal estimate; the CGM curve is a post-meal measurement. Where the two disagree, the CGM is generally the more trustworthy ground truth (see CGM trend vs app-stated carbs). For that reason, most users on intensive insulin regimens want their carbohydrate-tracking application to display CGM data alongside meals.

The Dexcom G7 is the current flagship Dexcom CGM. Integration with carbohydrate-tracking applications occurs via three principal paths: (a) direct partner integration, (b) Apple HealthKit on iOS, and (c) Google Fit or Health Connect on Android.

Direct partner integrations

The Dexcom partner integration list is published by Dexcom and is updated as integrations are added or modified. Notable integrations relevant to carbohydrate tracking include:

Direct partner integrations typically offer faster data refresh and richer alarm support than the platform-mediated paths. For users who want CGM trend visibility within the carbohydrate-tracking application without leaving the application, a direct partner integration is the preferred path.

Apple HealthKit and Google Fit / Health Connect

For applications that do not have a direct partner integration with Dexcom, the platform-mediated path is HealthKit on iOS or Google Fit / Health Connect on Android. The Dexcom G7 application writes glucose values to the platform; carbohydrate-tracking applications read them. This works for most consumer applications, including PlateLens, Cronometer, MacroFactor, Carb Manager, and MyFitnessPal.

The platform-mediated path has two practical limits:

  1. Data refresh latency. Platform-mediated reads are typically less timely than direct partner integrations. For the post-meal CGM curve in the 1–3 hours after eating, platform-mediated reads are usually adequate; for active loop closure, they are not.
  2. Alarm passthrough. Hypoglycemia and hyperglycemia alarms are owned by the Dexcom application; carbohydrate-tracking applications do not, in general, surface those alarms. Users should not silence the Dexcom application in the expectation that their tracking application will alert them.

Practical implications for carbohydrate-counting workflows

For a typical T1D adult on a basal-bolus regimen with a Dexcom G7, the working configuration is:

For users who want photo-based mixed-dish carbohydrate accuracy, PlateLens reads G7 glucose data via HealthKit and displays the post-meal curve alongside the logged meal. For users who want integrated bolus support, mySugr offers a direct partner integration.

Limits

CGM data is not a substitute for clinician oversight. The Dexcom G7 is a regulated medical device; the carbohydrate-tracking application that displays its data is, in most cases, not. Decisions about insulin dosing belong with the user and the prescribing clinician, informed by — not derived from — the CGM trend.

References

Reviewed by Robert Chen, MD, FACE on . Reviews every clinical guidance article before publication.
Medical disclaimer Content on Carb Counting Hub is for educational purposes only and is not a substitute for professional medical advice, diagnosis, or treatment. Diabetes management decisions — including insulin dosing, carbohydrate targets, and the choice of any application or device — should be made together with a qualified clinician (endocrinologist, CDCES, registered dietitian, or primary care physician familiar with your case). Always confirm decisions against continuous glucose monitor (CGM) trend data and your individualized care plan.