Skip to content

docs: document built-in analytics dashboard#6192

Closed
fern-api[bot] wants to merge 3 commits into
mainfrom
devin/built-in-analytics-docs-1783695579
Closed

docs: document built-in analytics dashboard#6192
fern-api[bot] wants to merge 3 commits into
mainfrom
devin/built-in-analytics-docs-1783695579

Conversation

@fern-api

@fern-api fern-api Bot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

Summary

Documents Fern's built-in docs analytics dashboard (the "Web Analytics" view in the Fern Dashboard), which was previously undocumented in the public docs. Prompted by a customer question about what insights Fern's built-in analytics provides.

Adds a new page fern/products/docs/pages/integrations/analytics/built-in.mdx and wires it into the Analytics & integrations section of fern/products/docs/docs.yml (slug analytics/built-in, placed right after Overview so readers see the native option first).

The page:

  • Explains that built-in analytics works automatically with no configuration, and clearly distinguishes it from forwarding analytics events to third-party providers (GA4/GTM, PostHog, Segment, Mixpanel) configured via analytics: in docs.yml. Cross-links the overview and analytics events reference.
  • Documents how to open the Web Analytics view, the selectable time periods (7/14/30/90/180 days) and Refresh, and the ~3-4h data delay.
  • Lists the metrics surfaced (overview page views/visitors/sessions, top pages, top countries, traffic channels, device types, referring domains, LLM file views, API Explorer requests, LLM bot traffic by provider) — sourced from redshift-analytics.ts and the analytics service README in fern-api/fern-platform.

Also adds a changelog entry (pages/changelog/2026-07-10.mdx) announcing the built-in analytics dashboard.

Plan/entitlement gating

Not gated by plan. Verified in fern-api/fern-platform: the Web Analytics route (.../web-analytics/page.tsx) and getWebAnalytics action gate access only on org membership (getAuthenticatedSessionOrRedirect / verifyDomainAccessassertUserHasOrganizationAccess). There is no entitlement/upsell check in the web-analytics page or components. The page therefore makes no plan-tier claims. Please confirm this matches product intent before publishing.

For human review

  • Changelog date caveat: this documents an existing feature, so the 2026-07-10 changelog entry announces something that shipped earlier. Keep, re-date, or drop as you see fit.
  • Vale could not be run in-session (binary download blocked by network policy); content was checked manually against the FernStyles rules (Reject/Current/Hedges/Please/Headings/HeadingPunctuation). Please rely on CI Vale results.
  • Assigned to devalog.

@fern-api fern-api Bot requested a review from devalog as a code owner July 10, 2026 15:00

1. Open the [Fern Dashboard](https://dashboard.buildwithfern.com) and select your docs site.
2. Go to the **Web Analytics** view.
3. Select a time period (7, 14, 30, 90, or 180 days). Use **Refresh** to recompute the metrics from the most recent data.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 [vale] reported by reviewdog 🐶
[Microsoft.Wordiness] Consider using 'time' instead of 'time period'.

| LLM bot traffic | AI crawler access, grouped by provider. |

<Note>
Analytics data reflects a delay of roughly three to four hours as events replicate from the underlying event pipeline. Recent traffic may not appear immediately.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 [vale] reported by reviewdog 🐶
[FernStyles.Adverbs] Remove 'roughly' if it's not important to the meaning of the statement.

@github-actions

Copy link
Copy Markdown
Contributor

@devalog devalog closed this Jul 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant