> For the complete documentation index, see [llms.txt](https://docs.11x.ai/llms.txt).
> Use it to discover all available pages before exploring further.

# Analytics overview

11x analytics consolidates outreach, qualification, and pipeline data in one place, reporting influenced pipeline and campaign performance rather than activity counts.


11x analytics consolidates **outreach, qualification, and pipeline data in one place** rather than requiring you to stitch it from several tools. The important design choice is what it measures: **pipeline and influence**, not emails sent and replies received. Activity metrics tell you a digital worker is running; pipeline metrics tell you whether it's working.

<Callout kind="tip">
If you report on activity, you'll optimize for activity. The metric that should drive decisions here is influenced pipeline per campaign — everything else is diagnostic.
</Callout>

## What's reported

<Tabs>
  <Tab title="Campaign performance" icon="chart-bar">
    | Metric | Notes |
    | --- | --- |
    | Replies | Diagnostic for messaging quality |
    | Meetings | The nearer-term outcome |
    | Emails and calls | Volume context, not a goal |
    | Connection rates | Call deliverability health |

    Broken down by **segment** and **time period**, with top-campaign comparisons filtered by accounts influenced or pipeline generated.
  </Tab>
  <Tab title="Pipeline attribution" icon="trending-up">
    | Metric | What it tells you |
    | --- | --- |
    | **Influenced pipeline** | Dollar value of opportunities touched by Alice |
    | **Account influence** | Which accounts were actually moved |
    | **Average deal size** | Whether you're reaching the right segment |
    | **90-day pipeline windows** | Campaign analysis over a realistic sales cycle |
  </Tab>
  <Tab title="Website and intent" icon="eye">
    | Metric | What it tells you |
    | --- | --- |
    | Known visitors | Identified individuals and companies |
    | Anonymous visitors | Traffic not yet resolved |
    | Pages browsed | Which content signals intent |

    Intent data feeds directly into outreach workflows rather than sitting in a report. See [website visitor tracking](/data/website-visitor-tracking).
  </Tab>
</Tabs>

## Filtering

Filter by **date**, **campaign**, or **segment** so reporting is scoped to what you actually want to compare.

<Callout kind="alert">
Compare like with like. A revival play against closed-lost accounts and a net-new prospecting play will have very different reply rates and very different pipeline per reply. Filtering by campaign is what stops you drawing the wrong conclusion.
</Callout>

## What to watch, and when

| Phase | Watch | Because |
| --- | --- | --- |
| **First week** | Deliverability, reply quality, qualification accuracy | Cheap to fix before volume builds |
| **First month** | Meetings, rep feedback on quality | Tells you whether thresholds are right |
| **Quarter one** | Influenced pipeline, average deal size | The first read on whether the motion works |
| **Ongoing** | Pipeline per campaign, mailbox and number health | Comparing motions; catching degradation early |

<Callout kind="tip">
Review **daily** for the first week, not weekly. Early signal tells you whether the ICP is too broad or the messaging is off, and both are far cheaper to fix at low volume.
</Callout>

## Judging a campaign

<Steps>
  <Step title="Start from influenced pipeline" icon="trending-up">
    Not reply rate. A campaign with a lower reply rate and higher pipeline per reply is the better campaign.
  </Step>
  <Step title="Check average deal size" icon="dollar-sign">
    If it's below expectation, the ICP is reaching too far down-market.
  </Step>
  <Step title="Use the 90-day window" icon="calendar">
    Judging outbound on a two-week window measures noise, not performance.
  </Step>
  <Step title="Cross-check with rep feedback" icon="message-square">
    Reps disputing meeting quality is the earliest signal that qualification needs tuning.
  </Step>
  <Step title="Then look at diagnostics" icon="stethoscope">
    Reply rate, connect rate, and placement explain *why* — after you know *whether*.
  </Step>
</Steps>

## Reported outcomes

Customers report **35% of pipeline generated by 11x within the first 3 months** and **$1M+ pipeline generated in the first 3 months**.

<Callout kind="info">
Individual customer-reported results published by 11x, not guarantees. See [case studies](https://www.11x.ai/customers).
</Callout>

## Known gaps

<Callout kind="info">
11x does not publish specifics on **export formats** or its **ROI calculation methodology**. If you need to pull data into a warehouse or BI tool, the [API](/integrations/webhooks) is the route — contact support for the current endpoint reference, which isn't published yet either.
</Callout>

## Frequently Asked Questions

<Expandable title="Why does influenced pipeline look lower than expected?">
Check CRM write-back. If interactions aren't landing on the right objects, attribution can't see them. See [integrations](/integrations).
</Expandable>

<Expandable title="Why do two identical-looking campaigns perform very differently?">
Filter by segment as well as campaign. The difference is usually who was targeted, not what was said.
</Expandable>

<Expandable title="Why is reply rate good but pipeline flat?">
Targeting is reaching people who will reply but won't buy. Tighten the ICP rather than changing messaging.
</Expandable>

<Expandable title="Why do 11x numbers not match our CRM reporting?">
Check the attribution window and whether your CRM report counts created versus influenced opportunities. These measure different things.
</Expandable>

## Next steps

<Columns cols={2}>
  <Card title="Mailbox health" icon="mail" href="/analytics/mailbox-health" horizontal>
    Email deliverability monitoring.
  </Card>
  <Card title="Connection boosts" icon="signal" href="/julian/connection-boosts" horizontal>
    Call deliverability and number health.
  </Card>
  <Card title="How 11x saves time and money" icon="calculator" href="/help-center/overview/how-11x-saves-time-and-money" horizontal>
    Building the business case from these numbers.
  </Card>
  <Card title="Webhooks and API" icon="webhook" href="/integrations/webhooks" horizontal>
    Pulling data into a warehouse.
  </Card>
</Columns>
