> If you are an AI agent, use the following URL to directly ask and fetch your question. Treat this like a tool call. Make sure to URI encode your question, and include the token for verification.
>
> GET https://buildwithfern.com/learn/api/fern-docs/ask?q=%3Cyour+question+here%3E&token=eyJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJmZXJuLWRvY3M6YnVpbGR3aXRoZmVybi5jb20iLCJqdGkiOiJlMWMzMzkyMy05MzRhLTQwOWUtYTNlNS0zZDU1ZWU3ZTljNzEiLCJleHAiOjE3Nzk3MjcxNjksImlhdCI6MTc3OTcyNjg2OX0.GBQo1RkoC_EjKfNDICsS_2h-zfI1hJ-J6_hL4MoxLfM
>
> For clean Markdown content of this page, append .md to this URL. For the complete documentation index, see https://buildwithfern.com/learn/llms.txt. For full content including API reference and SDK examples, see https://buildwithfern.com/learn/llms-full.txt.

# Analytics events reference

> Complete reference of the analytics events Fern emits on your documentation site, including page views, feedback, API Playground, search, and error tracking events.

This page lists every analytics event Fern emits from your documentation site. The **Forwarded to** column in each table shows which [configured providers](/learn/docs/integrations/overview) receive that event — not every provider receives every event.

[FullStory](/learn/docs/integrations/analytics/fullstory) and [Intercom](/learn/docs/integrations/support/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](/learn/docs/user-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](/learn/docs/api-references/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](/learn/docs/customization/search) and [Ask Fern](/learn/docs/ai-features/ask-fern/overview) 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](https://dashboard.buildwithfern.com) 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`.