Infeasible
Status Update
No update yet.
Comments
pu...@google.com
ja...@google.com
Thank you for reporting this issue.For us to further investigate this issue, please provide the following additional information:
Please provide the bugreport immediately after the issue is reproduced.We need bugreport to investigate this issue.
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:https://developer.android.com/studio/debug/bug-report#bugreportdevice
Alternate method:
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.
Please provide the bugreport immediately after the issue is reproduced.We need bugreport to investigate this issue.
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:
Alternate method:
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.
Description
We tried to sync a BigQuery table to populate a Google Ads customer list. Both BigQuery and Google Ads users have admin permissions to both systems.
"Can't connect to BigQuery. Make sure your Google Cloud permissions are set up correctly and try again. (Error code: 21)".
Even if the connection is created, when running the sync manually, no rows are imported.
What you expected to happen:
The table to sync and import rows into a Google Ads customer list.
Steps to reproduce:
1. Create a new connection in a customer list in Google Ads.
2. Try to sync to the table from a project.
3. Run a manual sync or a schedule sync.
Other information (workarounds you have tried, documentation consulted, etc):
* We added the service accounts in this support article:
* We opened a ticket with Google Ads Support, who said this is a BigQuery issue.