Enterprise Data Warehouse
Direct table and SQL query ingestion from Google BigQuery
Connect tables or custom queries in your BigQuery project to ingest closed sales with column mapping and drop-detection safeguards.
What this integration connects
Enterprise queries executed against Google Cloud BigQuery API.
- ✓Datasets and tables tracking sales, billings, or subscriptions in your GCP project
- ✓Custom SQL queries (SELECT) supporting incremental watermark parameters (@desde)
- ✓Secure authentication via Google OAuth or service accounts
- ✓Flexible key mapping for customer identity, timestamp, value, and deal status
What you see in Ollie
Verified revenue ingested straight from your analytical warehouse.
Reconciled sales and deal values
Warehouse tables populate won stages in the marketing funnel with exact timestamps and monetary values.
Scan bytes and cost transparency
Every execution logs scanned bytes and estimated query cost in USD for full accountability.
Drop-detection canary guard
Automatic safeguard that alerts and pauses ingest if query results drop below 50% of historical average.
No-code column mapping
Intuitive interface to designate email, phone, transaction ID, and revenue columns without coding.
How to connect in 3 simple steps
No complex engineering required. Authorize and map your data within minutes.
Connect your Google Cloud account
Authenticate with a user account holding query execution (jobs.create) and table read permissions in GCP.
Designate table or custom SQL
Set your GCP billing project and pick a table or provide a SQL statement with incremental filters.
Map key identity columns
Match identity columns (email, phone), deal timestamp, and revenue amounts to Ollie destination fields.
Honest limits: what this integration does NOT do
Uncompromising security for your corporate data warehouse.
- Datasets and tables tracking sales, billings, or subscriptions in your GCP project
- Synchronized incrementally and safely into your Ollie tenant.
- Custom SQL queries (SELECT) supporting incremental watermark parameters (@desde)
- Synchronized incrementally and safely into your Ollie tenant.
- Secure authentication via Google OAuth or service accounts
- Synchronized incrementally and safely into your Ollie tenant.
- Flexible key mapping for customer identity, timestamp, value, and deal status
- Synchronized incrementally and safely into your Ollie tenant.
- Query processing billed to your GCP account
- Query computation runs on your GCP billing project. Ollie details scanned bytes and estimated cost per sync run.
- Strictly read-only access
- We execute SELECT queries only. Ollie never creates tables, modifies schemas, or deletes rows in your database.
- Requires existing identity columns
- Queries must output at least one person identifier (email or phone) to enable closed-loop attribution.
- Demands correct GCP IAM roles
- The authorized user must have bigquery.jobs.create on the billing project and bigquery.tables.getData on target datasets.
Frequently asked questions
Direct answers to operator questions regarding permissions, security, and data handling.
How much does each BigQuery query cost?
Google Cloud bills queries according to your GCP rates. Ollie run history displays exact bytes scanned and estimated USD cost.
Can Ollie modify my data in BigQuery?
No. The connector runs in read-only mode (SELECT) and lacks permissions to alter schemas or delete records.
How does incremental sync work?
You can include the @desde parameter in your custom query to fetch only records created or updated since the last run.
Connect BigQuery data directly to media decisions
Import verified sales from your warehouse with complete governance and transparency.