Skip to main content
Veyda draws on a wide range of data sources to build its picture of your health — from the continuous stream of readings your smartwatch generates to the meals you log manually. The more sources you connect and the more consistently you use them, the more complete and accurate your insights become. Understanding how Veyda ingests, interprets, and reconciles data from different sources helps you get the most out of the platform.

​
Types of data sources

Veyda supports three categories of data sources, which you can connect and manage from your account settings. Wearables are devices you wear throughout the day that passively collect health data. Veyda supports smartwatches, fitness trackers, and continuous glucose monitors (CGMs). These devices provide the most granular, continuous data streams — typically recording metrics every few seconds or minutes without any manual effort. Health platform apps act as aggregators that collect data from multiple devices and apps on your behalf. Veyda connects to Apple Health, Google Fit, and Garmin Connect, among others. Connecting a health platform often gives Veyda access to data from devices and apps you’ve already set up, reducing the need to connect each source individually. Manual logging lets you record data that your devices don’t capture automatically — such as nutrition, body weight, mood, or specific symptoms. Manual entries are treated as first-class data points alongside sensor-generated readings.

​
How data syncs

Veyda syncs data from connected sources in two ways:
  • Automatic background sync runs continuously while the Veyda app is active on your device. New readings from connected wearables and health platforms are pulled in as they become available, typically within minutes of being recorded.
  • Manual refresh lets you trigger an immediate sync at any time from the Data Sources screen. Use this if you’ve just completed a workout or logged a meal and want Veyda to reflect the latest data before viewing your insights.
Sync your wearable with its companion app at least once a day to ensure Veyda always has your most recent data. Gaps in sync history can reduce the accuracy of trend-based insights and recovery scores.

​
What Veyda collects

Veyda pulls specific data types from your connected sources. The exact metrics available depend on your devices and the health platforms you’ve connected.
Activity data covers how you move throughout the day. Veyda collects:
  • Step count — Total daily steps, broken down by hour where available.
  • Active minutes — Time spent in moderate or vigorous physical activity.
  • Workouts and sessions — Type, duration, distance, pace, and calorie estimates for logged exercises, including runs, cycling, swimming, strength training, and more.
  • Floors climbed — Available from compatible smartwatches and trackers.
  • Calories burned — Both active calories (from exercise) and total daily energy expenditure (TDEE) where supported.
  • VO2 max estimates — Where provided by your device’s firmware.
Veyda uses activity data to contextualize recovery, set training load baselines, and evaluate progress toward fitness goals.
Sleep data helps Veyda understand your recovery and its downstream effects on other metrics. Veyda collects:
  • Sleep duration — Total time asleep, including naps where logged.
  • Sleep stages — Light, deep, and REM sleep proportions, where your device supports sleep staging.
  • Sleep schedule consistency — Bedtime and wake time patterns over time.
  • Sleep scores — Proprietary recovery scores from Garmin, Oura, WHOOP, and other supported platforms, where available.
  • Overnight HRV and resting heart rate — Recorded during sleep for stable, uninterrupted baseline readings.
Sleep is one of the most influential inputs in Veyda’s insight engine. Consistent, high-quality sleep data significantly improves the accuracy of recovery, readiness, and stress-related insights.
Heart and recovery data captures how your cardiovascular system responds to stress, exercise, and rest. Veyda collects:
  • Resting heart rate (RHR) — Recorded throughout the day and during sleep.
  • Heart rate variability (HRV) — The variation in time between heartbeats, used as a proxy for autonomic nervous system balance and recovery status.
  • Heart rate zones — Time spent in each heart rate zone during workouts.
  • Blood oxygen saturation (SpO2) — Where recorded by your device, typically during sleep.
  • Respiratory rate — Available from select wearables.
  • Stress scores and body battery readings — Proprietary recovery metrics from platforms such as Garmin and Fitbit.
Veyda uses these signals together to calculate your daily readiness and flag anomalies that may warrant attention.
Nutrition data is collected through manual logging or connected apps such as MyFitnessPal and Cronometer. Veyda collects:
  • Caloric intake — Total daily calories and meal-level breakdown where available.
  • Macronutrients — Protein, carbohydrates, and fat.
  • Hydration — Water intake, where logged.
  • Blood glucose — Continuous readings from connected CGMs, or manual spot readings.
Nutrition data is optional. If you don’t log food, Veyda will still generate insights from your other data sources, but nutrition-correlated insights — such as post-meal glucose patterns or energy availability during workouts — won’t be available.

​
Data quality and insight accuracy

The quality of your insights depends on the consistency and completeness of your data. Veyda is designed to handle imperfect data gracefully — gaps, missed days, and occasional outliers won’t break your insights — but they do affect their accuracy. Consistency matters more than completeness. A few days of missing data are far less disruptive than inconsistent wearing habits. If you wear your device sporadically, Veyda has a harder time establishing a reliable baseline, which reduces the relevance of trend and anomaly insights. Conflicting data from multiple sources is reconciled automatically. If two connected sources report different step counts for the same time period, Veyda applies a priority order based on source reliability and sensor quality to select the most accurate reading. Gaps in data are flagged, not fabricated. Veyda never interpolates or estimates missing values. If data is missing for a period, that gap is noted in your timeline and excluded from trend calculations to avoid skewing your baseline.

​
Historical data import

When you first connect a data source, Veyda imports your historical data going back as far as the source supports — typically up to two years for most wearables and health platforms. This historical import gives Veyda an immediate head start on building your personal baseline, so your early insights are more meaningful than they would be with only a few days of data. Historical import runs once in the background after you connect a source and does not affect ongoing sync performance. You can monitor import progress from the Data Sources screen in the Veyda app.