Quick start

About 5 minutes from a new project to your first question. AgentHog collects pageviews, clicks, forms and scroll depth on its own; you read the numbers in the dashboard, or ask for them from the ah CLI and your coding agent.

Want to talk with an AgentHog team member? Schedule a free 30-minute consultation.

What are you adding it to?

  1. 1

    Create a project

    You get a key shaped ah_xxxxxxxx. One key covers everything a single product ships on: its website, app and game all report into the same project.

    Create a project
  2. 2

    Let your agent install it

    The AgentHog skill tells your coding agent which SDK this site needs, where the snippet goes, how to name events, and how to check that data arrived. In Claude Code, install the plugin:

    /plugin marketplace add AnniesAI/agenthog-claude
    /plugin install agenthog@agenthog

    In any other agent (Codex, Cursor, Copilot, Gemini and about 70 more), run this instead. Use one or the other, not both:

    npx skills add AnniesAI/agenthog-claude

    Then, in your site’s repo, ask for it with your key:

    add AgentHog analytics to this site — project key <your ah_ key>

    Self-hosted, or want a single skill? More ways to install the skill.

    Rather do it by hand? The full Web install, step by step.
  3. 3

    Check that data arrived

    The skill does this before it reports success. To see it yourself: Load the site and click through a few pages. Then open the dashboard. The web tracker sends every 5 seconds, so the first rows show up within seconds.

  4. 4

    Ask about it

    Install the ah CLI and log in once. ah digest is the one-call summary: sessions, sources, entry pages and top events against the previous window.

    npm i -g @brightmotion/agenthog
    ah login
    ah digest

    From then on your coding agent can answer questions by running ah for you. Ask it in plain words:

    "where do people drop out of signup on mobile?"
    "which campaign brought the visitors who converted this week?"
    "what changed in traffic since Tuesday's deploy?"

    The ah CLI has the CLAUDE.md block that points an agent at it and the verbs worth knowing. Prefer MCP? The MCP server serves the same verbs as tools.

Create an account

Free to start, no credit card. Set up your first project and get its key.

Create account

Talk it through first

Schedule time with an AgentHog team member to talk over the fit and your use case. Free, 30 minutes.

Schedule a call

What to read next

  • Eventsstart here — everything autocapture sends per platform, and how to add your own
  • Server to server — webhooks, jobs and history backfills straight to /ingest
  • Revenue & LTV — net revenue, ARPU and cohort LTV from an event you already send
  • Experiments — feature flags and A/B tests, run from the CLI
  • Shared reports — a live report your whole team can open

Concepts worth knowing early

Event names are a contract

Autocapture emits deterministic, human-readable names — pageview: /pricing, click: Join the waitlist, form_submit: waitlist. That is what lets an agent compose a question without first re-deriving your schema. Custom events keep your name verbatim, so keep varying values in props rather than baked into the name.

Bots are excluded by default

Sessions are classified as human, unknown, suspected bot, or crawler from behavioral and environmental signals. Aggregates count humans and unknowns; pass --all to include bots or --bots to see only them. Traffic from your own devices can be labelled test — see ah test-ips — which is likewise excluded by default and readable with --test.

Projects, orgs, and tokens

A project is one ah_ key, owned by an organization — your website, app, and game can all report into it. Read tokens expose exactly what you can already see in the dashboard and any member can mint one; write tokens are admin-only. Unattended agents and CI should use AH_TOKEN rather than a browser login.