How To Connect Your Dexcom G7 to Levels For Sensors Obtained Elsewhere

This article will walk you through a step-by-step process for setting up your own Dexcom G7 sensors with the Levels app. With this option, you will be able to sync your glucose data from the Dexcom G7 app to Levels via Apple Healthkit (iOS) or Health Connect (Android). 

⚠️ Please note: This option has a 3-hour data delay from the Dexcom G7 app to the Levels app.


To connect a sensor obtained elsewhere, follow the steps below:

For iPhone users:

  1. Open the Levels app
  2. Tap More Devices → Manage
  3. Click Choose Sensor Type
  4. Select Dexcom G7 →  Apple Health  

5. Next, go back to the Today screen and you should be prompted to connect your Levels app to Apple Health

  • If you do not see a prompt, please open the More tab, select Settings, and tap the Connect button next to Apple Health (more information here).

6. Once your Levels app is successfully connected to Apple Health, head over to the Dexcom G7 app
7.  Select Connections
8. Select Apple Health, you’ll then be prompted to open your iPhone settings

9. Open your iPhone settings and select Health (see image below step)
10. Select Data Access & Devices 
11.  Select Dexcom G7
12.  Toggle ON Blood Glucose to allow the Dexcom G7 to write data to the Levels app
Once complete, glucose data will begin streaming into Levels on a 3-hour delay. The delay is a result of the timing of the sync between the Dexcom app and Apple Health. Apple Health receives glucose data from Dexcom every 3 hours.

For Android users:

  1. In the Levels app, tap More and then tap Settings
  2. Look for the Connect to Health Connect section and click Connect.
  3. Once the new screen appears, click Connect to Health Connect.
  4. Toggle on Allow all to allow Levels to access Health Connect. Scroll down and confirm by clicking Allow.

If you encounter any issues setting up your Dexcom <> Levels connectivity, email us at support@levels.com.

Did this article answer your question? Thanks for the feedback! There was a problem submitting your feedback. Please try again later.