BigQuery Agent Analytics

Your telemetry. Your dashboard.

Enter your fully qualified BQAA table ID. We’ll prepare a private copy of the published Looker Studio dashboard, connected with your Google credentials.

37 parity charts
8 report pages
No data leaves Google

Connect your BQAA data

Only the BQAA event table is required. Generated views are not used.

Fully qualified BQAA table ID project.dataset.table — one ID names all three. The plugin’s standard table is agent_events. Paste a fully qualified table ID or a BigQuery Console table link; backticks, a legacy colon after the project, and a trailing ; or , are cleaned up automatically. Charts read this table directly and extract reporting fields from its JSON columns.

Advanced settings

Billing project ID Optional. Leave blank to run queries in the source project.

Create my dashboard

Opens lookerstudio.google.com in a new tab. Building your private copy can take up to ~10 seconds, and the tab may briefly show an error page while Google provisions the report — don’t close it. One dialog is different: if the tab says “This report isn’t shared with you”, waiting will not fix it — see the note below.

This page has no backend. It sends no identifiers or credentials to the template owner; it only creates a Google Looker Studio URL. Verify in this page’s source.

Enter your table ID

Paste or type the fully qualified ID of the base table configured for the ADK BigQuery Agent Analytics plugin — project.dataset.table, one value naming all three.

Review in Google

The new tab may briefly show a loading or “not found” page while Google provisions your copy — don’t close it. (A dialog quoting “This report isn’t shared with you” is not that flicker; see below.) Looker Studio then shows an acknowledgement dialog. It appears because you’re about to create a data source that runs a SQL query this page supplied — read the exact query. The dialog lists that query, your billing project, and that the new data source initially uses Owner’s Credentials; nothing is created until you acknowledge it. The query reads only your table, using the opener’s credentials, in your billing project.

Save, then secure sharing

Choose “Edit and share” to save it. Before sharing, set the new data source’s credentials to Viewer’s Credentials so every viewer must have their own BigQuery access.

“This report isn’t shared with you” is not a setup error. That dialog is terminal — it offers Reload / Return to report list / Go to report template and does not resolve by waiting. It means the shared dashboard template is unavailable to the Google account signed in to that tab; nothing is wrong with your project, dataset, table, IAM setup, or the identifiers you entered. First confirm the tab is using the account you intend (Looker Studio uses the browser’s default Google account). If you are signed in with an organization-managed account, your own organization’s sharing policy can also block receiving Looker Studio assets from external domains — try a personal account if you can. If the dialog still persists, the template’s copy path is blocked — report it on issue #445 — say only whether the signed-in account is personal or part of an organization; do not post the account’s email address. The repository’s CLI preflight can still validate your table, but it copies the same template, so it is not a workaround; while the template is blocked, use the Grafana dashboard.

Required security check

Before you share the new report

The Linking API creates a new data source owned by the person who opens the link. Keep the report private until these checks pass.

Select Edit and share to save your copy.
Keep the report private while configuring its data source.
Open Resource → Manage added data sources → Edit.
Set Data credentials to Viewer’s Credentials.
Test the report with an account that has only viewer access.