How to escalate a BigQuery transfer issue to Supermetrics support

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.

  1. Resource name (pasted in text format)

  2. Transfer logs for each faulty transfer visible in the screenshot (as screenshot similar to below)

  3. Transfer run status with dates (as screenshot similar to below)

  4. 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:

You can see all tables for Big Query transfers here:

Click the data source name you're using and select Data Warehouse Tables.

A potential discrepancy in BigQuery transfers

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

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.