--- title: "Going Live with Google Health in Production" canonical: "https://help.validic.com/space/VCS/5788041217/Going%20Live%20with%20Google%20Health%20in%20Production" format: markdown --- Google Health source is production ready on the Validic side, and Validic's CASA assessment no longer blocks your production release. We know this process has shifted significantly. Both our communication about the path to production and Google's own requirements have evolved. Those changes stem from adjustments to Google's guidance. We're sharing this information to clarify the next steps to production so you can have a successful Google Health release before the Sept 30th Fitbit API sunset. # Release Steps ## Step 1: Test in your sandbox Validic org with GCP project credentials  - If you haven’t delivered sandbox credentials to Validic support to start your testing, then use the instructions below to get started with testing in your sandbox - [Create production credentials](https://help.validic.com/space/VCS/5581111299/Google+Health:+Getting+credentials+from+Google+Console): - Set required scopes per documentation. Only enable the scopes you will actually use - These credentials will always remain in testing status to ensure you only have to do one Google assessment process on your production GCP project and Google Health API credentials. Do not click “Publish this app” in the GCP project your sandbox credentials exist in. - [Enable webhooks](https://help.validic.com/space/VCS/5754421279/Google+Health:+Enable+webhooks+for+near+real+time+data+delivery) (required for production, so you should test with it in sandbox) - Follow the instructions in each of those docs to deliver the needed information to Validic support so we can enable Google Health in your sandbox org for testing - Things you should be aware of and have plans for regarding Fitbit and Google Health sources in marketplace: - Control visibility planning for production rollout: - For custom marketplaces with control over sources displayed in your UI, hide Fitbit when enabling Google Health to stop new connections to Fitbit, or explore one of the below options. - You can disable the connect option for Fitbit and only expose the disconnect for users previously connected to Fitbit - If you choose to keep both sources in your custom marketplace, then notify users that Fitbit is sunsetting with a banner or pop-up when the end user engages with the Fitbit source. - If you have no control over what sources display from custom marketplace JSON or use standard marketplace, then Validic can assist with removing the Fitbit source when you go live with the Google Health source - Critical: Users can connect to both Fitbit and Google Health simultaneously. Even with the Fitbit source removed from the marketplace, previously connected Fitbit users will continue to sync data from the Fitbit API. Prior to Google sunsetting the Fitbit API on Sept 30th, you should be prepared to see users with both google_health and fitbit data payloads coming to you. Implement logic to prioritize Google Health if present, and fall back to Fitbit if not. Test this scenario before launch. - Verify that your mapping allows you to ingest Google Health data payloads from either the Streaming API or the Push service. When you determine you are ready to move to production release, move to the next step. ## Step 2: Prepare in Google Cloud Platform - [Create production credentials](https://help.validic.com/space/VCS/5581111299/Google+Health:+Getting+credentials+from+Google+Console): - Set required scopes per documentation. Only enable the scopes you will actually use - [Enable webhooks](https://help.validic.com/space/VCS/5754421279/Google+Health:+Enable+webhooks+for+near+real+time+data+delivery) (required for production) - Publish app to production in GCP (triggers [OAuth verification](https://help.validic.com/space/VCS/5539037190/Requirements+and+Assessments+FAQs+for+Google+Health+API)) - Publishing your production credentials in GCP triggers OAuth verification, Google's review of your requested scopes, redirect URIs, and connection flow. This is separate from brand verification, which confirms your domain ownership and controls whether your app name and logo appear on the consent screen instead of the authorized domain. - If you have not already completed brand verification ([console.cloud.google.com/auth/branding](http://console.cloud.google.com/auth/branding)), do that first or in parallel. Until brand verification completes, your OAuth consent screen will continue to show "syncmydevice.com wants access to your Google Account" rather than your app name and logo, even after OAuth verification is submitted or approved. This is expected: syncmydevice.com is Validic's marketplace redirect domain, added automatically as an authorized domain when you configure the redirect URI from our docs, and it is what displays on the consent screen until your own branding is verified. If Google asks for a demo video during OAuth verification and your consent screen still shows syncmydevice.com instead of your app name, check your Branding page status before assuming there is a problem with your submission. - Once both brand verification and OAuth verification are complete, your branded consent screen will display and unverified app warnings will disappear in the Google OAuth flow for Google Health. Completing both will have you ready to expose the Google Health source to end users. ## Step 3: Contact Validic Support Email [support@validic.com](mailto:support@validic.com) with:  - Credentials JSON file (secure delivery required, and Validic support can assist with that) - Scope confirmation - Webhook JSON (secure delivery required, and Validic support can assist with that) - Production org ID confirmation  Also confirm:  - Do you control which sources display in your custom marketplace, or do you use the standard marketplace? - What's your plan for Fitbit transition before Sept 30? See the section in Step 1 about options for handling the Fitbit source when you enable Google Health - Do you have a date for your go live with Google Health? - Are you expecting more than 100 connected users? If so, then complete your [CASA assessment ](https://help.validic.com/space/VCS/5539037190/Requirements+and+Assessments+FAQs+for+Google+Health+API#Step-4:-Complete-your-CASA-assessment)before going live. **Google will only allow 100 users to connect to Google Health API credentials until CASA is completed for that GCP project. ** ## Step 4: Validic Enables Google Health - Custom marketplace with source control: We enable it, you decide when to expose to users. - No source control or standard marketplace: We coordinate timing with you. - You reach your go live date and end users can connect to Google Health through the Validic marketplace!!! ## Step 5: Complete CASA [CASA assessment](https://help.validic.com/space/VCS/5539037190/Requirements+and+Assessments+FAQs+for+Google+Health+API#Step-4:-Complete-your-CASA-assessment) doesn't block your release, but there is a 100 connected user limit until CASA is completed. If you are only expected less than 100 connected users to Google Health in your production org, you can do CASA assessment in parallel to your go live. If you are expecting more than 100 connected users, then complete your CASA assessment before go live. # Questions?  Reply to your support case or email [support@validic.com](mailto:support@validic.com).