> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flow-board.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Analyse

> Monitor flow performance, conversion, and drop-off over time.

Pulse is the analytics area of Flowboard. It helps you understand how your onboarding is performing after it goes live.

## What Pulse is made for

Use Pulse when you want to:

* See how many users launch a flow
* Measure completion and drop-off
* Compare performance across flows
* Review trends by date range or platform

## How Pulse works

Pulse aggregates flow activity for your app and presents it in a format that is easy to monitor. Instead of inspecting each flow manually, you can see the overall picture and then drill into the flows that need attention.

## What you can review in Pulse

<AccordionGroup>
  <Accordion title="Global metrics">
    Review launch rate, completion rate, drop rate, and average completion time across your app.
  </Accordion>

  <Accordion title="Date range filters">
    Narrow the data to the period you want to analyze, such as the last 7, 30, or custom date range.
  </Accordion>

  <Accordion title="Platform filters">
    Compare performance on iOS and Android when behavior differs by platform.
  </Accordion>

  <Accordion title="Flow-level performance">
    See which flows are being detected and how each one performs during the selected period.
  </Accordion>
</AccordionGroup>

## How to use Pulse well

<Steps>
  <Step title="Start broad">
    Check the app-level metrics first to see whether onboarding health is improving or declining.
  </Step>

  <Step title="Spot the outliers">
    Identify flows with unusually low completion or high drop-off.
  </Step>

  <Step title="Connect insight to action">
    Use what you find to update the flow, adjust the audience, or launch an experiment in Labs.
  </Step>

  <Step title="Measure again after changes">
    Compare the next period against the previous one so you know whether the update helped.
  </Step>
</Steps>

## Best practices

* Review Pulse on a regular schedule, not only after a problem appears.
* Compare similar periods when judging performance.
* Watch both completion rate and time to completion, not just one metric.
* Investigate a sudden drop before making major design changes.
* Use Pulse together with Labs to validate whether an experiment actually improved outcomes.

## Related guides

* [Understand flows](/features/flows-overview)
* [Target by segment with audiences](/features/audiences)
* [Run tests in Labs](/features/labs)