For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Book a demoLog inStart for free
  • Getting started
    • Overview
    • How it works
    • Quickstart
    • Project structure
    • Customer showcase
    • Changelog
  • Configuration
    • Overview
    • Site-level settings
    • Page-level settings
  • Writing content
    • Markdown basics
    • Rich media in Markdown
    • Fern Editor
    • Reusable snippets
  • AI features
    • Overview
    • Fern Writer
    • AI-generated examples
    • Markdown access
      • Overview
      • Customize LLM output
      • Agent directives
      • Analytics and integration
    • MCP server
    • API catalog discovery
      • Overview
      • PostHog
      • Google
      • Segment
      • Mixpanel
      • Analytics events reference
      • Fullstory
      • Intercom
      • Postman
      • Context7
  • Public API
    • GETJWT from Fern API key
    • GETAlgolia search credentials
    • GETCurrent user information
  • Fern Writer API
    • GETGet Fern Writer Install Link
Checking status...
SOC2Soc 2 Type II
© 2026 Fern • Birch Solutions, Inc., a Postman company

Documentation

SDKsDocsAsk FernCLI Reference

API Definitions

OpenAPIAsyncAPIOpenRPCgRPC

Resources

BlogSupportPricing

Company

Brand KitPrivacy PolicyTerms of Service
LogoLogo
Book a demoLog inStart for free
On this page
  • Page views
  • Feedback events
  • API playground events
  • Search and AI events
  • Error events
  • CLI and Dashboard events
Analytics & integrations

Analytics events reference

||View as Markdown|
Was this page helpful?
Edit this page
Previous

Mixpanel

Next

Fullstory

This page lists every analytics event Fern emits from your documentation site. The Forwarded to column in each table shows which configured providers receive that event — not every provider receives every event.

FullStory and Intercom provide session recording and live chat respectively. They don’t receive the named events listed below.

Page views

EventDescriptionForwarded to
$pageviewFired on every route change. Includes the current URL.PostHog, Segment
$pageleaveFired when a user navigates away from a page.PostHog

Page view tracking is automatic and requires no additional configuration. GA4 and Google Tag Manager (GTM) handle their own page view tracking natively when configured.

Feedback events

These events are emitted by the on-page feedback widget and the Ask Fern feedback component.

EventDescriptionForwarded to
feedback_votedUser clicked the thumbs up or thumbs down button.PostHog, GA4, GTM
feedback_submittedUser submitted written feedback after voting.PostHog, GA4, GTM
code_block_feedback_openedUser opened the feedback prompt on a code block.PostHog, GA4, GTM
code_block_feedback_submittedUser submitted feedback on a code block.PostHog, GA4, GTM

API playground events

These events track usage of the API Explorer.

EventDescriptionForwarded to
api_playground_request_sentUser sent a request from the API Explorer.PostHog, GA4, GTM
api_playground_request_receivedA response was received in the API Explorer.PostHog, GA4, GTM

Search and AI events

These events track search and Ask Fern usage.

EventDescriptionForwarded to
ask_ai_suggestAn Ask Fern suggestion was generated.None (Fern internal only)

Error events

These events help identify broken pages and missing content.

EventDescriptionForwarded to
not_foundA visitor hit a 404 page.PostHog, GA4, GTM

CLI and Dashboard events

The Fern CLI and Dashboard emit their own analytics events for internal product telemetry (command usage, onboarding funnels, billing events, etc.). These aren’t forwarded to your analytics providers and are used only by Fern for product improvement.

CLI telemetry can be disabled by setting the FERN_TELEMETRY_DISABLED environment variable or adding telemetry.enabled: false to ~/.fernrc.