Analytics - Example Product | Fiskil Docs Guide Docs

Published sites record how readers use your docs — page views, sessions, searches, Ask AI activity, and feedback — and show it all in the Fiskil console under your site's Analytics page. It's on by default, needs no configuration, and collects no personal data: visitors are identified only by random anonymous ids, and browsers with Do Not Track or Global Privacy Control set are never tracked.

Turn it off entirely with one setting:

{
  "analytics": { "enabled": false }
}

What gets recorded

Events use a docs.* naming scheme:

Event	When
`docs.session.start`	A reader arrives (carries the referrer)
`docs.content.view`	A page is viewed
`docs.search.query` / `docs.search.result_click`	A search settles / a result is opened
`docs.assistant.*`	Ask AI opens, messages, completions, citation clicks, thumbs
`docs.feedback.submitted`	A "Was this page helpful?" vote
`docs.code.copy`	A code block is copied

The console turns these into traffic trends, top pages, search terms (with zero-result queries — your content gaps), and referrers, each exportable as CSV.

Send events to your own tools

Add an integration under integrations and the same events also fire into your own analytics project, straight from the reader's browser:

{
  "integrations": {
    "posthog": {
      "apiKey": "phc_your_project_key",
      "apiHost": "https://us.i.posthog.com",
      "sessionRecording": false
    }
  }
}

apiKey is your publishable PostHog project key — safe to commit.
apiHost is only needed for self-hosted or EU-cloud projects.
sessionRecording: false keeps event analytics but disables session replay. Omit it to let your PostHog project settings decide.

PostHog autocaptures page views and sessions natively, so docs.content.view and docs.session.start are not forwarded there — no double counting.

Next: agent tools

Make your docs consumable by AI agents.