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

# Trial success guide

> Run a Leadpipe trial in a way that proves real value quickly

## What a good trial should answer

A good trial should not just prove that Leadpipe can collect data. It should prove that your team can turn that data into something commercially useful.

By the end of a trial, you should be able to answer:

* did the data fit our traffic?
* did we find enough useful visitors?
* did we route them somewhere useful?
* did the workflow create meetings, replies, audiences, or another real outcome?

## The best trial shape

<Steps>
  <Step title="Track one clean domain or use case">
    Start narrow so the data is easier to judge.
  </Step>

  <Step title="Suppress obvious noise early">
    Do not let bad-fit traffic distort the trial.
  </Step>

  <Step title="Define one ideal customer profile">
    Be specific about who should count as a good result.
  </Step>

  <Step title="Choose one output">
    Pick one workflow such as CRM routing, Slack alerts, lifecycle email, or export review.
  </Step>

  <Step title="Review outcomes, not just volume">
    The right question is not just how many visitors were identified. It is whether the identified visitors were useful.
  </Step>
</Steps>

## What to measure

| Measure                       | Why it matters                                        |
| ----------------------------- | ----------------------------------------------------- |
| Verified pixel and data flow  | Confirms the setup is real                            |
| Volume of identified visitors | Shows whether the traffic is large enough to evaluate |
| Fit of identified visitors    | Shows whether the product matches your market         |
| Actionability of records      | Shows whether the data is usable in your workflow     |
| Downstream result             | Shows whether the workflow creates business value     |

## Common reasons trials fail

<AccordionGroup>
  <Accordion title="The traffic was too broad">
    Trials are harder to judge when the traffic mix is noisy and unfiltered.
  </Accordion>

  <Accordion title="Nobody owned the next step">
    A trial without a downstream owner often creates interest but not proof.
  </Accordion>

  <Accordion title="The workflow was too ambitious">
    Start with one clear path, not five integrations and three segments at once.
  </Accordion>

  <Accordion title="The team only measured volume">
    A smaller set of usable records can be more valuable than a larger noisy feed.
  </Accordion>
</AccordionGroup>

## A clean trial outcome

At the end of the trial, you should be able to say one of three things clearly:

* this is a fit and we know how we will use it
* this is a fit, but we need a tighter workflow
* this is not a fit for our traffic or operating model