Integrating Hybrid Data Pipeline with a Google OAuth 2.0 authorization flow to access Google Analytics
Hybrid Data Pipeline must be integrated as a client application into a Google OAuth 2.0 authorization flow to create a data source for accessing Google Analytics. The following workflow outlines the tasks required to achieve this integration. The remaining topics in this section provide detailed instructions for these tasks.
1. Hybrid Data Pipeline must be registered as a client application with the Analytics API in the Google Developer Console.
2. The OAuth applications API must be used to create an OAuth application object. The OAuth application object holds the client ID and secret provided by Google. This information allows Hybrid Data Pipeline to identify itself as a registered application with the Analytics API.
3. An OAuth profile must be created as part of the process of creating a data source on a Google Analytics data store. (Once a profile has been created, it may be selected by a user during the creation of subsequent data sources.)
If creating the data source through the Web UI, the user enters the name of the new OAuth profile in the OAuth Profile Name field. Then, the user clicks Authorize with Google. The user is redirected to Google where he or she must login to Google. When the user clicks Accept, Google sends access and refresh tokens to Hybrid Data Pipeline. The user is then returned to the Hybrid Data Pipeline interface to finish creating the data source.
If creating the data source with the Hybrid Data Pipeline API, the user must begin by obtaining OAuth access and refresh tokens from Google. Then, the user creates an OAuth profile object with the OAuth profile API. Once the OAuth profile has been created, the user can proceed with creating the data source using the Data Sources API.
If creating the data source through the Web UI, the user enters the name of the new OAuth profile in the OAuth Profile Name field. Then, the user clicks Authorize with Google. The user is redirected to Google where he or she must login to Google. When the user clicks Accept, Google sends access and refresh tokens to Hybrid Data Pipeline. The user is then returned to the Hybrid Data Pipeline interface to finish creating the data source.
