Google BigQuery
Source (Direct Connection) — Vendo reads directly from your BigQuery datasets using a shared service account. No data is copied — queries run in your project.
What Vendo Accesses
Vendo connects to your BigQuery project and queries tables directly for use in attribution models, audience segments, and data models.
Supported Data
| Data | Description |
|---|---|
| Any Table | Read from any table or view in authorized datasets |
| Partitioned Tables | Supports date-partitioned and ingestion-time partitioned tables |
| Nested/Repeated Fields | Full support for STRUCT and ARRAY columns |
| Views | Authorized views and materialized views |
Connection Behavior
| Behavior | Description |
|---|---|
| Direct Query | No data import — Vendo queries your tables in place |
| Service Account | Uses a shared service account with read-only access |
| No Storage Cost | No data duplication — queries run against your existing tables |
| Schema Auto-Detection | Vendo discovers your table schemas automatically |
Platform Details
| Setting | Value |
|---|---|
| Auth Method | Service account key (JSON) |
| Connection Type | Direct connection (no sync) |
| API | BigQuery Storage Read API |
| Billing | Queries billed to your GCP project |
Common Use Cases
- GA4 data — Query GA4 BigQuery exports for attribution and analytics
- Custom datasets — Use existing warehouse tables as sources for models and segments
- Cross-platform joins — Join BigQuery data with other Vendo sources
- BQML models — Run predictions on existing tables
Setup
- Navigate to App Connections > Add App Connection
- Select Google BigQuery from the data warehouse category
- Upload your service account JSON key or paste it inline
- Grant the service account
BigQuery Data ViewerandBigQuery Job Userroles on your project - Select which datasets Vendo should have access to
- Click Save — Vendo will auto-discover your tables
Permissions Required
The service account needs these IAM roles on your GCP project:
| Role | Purpose |
|---|---|
roles/bigquery.dataViewer | Read table data and metadata |
roles/bigquery.jobUser | Execute queries |
Troubleshooting
- “Permission denied” errors — Ensure the service account has the correct IAM roles on the specific datasets
- Tables not appearing — Check that the service account has access to the dataset (dataset-level permissions, not just project-level)
- Slow queries — Queries run in your project using your compute quota. Consider using partitioned tables and clustering for large datasets
Last updated on