BigQuery
Export semantic datasets and replicated source tables into Google BigQuery with backend-owned table and schema planning.
Browse every registered connector, then open a connector to inspect its available datasets, report schemas, provider fields, Meridian mappings, and data types.
Send governed Meridian datasets into warehouses, lakehouses, object storage, spreadsheets, BI tools, and built-in Meridian analysis surfaces.
Export semantic datasets and replicated source tables into Google BigQuery with backend-owned table and schema planning.
Load governed exports into Snowflake databases and schemas using key-pair credentials and validated write modes.
Send period-safe semantic exports to Redshift tables through staged Parquet loading and customer IAM role access.
Stage semantic exports into Databricks SQL and Delta workflows with service-principal authentication.
Export modeled datasets into OneLake and Fabric Lakehouse tables through service-principal credentials.
Replace selected spreadsheet ranges with semantic exports for recurring team reporting and lightweight analysis.
Use spreadsheet-ready exported datasets in Excel workflows when teams need offline review or workbook handoff.
Expose saved Meridian semantic exports to Looker Studio through the Meridian connector surface.
Push backend-compiled semantic exports into Power BI datasets with service-principal authentication.
Write JSON Lines exports to customer-owned S3 prefixes using cross-account IAM role access.
Deliver JSON Lines exports to GCS buckets with destination credentials stored outside export configs.
Export JSON Lines datasets to Azure Blob Storage or ADLS Gen2 with Entra ID service-principal auth.
Use built-in dashboards powered by the same governed semantic layer used by exports.
Inspect fields, validate data, and explore modeled datasets inside Meridian before sending them downstream.
Meridian automatically puts each supported report into the correct semantic table, maps platform fields into shared business definitions, and keeps every query tied to the right account, source, date, currency, and grain. Your team gets trusted reporting data without rebuilding the same warehouse model from scratch.
Connectors bring in provider data and preserve source context, including account scope, source lineage, dates, currency, and provider-native detail for audit and advanced use.
Meridian writes each report to the table that matches its business domain and grain, then maps native provider fields into canonical dimensions and metrics.
Dashboards, Explore, and exports use the same semantic rules, so users select fields instead of writing SQL joins or guessing which metrics can be added together.
The semantic layer turns raw platform data into a governed product surface. It gives marketers useful fields, gives analysts consistency, and gives technical teams a model they can trust in downstream tools.
Meridian connects marketing, CRM, payment, and ecommerce data, stores it, maps it into common business fields, and sends it where your team works. No-code for marketers. Programmable workflows for technical teams.
Pay monthly for what you use: 4 data sources + Google Sheets export one month, 100 sources + BigQuery the next. For commerce teams, the modeled layer separates customer-paid shipping revenue, merchant shipping costs, gateway fees, and retroactive return adjustments so profit reporting does not collapse into generic dashboard math.
Meridian stores your source data, shapes it into shared business definitions, and keeps it ready for dashboards, exports, and automation. Commerce models preserve the difference between what customers paid for shipping, what the merchant paid to fulfill it, transaction fees, and late return adjustments.
Bring in marketing, CRM, payment, ecommerce, and analytics data. Keep source data stored so reporting is fast and repeatable.
Map platform-specific fields into common business fields. Create custom dimensions and metrics for your own reporting logic.
Explore data in Meridian, export it to your tools, and automate supported workflows through API and MCP.
Meridian keeps source detail available while giving your team common fields for reporting. Build shared definitions once, then use them in dashboards, exports, and automated workflows.
| Source | Native field | Value |
|---|---|---|
| Meta Ads | spend | 420.13 |
| Google Ads | cost_micros | 391200000 |
| LinkedIn Ads | amountSpent | 82.44 |
| Common field | Value |
|---|---|
| cost | 893.77 |
| shipping_amount | 12.00 |
| shipping_cost_amount | 10.00 |
| payment_fee_amount | 11.00 |
| refund_amount | 50.00 |
| return_cost_amount | 4.00 |
| currency | USD |
| date | 2026-05-01 |
| channel | Paid social / Paid search |
The same data model powers the UI, exports, and programmable workflows, so marketers and technical teams can work from one shared foundation.
Use Dashboards and Data Explorer, export to spreadsheets and BI tools, and sync clean datasets to your warehouse destinations.
Your bill changes when you connect more data or add exports, not when someone needs another seat or a team wants to use a product feature.
Connect a source, normalize the fields that matter, and send business-ready data to the tools your team already uses.