For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Sign inTry it free
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
  • Get started
    • Overview
    • Onboarding
    • Get started
    • Launch Insights
    • LaunchDarkly architecture
    • LaunchDarkly vocabulary
  • AgentControl
    • AgentControl
    • Manage AgentControl
  • Feature flags
    • Create flags
    • Target with flags
    • Flag templates
    • Manage flags
    • Code references
    • Contexts
    • Segments
  • Releases
    • Releasing features with LaunchDarkly
    • Release policies
    • Percentage rollouts
    • Progressive rollouts
    • Guarded rollouts
    • Feature monitoring
    • Release pipelines
    • Engineering insights
    • Release management tools
    • Applications and app versions
    • Change history
    • Restoring previous flag versions
  • Observability
    • Observability
    • Session replay
    • Error monitoring
    • Logs
    • Traces
    • Observability metrics
    • Product analytics events
    • LLM observability
    • Alerts
    • Dashboards
    • Service map
    • Vega for auto-remediation
    • Observability MCP server
    • Search specification
    • Observability settings
    • Observability integrations
  • Experimentation
    • Experimentation
    • Experiment metric types
    • Experiment configuration
    • Managing experiments
    • Analyzing experiments
    • Multi-armed bandits
    • Holdouts
  • Metrics and events
    • Metrics in LaunchDarkly
    • Creating metrics
    • Metric groups
    • Events
    • Autogenerated metrics
  • Warehouse native
    • Warehouse native metrics
    • Setting up external warehouses
      • BigQuery native Experimentation
      • Databricks native Experimentation
      • Redshift native Experimentation
      • Snowflake native Experimentation
        • Data requirements
        • Setting up the Snowflake integration
        • Snowflake common questions
      • Warehouse health checks
    • Creating experiments using warehouse native metrics
  • Infrastructure
    • Connect apps and services to LaunchDarkly
    • LaunchDarkly in China and Pakistan
    • LaunchDarkly in the European Union (EU)
    • LaunchDarkly in federal environments
    • Public IP list
  • Your account
    • Projects
    • Views
    • Environments
    • Tags
    • Teams
    • Members
    • Roles
    • Account security
    • Feature previews
    • Billing and usage
    • Changelog
Sign inTry it free
LogoLogo
On this page
  • Assignment data
  • Metric events data
Warehouse nativeSetting up external warehousesSnowflake native Experimentation

Snowflake data requirements

Was this page helpful?
Previous

Setting up the Snowflake integration

Next
Built with

This topic explains the data requirements for Snowflake native Experimentation.

To use Snowflake native Experimentation, two types of data sources are required: assignment data and metric events data. These two datasets are required for computing metrics and analyzing experiment results. LaunchDarkly handles generating and exporting experiment assignment data, and you are responsible for ensuring that metric event data is prepared, stored, formatted, and refreshed appropriately in your Snowflake warehouse.

Assignment data

Assignment data is a timestamped dataset that tracks which context, such as a user or account, was exposed to which experiment variation and when. Each row represents a unique assignment event, tracking the experiment exposure for each context. This data is automatically generated by LaunchDarkly when you run an experiment and is exported to Snowflake using the Snowflake Data Export integration. To prepare and use the assignment data dataset, configure the Snowflake Data Export integration.

Snowflake native Experimentation works only with LaunchDarkly experiment data

You cannot run Snowflake native experiments on experiment data coming from third-party sources, or flag evaluation data from LaunchDarkly that was not generated as part of a LaunchDarkly experiment.

Metric events data

To learn how to set up your metric events data, read Metric data sources.