Skip to main content

Linking and Syncing Strove with Health Connect

To help Android users link Health Connect with Strove, ensuring that activity, steps, and heart rate data sync correctly from your connected fitness apps and wearables.

Updated over a week ago

Overview

Health Connect is Google’s central health data platform that allows multiple fitness and wellness apps to share data securely. By connecting Health Connect with Strove, your data from apps like Samsung Health, Fitbit, Zepp, Huawei Health (via Health Sync), and others can flow automatically into Strove, letting you earn Strove Coins for your activity.

Think of Health Connect as the “hub” between your fitness tracker and Strove. If your data shows up in Health Connect, Strove can read it.

How to link Health Connect to Strove

  1. Open the Strove app on your Android device.

  2. Tap the Settings icon (top right of the home screen).

  3. Select Connected Apps.

  4. Tap Connect to Health Connect.

  5. When prompted, tap Allow All (or toggle individual data types to “On”) to grant permissions.

Your accounts are now linked, and any activity data recorded through connected apps will automatically sync with Strove.

Important Notes

  • Strove can only access data stored in Health Connect. Ensure that your fitness app (e.g., Samsung Health, Fitbit, Zepp, or Mi Fitness) is properly linked to Health Connect.

  • Manually entered activities in your fitness app will not sync to Strove. Only tracked data is shared.

  • Activities recorded before linking Health Connect may not always sync retroactively.

  • Syncing typically occurs automatically within a few minutes but may take up to an hour depending on app activity and network conditions.

Troubleshooting Heart Rate and Activity Syncing

If you notice that workouts appear in Strove but lack heart rate data (or don’t appear at all), follow these steps:

  1. Check that your fitness app is connected to Health Connect:

    • Open Health Connect → App Permissions → [Your Fitness App] → Allow All.

    • Make sure the app has permission to write activity, workout, and heart rate data.

  2. Check that Strove has permission to read data:

    • Go to Health Connect → App Permissions → Strove → Allow All.

  3. Refresh your fitness app and Strove:

    • Open your fitness app (e.g., Samsung Health, Zepp, or Fitbit) and confirm that your latest activity is visible.

    • Reopen Strove and swipe down on the home screen to manually refresh your feed.

  4. Re-establish the connection:

    • In Strove → Settings → Connected Apps, toggle Health Connect off, then back on again, and confirm all permissions.

  5. Restart your device if syncing remains stuck, as this will reset background processes that handle data transfer.

If heart rate data is still missing after reconnecting, the source app may not have shared it with Health Connect. Verify in your source app’s settings that heart rate recording is enabled during workouts.

Why Heart Rate Data Matters

Heart rate data helps Strove calculate your effort-based Strove Coins, rewarding you more accurately for workouts that demand higher intensity. Without heart rate data, your activity will still sync, but your reward calculation may be based on estimated intensity rather than real metrics.

Quick Tips for Reliable Syncing

  • Keep Strove, Health Connect, and your fitness apps updated to the latest versions.

  • Ensure background permissions are granted for all apps involved.

  • Avoid force-closing Health Connect; it needs to run quietly in the background.

  • Open your fitness app periodically to trigger sync updates.

  • Use a stable internet connection when recording and saving activities.

If Your Activities Still Don’t Sync

If you’ve followed the steps above and your data still isn’t appearing in Strove:

  1. Confirm that your activity shows in Health Connect.

  2. Check if Strove is listed as a connected app under Health Connect → App Permissions.

  3. Contact Strove Support with screenshots of your Health Connect data and Strove connections for troubleshooting.

Did this answer your question?