Warehouse Native Experimentation
Make confident product decisions by running experiments directly in your data warehouse, using metrics and SQL you fully control.
Run experiments faster. Use your data warehouse to run experiments on governed data without waiting for ETL or extra configuration.
Protect sensitive data. Keep PII and behavioral data inside your governed environment. Full compliance without shipping data to a third party.
Own your metrics. Build metrics from existing tables and views using your own SQL and transformation logic. No vendor templates, no lock-in.
Native integrations with leading data warehouses.
Run queries directly in Snowflake with full schema visibility
Native Redshift integration for governed experimentation
Query BigQuery tables without data movement
Metric sources come from your data warehouse. Write metric SQL against your own schemas. Reuse the same query logic your data team already trusts for internal reporting.
Reuse metrics across experiments. Define a metric once and apply it to every relevant experiment without duplicating logic or risking inconsistent definitions.
Include guardrail metrics. Track latency, error rate, revenue, and stability alongside your primary metrics so you catch regressions before they ship.
Refresh on a schedule or on demand. Results update daily automatically or instantly when you need them, with no manual query runs.
Track statistical significance automatically. Confidence levels surface as data accumulates so you know exactly when a result is ready to act on.
Inspect the SQL behind any result. Every result links back to the underlying query. Full transparency, no black boxes, full auditability.
checkout_cta_v2 · Day 12 of 14
Connect your warehouse once and you are ready to run experiments. No pipelines to build, no data to move, no extra infrastructure to maintain.
Grant read access to behavioral event and assignment tables, plus the ability to write results to a dedicated Harness schema and run scheduled query jobs.
Metric source tables contain event-level data used in metric definitions for consistent, verifiable representation of user behavior.
Define assignment sources to model how exposure is stored and mapped, and metric sources to represent event schemas and context.
Add key metrics and guardrails, then run experiments, monitor results, and collect validated insights.
increase in release velocity
risk-controlled deployments per month
“Split provides so much more than just a tool set ... It's transformative in terms of the teams, in terms of the culture that we adopt.”
— Mirza Baig, Senior VP of Engineering, Experian
Warehouse-Native Experimentation is an extension of Harness Feature Management & Experimentation that runs experiments directly in your data warehouse. It reads from assignment and metric source tables, writes results into a Harness schema, and uses SQL you can inspect so analysis is transparent and auditable.
Traditional experimentation tools often require copying data into separate systems and rely on black-box calculations. Warehouse-Native Experimentation keeps data in place, uses your existing schemas and governance, and lets you review and customize SQL, so you maintain end-to-end visibility and control.
No. Warehouse-Native Experimentation does not require streaming or ingestion pipelines. Harness FME reads directly from your warehouse tables, which reduces operational overhead and avoids additional infrastructure.
Warehouse-Native Experimentation supports Snowflake and Amazon Redshift, with additional platforms planned. For the latest list of supported warehouses, refer to the product documentation.
Your teams define metrics using warehouse data that already follows internal governance rules. Product, experimentation, and data teams can collaborate on shared metric definitions, ensuring that all experiment results map to trusted business KPIs.
Keep data secure, eliminate ETL bottlenecks, and use the metrics that matter to your business.