BigQuery - Integrate Data Transfers

BigQuery Data Transfers facilitate syncs of data from Google-affiliated products and funnel the resulting payload into BigQuery. Since these data transfers are between Google products, they are based on out-of-the-box reports.

During configuration, users have the option of choosing the report they would like to import. This, unfortunately, means there is no room for upstream customization.

While it might be intuitive to worry about a given report not having a specific field, the opposite is often true. Google's reports often contain so much data that it is necessary to construct views to extract only information that is relevant to your use case.

Data Transfers Require Authentication

Like other BigQuery integrations, data transfers require authentication.

• Luckily, since the transfer is initially configured in the UI, it is a simple auth flow.
• Using Oauth2, a user setting up a BigQuery transfer is required to log into and verify the account connected to Google Cloud Platform.
• Once authenticated, developers can choose from a drop-down of Google products and report types.

One of the most important aspects of the process, to facilitate ease of use with the resulting data, is to provide a memorable name as the suffix of the resulting table.

Note − There are certain reports like billing reports that do not allow users to change the name of the ingested tables.

Examples of Reports

Examples of reports that can be scheduled as Data Transfers include −

• DFP
• Google Ad Manager
• YouTube Channel Reports

These out-of-the-box reports can remove the development burden for certain BigQuery-compatible data resources.