# Website analytics

> Visits, identified leads, ICP match rate and who your visitors are, per website.

Every section below does the same job: in the dashboard (Guide), from your code (API) or through an AI assistant (MCP).

## Guide — In the dashboard

Source: /docs/websites/analytics

The dashboard shows how a website is doing: identified leads, how many fit your ideal customer, and who they are.

<DemoFrame guide="dashboard-overview" to="/homepage/{workspace}" />

1. **Dashboard:** plan, pixel status, leads this cycle.
2. **Identifications** and **ICP match rate** over 30 days.
3. **Who they are:** industries, company sizes, job titles.

### Every control on this screen [#every-control-on-this-screen]

Every button, field and switch, with what it does.

<ScreenControls screens={["dashboard"]} />


---

## API — From your code

Source: /docs/websites/analytics/api

Authenticated with `?privateKey=YOUR_KEY` (see [Authentication](/docs/authentication)).

<Endpoints ops={["GET /admin/website/analytics", "GET /admin/website/daily-stats", "GET /v3/websites/{websiteId}/diagnostics"]} />

<ApiPlayground
  ops={["GET /admin/website/analytics", "GET /admin/website/daily-stats", "GET /v3/websites/{websiteId}/diagnostics"]}
  method="get"
  path="/admin/website/analytics"
  tool="get_website_analytics"
  args={`{
  "websiteId": "64b7f0a1c2d3e4f5a6b7c8d9"
}`}
/>

### Use case: A weekly report [#use-case-a-weekly-report]

`GET /admin/website/daily-stats?websiteId=…` returns the last 30 days, day by day.


---

## MCP — AI agents

Source: /docs/websites/analytics/mcp

Connect the [MCP server](/docs/mcp#quickstart), then just ask.

<Tools names={["get_website_analytics", "get_website_daily_stats", "get_website_diagnostics"]} />

### Use case [#use-case]

> How many leads did acme.example get this month?

<McpToolCall name="get_website_analytics">

```json
{
  "websiteId": "64b7f0a1c2d3e4f5a6b7c8d9"
}
```

</McpToolCall>