BigQuery Transfers are created by a fixed schema built by Supermetrics Data Engineering team or custom schemas built in the Query Manager. Because of this we have limited visibility to the data pull process. To ensure proper debugging, we appreciate the following details to be shared from the transfer view in the web UI when escalating an issue to Support.
Resource name (pasted in text format)
Transfer logs for each faulty transfer visible in the screenshot (as screenshot similar to below)
Transfer run status with dates (as screenshot similar to below)
Transfer configuration view behind the EDIT button (as screenshot similar to below)
In case you find issues with the data set or need any external fields to suit your use case, we will need an example query for the data pull request. For building this we prefer to use Supermetrics for Google Sheets. In case you don’t have a license, you can enrol for a free trial here: https://gsuite.google.com/marketplace/app/supermetrics_for_google_sheets/523876908005
You can see all tables for Big Query transfers here: https://supermetrics.com/docs/
Click the data source name you're using and select Data Warehouse Tables.
A potential discrepancy in BigQuery transfers
- Create a query in Sheets displaying the metric split by dimension as they are set in the BigQuery table
For example, if you see a discrepancy in Clicks metric
Note! Please use the same date in the Sheets query as the transfer data date in BigQuery
- Compare results with Sheets and the BQ table
- If the discrepancy is present, create a ticket at support.supermetrics.com including all of these:
- Fill in consent for data access at https://team.supermetrics.com/support