Every metric & dimension
Pull the full Metabase field set - sessions, events, dimensions, and breakdowns - not just a fixed preset, so your reports and models are never missing a metric.
Metabase
Metabase
AnalyticsDataddo extracts the full Metabase metric and dimension set - sessions, events, rankings, behavior - and delivers it wherever your team needs it: into AI tools and agents, your warehouse like Snowflake and BigQuery, BI dashboards, and your marketing and CRM tools. Blend it with every other data source, backfill full history, and keep it fresh on your schedule - all fully managed, with the data plane running where you choose. No pipelines to build, no lock-in.
YOUR ANALYTICS SOURCE OF TRUTH
Turn Metabase into reporting your whole team trusts
Analytics data is only useful when it's complete, clean, and current. Dataddo extracts the full Metabase data model, governs it, and serves it to every warehouse, dashboard, AI tool, and downstream system - continuously and without manual exports.
Blend across every source
Combine Metabase with your marketing, product, and CRM data so cross-channel and full-funnel analytics live in one place.
Backfill full history
Load historical Metabase data beyond the platform's retention window, so trend, cohort, and year-over-year analysis holds up.
Model & clean before load
Normalize naming, time zones, and units, and let the Data Quality Firewall stop bad rows before Metabase data reaches your reports.
Fresh on your schedule
Incremental, scheduled syncs keep Metabase data current - as often as hourly - without manual exports or full reloads.
Governed & monitored
Delivery alerts and quality checks catch gaps in Metabase data early, so dashboards and models never silently break.
DATASETS
What you can pull from Metabase
The Metabase connector provides a list of curated datasets - ready-made sets of records, fields, and metrics you can extract on a schedule. Need something specific? Any dataset can be forked and customized, or built from scratch, with our Universal Connector.
List of curated datasets
Descriptiondescription
string
Archivedarchived
integer
View Countview_count
integer
Collection Positioncollection_position
integer
Creator Emailcreator_email
sensitivestring
Creator First Namecreator_first_name
sensitivestring
Creator Last Logincreator_last_login
datetime
Creator Is QBNewbcreator_is_qbnewb
integer
Creator Is Superusercreator_is_superuser
integer
Creator Idcreator_id
string
Creator Last Namecreator_last_name
sensitivestring
Creator Date Joinedcreator_date_joined
datetime
Creator Common Namecreator_common_name
sensitivestring
Initially Published Atinitially_published_at
datetime
Enable Embeddingenable_embedding
integer
Collection Idcollection_id
integer
Show In Getting Startedshow_in_getting_started
integer
Namename
string
Widthwidth
string
Caveatscaveats
string
Updated Atupdated_at
datetime
Made Public By Idmade_public_by_id
integer
Cache Ttlcache_ttl
integer
Idid
string
Last Viewed Atlast_viewed_at
datetime
Positionposition
integer
Archived Directlyarchived_directly
integer
Entity Identity_id
integer
Auto Apply Filtersauto_apply_filters
integer
Created Atcreated_at
datetime
Public Uuidpublic_uuid
string
Points Of Interestpoints_of_interest
string
Need a dataset, metric, or attribute you don't see?
Tell us what's missing and we'll add it to the connector.
WITH VS. WITHOUT
Who carries the load when things change
Keep Metabase data flowing to every warehouse, dashboard, and tool - and see who owns it when an API or schema changes:
| Without Dataddo |
With Dataddo
|
Outcome for you | |
|---|---|---|---|
| API or auth change | You discover the breakage and scramble to fix it. | We update the connector and restore the pipeline - often before you notice. | Syncs from Metabase keep flowing |
| Schema drift | Columns change and pipelines break or corrupt data silently. | Detected automatically and handled by configurable rules. | Only clean Metabase data lands in reports |
| Endpoint deprecated | You re-engineer the integration. | We own the update - the data contract holds. | Your Metabase reporting keeps working |
| Missing connector | You build and maintain a custom integration. | We build it and maintain it, under a ~4-week SLA. | Any Metabase data you need, on request |
| Silent degradation | You find out when a report or model run fails. | Proactive monitoring catches anomalies and delays first. | Gaps caught before dashboards break |
| Debugging | You dig through logs across disconnected tools. | Run histories, payload inspection, and end-to-end lineage in one place. | Faster root-cause, fewer reporting gaps |
Data residency by design
Choose where Metabase data is processed - same cloud, region, or sovereign
Metabase is a cloud API, so the question isn't on-prem vs cloud - it's which region your data flows through. With Dataddo you run the data plane in the region you choose, so Metabase payloads move straight to your destinations without transiting a third-party SaaS. Pin it to an EU or US region for compliance, or self-host when a downstream target lives inside your own network.
| Data Plane location | Typical data sensitivity | Why this setup |
|---|---|---|
|
Public cloud 
AWS
Microsoft Azure
Google Cloud
|
Low to moderate - general business, marketing, and product data; sources that are already cloud-native. | Fastest to stand up and scales elastically. Best when the data has no residency restriction and often already lives in the same public cloud. |
|
Regional & EU sovereign clouds
EU sovereign clouds
Regional providers
Private cloud
|
Regulated / residency-bound - PII, financial, and health data governed by GDPR or local law. | Keeps processing inside a specific jurisdiction to meet data-residency and sovereignty rules, while still running as managed infrastructure. |
|
On-premises 
Kubernetes
Red Hat OpenShift
VMware Tanzu
|
Highly sensitive / restricted - data that contractually or legally cannot leave the corporate perimeter. | Data never leaves your network. Required for air-gapped, classified, or locked-down environments; the Control Plane still manages it via metadata only. |
DATA DELIVERY
Every way to deliver Metabase data
Analytics data rarely has one home. Dataddo feeds Metabase into AI and agents, loads it into your warehouse for unified analytics, activates insights back into marketing and CRM tools, and delivers files to storage - all governed the same way.
| Transport type | What it does | Typical destinations | Typical business use cases |
|---|---|---|---|
| Data to AI™ & Agents | Feed Metabase data into vector databases, LLMs, and AI agents so copilots can reason over your analytics. | Load Metabase metrics into vector stores for retrieval-augmented analytics assistants, Give AI agents and copilots governed access to live Metabase data | |
| ETL / ELT to your warehouse | Load Metabase metrics and dimensions into your warehouse for unified, cross-source analytics. | Centralize Metabase alongside every other source in Snowflake, BigQuery, or Redshift, Backfill Metabase history for trend and cohort analysis | |
| Activate insights | Push segments and modeled metrics built from Metabase data back into ad and CRM platforms. | Sync modeled audiences and scores from Metabase to ad and CRM tools, Return insights to optimize campaigns and targeting | |
| Files to storage & partners | Deliver raw or modeled Metabase extracts to object storage and partners. | Archive raw Metabase exports to S3, GCS, or Azure storage, Send scheduled Metabase extracts to partners over SFTP |
Claude
Snowflake
BigQuery
Amazon Redshift
PostgreSQL
Google Ads
Meta
HubSpot
Salesforce
Google Cloud Storage
Azure Blob Storage
SFTP
Case Studies
See what data teams build with Dataddo
65,000 Social Media Accounts. One Platform. Zero Manual Authorizations.
Beauty & Consumer Goods
How Livesport Activates Data, Saves Engineering Resources with BigQuery and Dataddo
Entertainment
How ID&T Group Activates Data from 1M+ Festival Fans and Dozens of Social Accounts
Entertainment
How Sensire Accelerated Migration of a Proprietary On-Premise Data Infrastructure to the Cloud with Dataddo
Healthcare
How Ringside.ai Builds a Data Product Better and Faster Using Dataddo
Marketing
How Publicis Groupe Brasil Uses Dataddo's API to Scale a Data Product
Advertising
FAQ
Metabase as a source + Dataddo, answered
Where can I send Metabase data?
To any of Dataddo's 150+ destinations - warehouses like Snowflake and BigQuery, BI dashboards, CRMs and marketing tools, object storage, and AI or vector stores - plus custom destinations on request.
Do I have to maintain the pipeline?
No. Dataddo is fully managed: we maintain the Metabase connector, adapt to API and schema changes, and alert you if anything needs attention. There is no pipeline code for you to write or fix.
Can I combine Metabase with my other analytics tools?
Yes. Dataddo loads Metabase into Snowflake, BigQuery, or Redshift alongside your other analytics, marketing, and product sources, so you can build one unified view instead of stitching exports together.
What if Metabase changes their API?
That's on us, not you. Dataddo's team proactively tracks Metabase API and schema changes and updates the connector before they break your pipeline. Continuous monitoring watches every sync, and if anything needs attention you get an alert - so your Metabase data keeps flowing without you touching a thing.
Which Metabase metrics and dimensions are available?
The full Metabase API surface - every metric, dimension, and breakdown, not a fixed subset. If a field you need isn't exposed yet, we add it on request, usually at no extra cost.
How is my data secured?
Dataddo is SOC 2 Type II and ISO 27001 certified. Data is encrypted in transit and at rest, PII can be masked or hashed, and EU or US data residency is available. Self-host the data plane and payload data never leaves your network.
Will API rate limits be a problem?
Dataddo handles Metabase pagination, rate limits, and retries for you, and pulls incrementally on a schedule so you stay within API quotas without impacting your source.
Am I locked in?
No. Pipelines are source- and destination-agnostic - you can add or switch destinations without rebuilding, and data lands in native formats you own.