Data Availability

Your user has connected their data source and now? Simple: We'll get all data you need asap and all data updates in near-time. However, there are some limiting factors you need to be aware of.

At Thryve, we retrieve all data made available by the data sources. While we optimize to get data as fast as possible, there are still cases where data seems missing. There are many factors that can cause this, so we've grouped the most prominent factors affecting data availability:

Device and Sync Factors

Data Has Not Arrived at the Data Source

We cannot access data from a data source if it hasn't arrived yet. Most users record data with wearable sensors (e.g., Apple Watch), but these devices rarely stream data in real-time. Instead, data is synced in batches with smartphones, creating delays between recording and availability.

Common sync delay factors:

• Bluetooth connectivity: Users turning off Bluetooth or moving out of range

• Operating system optimizations: Energy-saving mechanisms and background process termination

• Network connectivity: For web data sources, data must reach the cloud before we can retrieve it

Important note: For web data sources, data can only be retrieved once it reaches the data source's cloud. Data being visible in a smartphone app doesn't guarantee it has synced to the cloud yet.

Device Capabilities

Not all devices within a data source ecosystem can record all data types. Older devices may lack certain sensors (e.g., SpO2 measurement capability) even though these data types are listed in our data source overview. Some measurements may also be limited to specific geographic regions due to regulatory requirements.

User Behavior Factors

End-User Activity in Your App

For native data sources, the Thryve SDK synchronizes data through your app on the user's device. This process depends heavily on the operating system, allowing synchronization, especially in the background.

When users don't regularly use your app, the operating system may:

• Reduce background data retrieval frequency

• Completely terminate background processes when prioritizing more frequently used apps

Regular app usage helps maintain consistent data synchronization.

End-User Activity in Data Source Apps

For web data sources, users must actively use the manufacturer's apps (e.g., Fitbit, Garmin Connect, Polar Flow) to ensure proper data flow. When users don't regularly open these apps, two critical sync processes are affected:

• Device-to-app sync: Data remains on the wearable device and doesn't transfer to the smartphone app

• App-to-cloud upload: Data stays locally in the app and doesn't reach the manufacturer's cloud servers

Since Thryve can only access data once it reaches the manufacturer's cloud, inactive users may experience significant data gaps even if their devices are recording properly.

System and API Limitations

API Data Availability Restrictions

Unfortunately, not all data visible in smartphone apps is made available to third parties through APIs. Data source manufacturers may restrict:

• Specific data granularities: Some data types are only available at the daily level without intraday breakdowns.

• Certain data types: Complete categories of data may be unavailable to third parties, this is specifically referring to scores and more complex assessments done by wearable devices.

Please note that certain data sources, like Fitbit or Polar, have limitations on the data available via API. Please check the dedicated data source pages for further information.

Best Practices for Data Availability

For Developers:

• Implement graceful handling of missing data periods

• Don't assume real-time data availability

• Consider data source-specific limitations when building features

For End Users:

• Encourage regular app usage to maintain background sync

• Ensure devices stay connected and charged

• Keep data source apps updated for optimal sync performance