m-Path offers two approaches to wearable data collection: the standard wearable integration (via Thryve) and the direct Garmin integrations, which include full sensing and Garmin Lite. This page gives a brief overview of the key differences to help you decide which is the right fit for your study.
At a glance
| Standard integration (Thryve) | Direct Garmin integrations (full sensing & Garmin Lite) | |
|---|---|---|
| Supported devices | Wide range of devices via Thryve. Currently integrated: Garmin, Fitbit, Apple Health (It is also possible to integrate other sources). | Garmin smartwatches only |
| Data resolution | Lower resolution but includes computed measures (e.g. sleep, daily summaries) | Raw, high-resolution data (e.g. heart rate every second, all BBI values) |
| Data Flow | Data goes from the watch -> smartwatch manufacturer app on the phone(Garmin Connect, Apple Health, etc) -> Thryve -> m-Path servers for export | Data goes from the watch -> m-Path Sense app -> Your cloud storage location |
| Trigger-based interventions | Not available | Available in full sensing mode |
| App required | Relevant manufacturer app + m-Path | m-Path Sense only |
| Add-on required | Smartwatch integration | Sensing full |
Where the standard integration has the advantage
Broader device support
The standard integration supports a wide range of devices with data harmonization through the Thryve platform. So it’s possible to recruit participants and have them join your study with their own devices. You can find the full list of currently integrated sources on the Thryve data sources page.
Lower add-on cost
The standard integration requires the Smartwatch integration add-on, which is less expensive than the Sensing full add-on required for the direct Garmin integrations. See pricing page.
Computed measures included
Thryve provides higher-level computed measures such as sleep scores, sleep stages, and daily activity summaries that are derived from raw sensor data. If these are sufficient for your research questions, the standard integration may cover your needs without the additional complexity of the direct integrations.
Where the direct Garmin integrations have the advantage
Higher-resolution data
Both direct Garmin integrations give you access to raw, high-resolution data that the standard smartwatch integration cannot provide. This includes heart rate at up to 1-second intervals and raw beat-to-beat intervals (BBI) for HRV computation. If your research questions require this level of detail, the direct integrations are the better fit.
Privacy-first data flow
With the direct Garmin integrations, data travels directly from the watch to the m-Path Sense app and then to the researcher’s own cloud storage (pCloud or OneDrive). If avoiding third-party processors is a requirement for your study, this is an important distinction.
Trigger-based interventions (full sensing mode)
The full sensing mode of the direct Garmin integration supports real-time trigger-based interventions: you can configure conditions based on incoming sensor values (e.g. heart rate or stress exceeding a threshold) that automatically send a questionnaire or notification to the participant. This is not possible with the standard integration or with Garmin Lite.
Full sensing or Garmin Lite?
If the direct Garmin integrations are the right fit for your study, the next question is whether you need full sensing or Garmin Lite.
- Choose full sensing if you need continuous background data collection or want to trigger interventions based on real-time sensor values.
- Choose Garmin Lite if you need high-resolution data but are happy to collect it at defined moments (e.g. as part of a daily questionnaire) rather than continuously. The app does not need to run in the background between syncs, which reduces battery and permission overhead for participants.
Both are included under the same Sensing full add-on. See the pricing page for details, or contact us at contact@m-path.io to discuss which option suits your study.