> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dqlabs.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# BigQuery — What We Collect

> The metadata, tags, lineage, and usage data Prizm extracts from BigQuery.

Prizm reads metadata, tags, lineage, and job history from BigQuery and the related Google Cloud APIs. It doesn't change datasets, tables, or data.

## Catalog Metadata

| Prizm asset | BigQuery object | Source |
| :- | :- | :- |
| Project | Google Cloud project | Resource Manager API |
| Dataset | BigQuery dataset | `INFORMATION_SCHEMA.SCHEMATA` or the REST API |
| Table | Table in a dataset | `INFORMATION_SCHEMA.TABLES` or the REST API |
| Attribute | Table column, including nested fields | `INFORMATION_SCHEMA.COLUMNS` and `COLUMN_FIELD_PATHS` |

## Tags and Classification

Tag import is optional and off by default. It needs the extra tag permissions listed in [Setup](/sources/bigquery/setup#grant-the-required-roles).

| Item | Source |
| :- | :- |
| Labels on datasets and tables | `SCHEMATA_OPTIONS`, `TABLE_OPTIONS`, or the datasets and tables APIs |
| Policy tags and their column mappings | `COLUMN_FIELD_PATHS` or the table schema |
| Resource tags (keys and values) | Resource Manager tag bindings |
| Data Catalog tags and aspects | Dataplex Catalog and Data Catalog entries |

## Lineage

| Lineage mode | Coverage |
| :- | :- |
| Via DataPlex API | Table-level lineage for query, load, and copy jobs from the Data Lineage API. Covers only jobs run after the API was enabled in the project. The API is regional, so the location you set must match where your jobs run |
| Job Logs (`INFORMATION_SCHEMA.JOBS`) | Source and destination tables of each job. Useful for history from before the Data Lineage API was enabled. DML targets and view-to-table links are weaker. LOAD, EXTRACT, and COPY jobs aren't covered yet |

You choose one mode per connection. Column-level lineage isn't covered yet.

## Usage and Performance

| Signal | Source |
| :- | :- |
| Job history and query activity | `JOBS_BY_PROJECT` or `JOBS_BY_ORGANIZATION` |
| Job timelines and performance | `JOBS_TIMELINE` |

`JOBS_BY_ORGANIZATION` requires the role at organization level. See [Setup](/sources/bigquery/setup#grant-the-required-roles).

## Next Steps

> **[Setup](/sources/bigquery/setup)**
>
> Enable APIs and grant the roles each item needs.

> **[FAQ](/sources/bigquery/faq)**
>
> Common questions about the BigQuery connector.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.