What is the Data Warehouse
The Data Warehouse gives your tenant a dedicated Google BigQuery dataset of pre-built SQL views over your support data — conversations, contacts, agents, teams, messages, and more. Once provisioned, you can connect any BI tool that speaks BigQuery, or run SQL directly with a service account key.
This is the answer for teams who’ve outgrown the built-in Analytics dashboards and need to join Atender data with everything else they have in a warehouse.
How it differs from Analytics
Built-in Analytics is for the in-app view: KPIs, dashboards, and standard reporting surfaces. Fast to load, but the dimensions are fixed.
The Data Warehouse is for everything beyond that:
- Custom SQL joins between Atender data and your CRM, billing, or product analytics
- Long-running queries that would time out in the app
- Feeding a BI tool of your choice (Looker Studio, Tableau, Metabase, Sigma, anything that connects to BigQuery)
- Cohort analysis, retention curves, custom funnels — anything that needs SQL flexibility
Some Analytics reporting is BigQuery-backed, while newer in-app Analytics tiles may be backed by Atender’s application database instead. For BigQuery-backed reports, you can compare the report output to the corresponding Data Warehouse views when reconciling numbers. For v2 or Postgres-backed in-app tiles, the tile may not be a direct parity check against the warehouse.
When reconciling, compare the same metric definition, source, filters, and time window. Differences in when data is counted, which source powers the metric, or how the time range is applied can explain gaps even when both surfaces are working correctly.
What you get when you provision
When you click Provision Data Warehouse, Atender:
- Creates a dedicated BigQuery dataset for your tenant
- Generates a set of SQL views — conversations, contacts, agents, teams, messages, and others — pre-shaped for analytics use
- Creates a service account scoped to that dataset only
You then download a service account JSON key from Atender’s UI, point your BI tool at the project and dataset, and authenticate with the key.
The data refreshes continuously — there’s no manual sync to schedule. As things happen in Atender, the views see them.
Credentials
Service account keys are stored on Google’s side; Atender hands you the JSON file once at download time. If you lose it, you can’t re-download — you generate a new one. You can revoke all keys at once if a key leaks; existing BI connections will fail until you replace them.
The credentials panel always shows the active key count so you know how many are out there.
Re-provisioning
When Atender ships new views or columns, an hourly check applies the updates to your dataset automatically. You don’t need to press anything after a deploy — the views are updated in place, and running queries keep working.
The automatic rebuild only touches view definitions. It never changes your credentials or grants, so existing service account keys and BI connections are unaffected.
Re-provision Views in the Connection Details card is still available if you want to apply updates on demand. If your workspace was renamed after its first provision, the hourly rebuild skips it and the card keeps showing Update available. Clicking Re-provision Views then builds the views in a new dataset named after the new workspace name: your service account keys keep working, but point your BI tool at the Dataset shown in Connection Details.
Limits to know
- One dataset per tenant
- Service account keys: generate as many as you want, but each one is a credential to track
- BI tool support: anything that speaks Google BigQuery works; if your tool doesn’t, this isn’t the right surface