Analytics events reference | Fern Documentation

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

Event	Description	Forwarded to
`$pageview`	Fired on every route change. Includes the current URL.	PostHog, Segment
`$pageleave`	Fired 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.

Event	Description	Forwarded to
`feedback_voted`	User clicked the thumbs up or thumbs down button.	PostHog, GA4, GTM
`feedback_submitted`	User submitted written feedback after voting.	PostHog, GA4, GTM
`code_block_feedback_opened`	User opened the feedback prompt on a code block.	PostHog, GA4, GTM
`code_block_feedback_submitted`	User submitted feedback on a code block.	PostHog, GA4, GTM

API playground events

These events track usage of the API Explorer.

Event	Description	Forwarded to
`api_playground_request_sent`	User sent a request from the API Explorer.	PostHog, GA4, GTM
`api_playground_request_received`	A response was received in the API Explorer.	PostHog, GA4, GTM

Search and AI events

These events track search and Ask Fern usage.

Event	Description	Forwarded to
`ask_ai_suggest`	An Ask Fern suggestion was generated.	None (Fern internal only)

Error events

These events help identify broken pages and missing content.

Event	Description	Forwarded to
`not_found`	A 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.