Skip to main content
Analyses are structured analytical views associated with a pipeline. They appear in the Project Explorer beneath their parent pipeline and are represented with a bar graph icon. An Analysis presents business insights derived from pipeline outputs, including visualizations, recommendations, and supporting data details.

​
Relationship to pipelines

Analyses are generated within the context of a pipeline and depend on that pipeline’s outputs. Pipelines prepare and transform data. Analyses interpret and present insights from those outputs for decision-making. Because Analyses are tied to pipelines:
  • They reflect the logic defined in the underlying transformations.
  • Updates to pipeline logic affect Analysis results.
  • A single pipeline can support multiple Analyses focused on different business questions.

​
What an Analysis includes

An Analysis may include:
  • Key insights summarizing findings.
  • Bar charts and other visualizations.
  • Key recommendations based on results.
  • Supporting metrics and data details.
  • Interactive configuration controls.
These elements are structured and versioned as part of the project. Example of analysis

​
Creating Analyses with the Agent

Analyses are generated by the Agent in response to business questions. When you ask a question, the Agent can:
  • Identify relevant datasets and pipeline outputs.
  • Generate or modify SQL models.
  • Create an Analysis beneath the pipeline.
  • Populate the Analysis with insights, charts, and recommendations.
In some cases, the Agent may suggest creating an Analysis dashboard for the pipeline. All generated assets are saved within the project. You can inspect and refine the SQL logic, adjust visualizations, and modify recommendations as needed.

​
Reuse and refinement

Once created, an Analysis can be reused and refined without rebuilding the underlying pipeline. You can modify an Analysis by:
  • Updating filters or scoring thresholds in the parent pipeline.
  • Adjusting business rules.
  • Editing insight summaries.
  • Adding or removing visualizations.
  • Rearranging the order of sections within the dashboard.
Changes to the Analysis do not require recreating the pipeline. Because the logic and configuration are stored within the project, Analyses can evolve over time while remaining versioned and editable. This allows you to iterate on insights, test different segments or scenarios, and adapt recommendations as business needs change.