# Review experimentation activity in Analytics

Use signals, execution balance, and detailed operational metrics.

Open **Analytics** to understand the flow of research and experimentation work. It summarizes the records and lifecycle activity tracked in ConversionLab.

## Start with Signals

The **Signals** tab highlights work such as insights and ideas created, experiments created, started and finished, and the average time from idea to experiment. Review comparisons with the prior period alongside the current totals.

**Weekly execution balance** compares experiments started and finished. It helps identify weeks when work entering the process exceeds work completed. These counts describe program activity; they are separate from an experiment's conversion rate or business impact.

## Inspect Details

Open **Details** to review operational metrics and the daily, weekly, or monthly tables. Use the rows to check which time periods explain a headline change. Missing values are shown as unavailable rather than always as zero; a prior period with no baseline may not have a meaningful percentage comparison.

## Improve the underlying records

Analytics relies on recorded work and lifecycle events. Keep experiment dates and states accurate, and connect ideas to the experiments that follow them. If totals seem unexpected, compare the relevant lists and dates before concluding that activity has been lost.

For conversion analysis of a particular test, open its [Results](https://conversionlab.app/docs/experiments/results) page. For upcoming work, use the [Roadmap](https://conversionlab.app/docs/experiments/roadmap).