Clics

Clics

Clics is privacy-friendly, cookieless web analytics. Agents manage projects, goals, funnels, sessions, AI crawlers, and analytics stats in two ways:

• MCP tools (clics server via @clicsdev/mcp) — preferred for agents.
• CLI (@clicsdev/cli, binary clics) — fallback when MCP is unavailable, for manual verification, or for scripts and CI.

Choosing MCP vs CLI

Prefer MCP tools whenever the clics MCP server is connected — no shell is required, and the API key is supplied by the MCP client environment.

Use the CLI when:

• The MCP server is not connected in this session.
• You need to verify behavior manually or from a script or terminal.
• You are automating in CI where stdio MCP is not available.

Authentication

MCP — set in the MCP client config (never pass the API key as a tool argument):

CLICS_API_KEY=your_api_key

Typical Cursor setup: npx -y @clicsdev/mcp with that environment variable.

CLI — one-time local configuration (stored in ~/.config/clics/):

npm install -g @clicsdev/cli
# or: npx @clicsdev/cli …
clics init --api-key "<your-api-key>"

Re-run clics init to rotate the key. Clear stored credentials with clics logout. Successful CLI commands print a single JSON document on stdout; errors are written to stderr with a non-zero exit code.

clics logout

MCP tools (preferred)

Server name: clics. Call tools directly; full input schemas are defined on each tool. Confirm the connected server's tool list before calling it. The local @clicsdev/mcp server exposes the complete set below; if a connected MCP server does not offer a read operation, use the CLI rather than inventing a direct request.

Projects

Empty workspace setup

If list_projects returns no projects, do not continue with stats, sessions, goals, funnels, or AI crawler analytics. Ask the user for:

• project name
• production website domain
• whether localhost tracking should be allowed for development

Then create the project with create_project or:

clics projects create --name "<project-name>" --website-url "<domain>"

If the user wants localhost tracking, add --allow-localhost.

After the project is created, help the user set up browser tracking. Read https://docs.clics.dev/installation-guides, choose the section that matches the user's framework, and give them the browser tracking snippet with the returned project_id already filled in:

<script
  defer
  data-project-id="<project_id>"
  src="https://clics.dev/tracker.js"
></script>

For Next.js, use the same project_id in next/script:

<Script
  strategy="afterInteractive"
  src="https://clics.dev/tracker.js"
  data-project-id="<project_id>"
/>

Ask where the code should be installed when the framework or entry file is not clear. Help the user place the snippet in the correct file, then tell them how to verify the first pageview in the dashboard.

For AI crawler tracking, do not invent a crawler snippet. It uses a separate server-side setup. Read https://docs.clics.dev/installation-guides/ai-crawler-tracking, identify the right section for the user's runtime, then help them add the server-side tracking code and required project-scoped crawler token.

Goals

env_id: production | development (default production).

Use the rule that matches goal_type:

Use an exact HTTP(S) URL for an outbound goal. Use a whole scroll-depth percentage from 1 to 100. When changing a goal's type, send the complete rule for the new type. get_goal_stats returns dashboard-ready totals, comparison, series, and meta.timezone for every goal type.

Funnels

Sessions

Period presets match query_stats (last24h, last7days, …, allTime). For a custom range, pass both start and end. Pass an IANA timezone when calendar boundaries must use a local timezone; UTC is the default. Use optional domain to scope a site.

AI crawlers

AI crawler analytics always query production. Period presets match query_stats; for a custom range, pass both start and end.

category is answer_fetch, search_index, or training. provider and crawler are enum values from the supported crawler registry and can be passed as one value or a list. status is still a status-code string such as 200 or 404; 0 means unknown. Filter operators are is or is_not.

Providers: OpenAI, Anthropic, Perplexity, Google, Microsoft, Mistral, Amazon, DuckDuckGo, Apple, Moonshot AI, Common Crawl.

Crawlers: ChatGPT-User, OAI-SearchBot, GPTBot, Claude-User, Claude-SearchBot, ClaudeBot, Perplexity-User, PerplexityBot, Google-Agent, Google-GeminiNotebook, Google-NotebookLM, Google-Read-Aloud, Google-InspectionTool, Googlebot, GoogleOther, Google-CloudVertexBot, Bingbot, msnbot, MistralAI-User, MistralAI-Index, Amzn-User, Amzn-SearchBot, Amazonbot, DuckAssistBot, Applebot, Kimi-User, Kimi-SearchBot, KimiBot, CCBot.

Stats

{
  "project_id": "your_project_id",
  "metrics": ["visitors", "pageviews", "bounce_rate"],
  "date_range": "last30days",
  "timezone": "UTC",
  "include": { "previous_period": true }
}

For query_stats, use one time dimension (time, time:hour, or time:day) or up to two breakdown dimensions. event:name, event:outbound_url, and referrer:ai_provider support event and AI analytics. Filters additionally support event:goal. For a custom stats range, set date_range to a two-item ISO date pair.

Responses return JSON text in content and the same object in structuredContent. Failures set isError: true.

CLI reference (fallback)

Package: @clicsdev/cli. Binary: clics. Help: clics --help, clics --version, clics help <command>.

Run without a global install: npx @clicsdev/cli <command> ….

Projects

List

clics projects list
clics projects list --limit 20
clics projects list --cursor "<cursor>"

Get

clics projects get <project-id>

Create

clics projects create --name "My site" --website-url https://example.com
clics projects create --name "My site" --website-url https://example.com --allow-localhost

Update

clics projects update <project-id> --name "New name"
clics projects update <project-id> --website-url https://new.example.com
clics projects update <project-id> --allow-localhost

Delete

clics projects delete <project-id>

Goals

env_id is production or development (API default: production).

List

clics goals list <project-id>
clics goals list <project-id> --env-id development

Create — page goal:

clics goals create <project-id> --goal-type page --display-name "Signup page" --page-path /signup

Create — event goal:

clics goals create <project-id> --goal-type event --display-name "Purchase" --event-name purchase

Create — outbound-link and scroll-depth goals:

clics goals create <project-id> --goal-type outbound --display-name "Documentation" --outbound-url https://example.com/docs
clics goals create <project-id> --goal-type scroll_depth --display-name "Article 75%" --page-path /article --scroll-depth-threshold 75

Goal rules are type-specific: page requires --page-path; event requires --event-name; outbound requires an exact --outbound-url; and scroll_depth requires both --page-path and a whole --scroll-depth-threshold from 1 to 100.

Statistics

clics goals stats <goal-id> --date-range last30days --timezone UTC
clics goals stats <goal-id> --start 2026-07-01 --end 2026-07-31 --timezone Europe/London
clics goals stats <goal-id> --domain app.example.com --ai-provider chatgpt

--ai-provider accepts chatgpt, claude, gemini, perplexity, or copilot.

Optional environment:

clics goals create <project-id> --goal-type page --display-name "Home" --page-path / --env-id development

Update

clics goals update <goal-id> --goal-type page --display-name "Signup" --page-path /signup
clics goals update <goal-id> --goal-type event --display-name "Purchase" --event-name purchase
clics goals update <goal-id> --goal-type outbound --display-name "Partner signup" --outbound-url https://partner.example.com/signup
clics goals update <goal-id> --goal-type scroll_depth --display-name "Read 75%" --page-path /pricing --scroll-depth-threshold 75

Delete

clics goals delete <goal-id>

Funnels

List, get, and delete use flags. Create and update take JSON via --body (inline or @file.json).

List

clics funnels list <project-id>
clics funnels list <project-id> --env-id production --limit 20
clics funnels list <project-id> --cursor "<cursor>"

Get

clics funnels get <funnel-id>

Statistics

clics funnels stats <funnel-id> --date-range last30days --timezone UTC
clics funnels stats <funnel-id> --start 2026-07-01 --end 2026-07-31 --timezone Europe/London
clics funnels stats <funnel-id> --domain app.example.com --ai-provider chatgpt

--ai-provider accepts chatgpt, claude, gemini, perplexity, or copilot.

Create

clics funnels create <project-id> --body @funnel.json

Example funnel.json:

{
  "name": "Signup funnel",
  "conversion_window": { "value": 7, "unit": "days" },
  "steps": [
    {
      "name": "Landing",
      "filters": [{ "filter_type": "page", "operator": "is", "values": ["/"] }]
    },
    {
      "name": "Signup",
      "filters": [{ "filter_type": "page", "operator": "is", "values": ["/signup"] }]
    }
  ]
}

Optional env_id in the body: production | development.

Update (same shape as create, without env_id):

clics funnels update <funnel-id> --body @funnel-update.json

Delete

clics funnels delete <funnel-id>

Sessions

List

clics sessions filter-values <project-id> --field country --date-range last30days
clics sessions filter-values <project-id> --field referrer --domain app.example.com --timezone Europe/London --limit 100
clics sessions list <project-id>
clics sessions list <project-id> --date-range last7days --limit 20
clics sessions list <project-id> --domain example.com --date-range last30days
clics sessions list <project-id> --start 2026-07-01 --end 2026-07-15
clics sessions list <project-id> --date-range last30days --timezone Europe/London
clics sessions list <project-id> --cursor "<cursor>"

The available session-filter fields are country, device, browser, os, page_entry, page_exit, and referrer.

Get

clics sessions get <project-id> <session-id>
clics sessions get <project-id> <session-id> --date-range last30days
clics sessions get <project-id> <session-id> --timezone Europe/London

Events

clics sessions events <project-id> <session-id>
clics sessions events <project-id> <session-id> --domain localhost
clics sessions events <project-id> <session-id> --timezone Europe/London

AI crawlers

clics ai-crawlers <project-id>
clics ai-crawlers <project-id> --date-range last30days --timezone Europe/London
clics ai-crawlers <project-id> --category training --provider OpenAI --provider-op is_not

Query analytics

--metrics and --date-range are required (unless using --file).

Presets

clics query <project-id> --metrics visitors --date-range last24h
clics query <project-id> --metrics visitors --date-range last7days
clics query <project-id> --metrics visitors --date-range last30days
clics query <project-id> --metrics visitors --date-range last3months
clics query <project-id> --metrics visitors --date-range last12months
clics query <project-id> --metrics visitors --date-range monthToDate
clics query <project-id> --metrics visitors --date-range quarterToDate
clics query <project-id> --metrics visitors --date-range yearToDate
clics query <project-id> --metrics visitors --date-range allTime

Basic KPIs

clics query <project-id> --metrics visitors pageviews bounce_rate --date-range last30days
clics query <project-id> --metrics visitors pageviews --date-range last30days --timezone Europe/London

Comparison / totals

clics query <project-id> --metrics visitors pageviews bounce_rate --date-range last30days --previous-period --total-rows

Domain filter

clics query <project-id> --metrics visitors --date-range last7days --domain example.com

Use --domain localhost for development traffic only.

Breakdown

clics query <project-id> --metrics visitors pageviews --date-range last30days --dimensions visit:country

Events and AI analytics

clics query <project-id> --metrics visitors events conversion_rate --date-range last30days --dimensions event:name
clics query <project-id> --metrics visitors events conversion_rate --date-range last30days --dimensions event:outbound_url
clics query <project-id> --metrics visitors pageviews --date-range last30days --dimensions referrer:ai_provider

Pagination

clics query <project-id> --metrics visitors --date-range last30days --dimensions visit:country --limit 50 --offset 0

Advanced file (filters, order_by, custom date ranges):

clics query <project-id> --file query.json

Example query.json:

{
  "metrics": ["visitors", "pageviews", "bounce_rate"],
  "date_range": "last30days",
  "timezone": "Europe/London",
  "dimensions": ["visit:country"],
  "filters": [["is", "visit:country", ["US", "FR"]]],
  "order_by": [["visitors", "desc"]],
  "include": {
    "previous_period": true,
    "total_rows": true
  },
  "pagination": {
    "limit": 50,
    "offset": 0
  }
}

project_id in the file is overwritten by the CLI argument.

Allowed metrics: visitors · visits · pageviews · bounce_rate · visit_duration · views_per_visit · conversion_rate · events

• KPI / time-series: visitors, visits, pageviews, bounce_rate, visit_duration, views_per_visit
• Breakdown: visitors, pageviews, conversion_rate, events

Allowed date ranges: last24h · last7days · last30days · last3months · last12months · monthToDate · quarterToDate · yearToDate · allTime (custom ISO pairs via --file)

Allowed dimensions: event:page · event:hostname · event:name · event:outbound_url · visit:country · visit:device · visit:browser · visit:os · visit:referrer · referrer:ai_provider · visit:utm_source · visit:utm_medium · visit:utm_campaign · visit:utm_term · visit:utm_content · time · time:hour · time:day

Additional filter-only dimension: event:goal.

Scripting

clics projects list | jq '.projects[].id'

Prefer --body @file.json / --file file.json over inline JSON (especially on PowerShell).

Playbooks

1. Overview (last 30 days)

1. Run list_projects or clics projects list and pick a project_id.
2. Run query_stats or clics query <id> --metrics visitors visits pageviews bounce_rate visit_duration views_per_visit --date-range last30days --previous-period.
3. Summarize KPIs and period-over-period changes from the JSON response.

2. Top pages and countries

1. Resolve project_id as above.
2. Pages: query_stats with metrics: ["visitors","pageviews"], date_range: "last30days", dimensions: ["event:page"], order_by: [["visitors","desc"]], pagination: { "limit": 10 }.
   CLI: clics query <id> --metrics visitors pageviews --date-range last30days --dimensions event:page --limit 10
3. Countries: same query with dimensions: ["visit:country"].
   CLI: clics query <id> --metrics visitors pageviews --date-range last30days --dimensions visit:country --limit 10

3. Goals and funnels check

1. Run list_goals or clics goals list <project-id> (add --env-id development if needed), then inspect one with get_goal / clics goals get <goal-id> when its exact rule matters.
2. Run list_funnels or clics funnels list <project-id>.
3. Optionally run get_funnel or clics funnels get <funnel-id> for step details.
4. Run get_goal_stats / clics goals stats <goal-id> or get_funnel_stats / clics funnels stats <funnel-id> when the user asks for performance, rather than attempting to reconstruct it from raw rows.
5. Report what is configured. Do not create or delete resources unless the user asked.

4. Inspect recent sessions

1. Resolve project_id as above.
2. Use list_session_filter_values / clics sessions filter-values <project-id> --field <field> first when you need to discover valid session-filter values.
3. Run list_sessions or clics sessions list <project-id> --date-range last7days --limit 20.
4. Pick a session_id, then get_session / clics sessions get <project-id> <session-id> and list_session_events / clics sessions events <project-id> <session-id>.
5. Summarize landing/exit, bounce, duration, and notable events. Do not invent session IDs.

5. Inspect AI crawler activity

1. Resolve project_id as above.
2. Run get_ai_crawler_analytics or clics ai-crawlers <project-id> --date-range last30days.
3. Use dashboard-style filters (category, provider, crawler, status) only when the user asks for a narrower view.
4. Summarize verified crawler activity from categories, timeseries, and breakdowns; mention meta.environment is production.

Manual verification

Confirm authentication and API access with the CLI so JSON is visible in the terminal:

clics projects list
clics query <project-id> --metrics visitors --date-range last7days
clics sessions list <project-id> --date-range last7days --limit 5
clics ai-crawlers <project-id> --date-range last7days

Expect a JSON projects payload, a stats results array, and a sessions list. Common errors:

• API key is required. Run clics init. — run clics init --api-key "…"
• 401 / invalid key — rotate or recreate the key, then run clics init again
• 403 / UPGRADE_REQUIRED — a paid plan is required for API access

Links

• Product: https://clics.dev
• Dashboard: https://platform.clics.dev
• Docs: https://docs.clics.dev
• MCP: @clicsdev/mcp
• CLI: @clicsdev/cli