CLI Tracking

Track how developers use your CLI tool. See which commands are popular, how long they take, and what errors occur -- without collecting PII.

npm install @bettermeter/node

import { BetterMeter } from "@bettermeter/node";
import { Command } from "commander";

const bm = new BetterMeter({
  siteId: "my-cli-tool",
  apiKey: "bm_...",
});

const program = new Command();

// Wraps all commands — tracks name, flags, exit code
bm.wrapCommander(program, { version: "1.0.0" });

program.command("deploy").action(() => { /* ... */ });
program.parse();

// Flush on exit
process.on("SIGTERM", () => bm.shutdown());

bm.trackCommand({
  command: "deploy",
  subcommand: "preview",
  flags: ["--prod", "--verbose"],
  version: "2.1.0",
  durationMs: 4500,
  exitCode: 0,
  isCi: !!process.env.CI,
});

What gets tracked

Command names and flag names only. Flag values, arguments, and file paths are never sent. The SDK captures OS and architecture for environment analytics.

CLI Reference

The BetterMeter CLI lets you query analytics from the terminal with beautiful visual output. All commands accept -r/--range and --json, and every one but all-sites also accepts -s/--site — that one is account-wide and takes no site. -l/--limit applies only to the commands that return a ranked list.

npm install -g bettermeter
bettermeter login -t <apiKey> -u https://bettermeter.com

Output Formats

By default, the CLI renders rich visual output with ASCII art charts, colored text, sparklines, and box-drawn stat cards. All output uses Unicode characters compatible with every modern terminal. Colors auto-detect terminal capabilities and respect the NO_COLOR environment variable.

Visual output includes:

• Line charts for timeseries data (daily visitors, invocations)
• Horizontal bar charts for ranked lists (pages, sources, countries)
• Sparklines inline with overview stats for quick trend visualization
• Box-drawn stat cards with colored change indicators for overviews
• Styled tables with box-drawing borders for detailed data

# Visual output (default)
bettermeter stats -s example.com

# JSON output for scripting
bettermeter stats -s example.com --json | jq '.visitors'

Authentication

Real-Time

Portfolio

Web Analytics

Human-traffic commands exclude known bots, explicit headless automation, and high-confidence scraper cohorts by default. Add --include-bots to stats, pages, sources, timeseries, AI traffic, countries, devices, browsers, sessions, session-stats, channels, goals, goal:show, or goals:suggest to include them.

-l/--limit is accepted by the commands that return a ranked list: pages, sources, bots, countries, browsers, visitors, sessions, events, campaigns, conversions, keywords, campaign:visitors, export, cli-commands, mcp-tools, mcp-clients, and api-endpoints. It has no default of its own: omit it and the command returns the endpoint's own default page, which differs per dataset — today visitors returns 50 rows where pages returns 10 — and the flag is how you ask for a specific number. The summary, trend, and detail commands do not accept it — stats, ai-traffic, timeseries, devices, channels, marketing, ads, campaign, event, and the cli, mcp, and api overview and timeseries commands. On sources --filter and bots --category the limit is applied before the filter, so a filtered result can hold fewer rows than the limit.

CLI Analytics

MCP Analytics

API Analytics

Builder

Pulse AI

Search Rankings and AI Visibility

Paid external scans accept 1-10 queries per request. Competitor comparison accepts up to 10 competitors.

Conversion Goals

Site Management

Team Management

Billing

Options