Who Needs to Reauthorize

Find out which participants must reauthorize for the Google Health API: active, longitudinal, demo, and test accounts, versus those finishing before the cutoff.

How to Reauthorize Participants

Walk participants through Google Health API reauthorization in the Google Health app Partner apps screen or a Fitabase link, and track who needs to reconnect.

Reauthorizing Demo and Test Accounts

Reauthorize study-managed demo and test accounts yourself from the Requires reauthorization tab using Connect to Google Health and the account's credentials.

Changes to Data Exports

Review how Fitabase exports change with the Google Health API: new UTC, time zone, and source columns, unchanged column names, and tips for export scripts.

Dataset Availability

See which Fitabase exports include Google Health API data today, which are delayed, which stay Fitbit API only, and which datasets are new in Google Health.

Sample Message for Participants

Use this sample email or script to tell participants they must grant Fitabase permission again, in the Google Health app or with their reauthorization link.

Key Dates and Timeline

Plan around key Google Health API migration dates: when reauthorization opens, the October 30 Fitbit Web API shutoff, and the November 30 reconnect window.

Migration FAQ

Get answers to common researcher questions about the Google Health API move, including reauthorization, invitation links, IRB, step goals, and sleep data.