For AI agents: the documentation index is at llms.txt. Markdown versions are available by appending .md to any page URL, including this page's markdown.
PostHog analytics
Connect your own PostHog project key in the dashboard to load analytics on every tenant docs page, with an optional EU host and no content wiring.
All deployed Edda docs sites report pageviews and docs interactions to the shared blode.co PostHog project, including tenant subdomains, custom domains and proxied docs. Local development is excluded.
You can also send analytics to your own PostHog project. Add its public key in the dashboard.
Add PostHog
- Open the dashboard, pick your project, and go to Settings → Analytics.
- Fill in:
- PostHog: paste your project API key (starts with
phc_). Find it in PostHog → Project settings. Personal API keys (phx_) are not supported. - PostHog host: optional. Defaults to
https://us.i.posthog.com. Usehttps://eu.i.posthog.comif your project lives in the EU cloud.
- PostHog: paste your project API key (starts with
- Save. The next request on your tenant domain loads the script.
Leave the project key empty to disable your additional project. Shared platform analytics remain enabled.
How it works
When tenant analytics are configured, every request through the docs proxy carries a compact, tenant-scoped header that the root layout reads on the server. We inject a small PostHog provider that initializes posthog-js with capture_pageview: false and emits a $pageview event on every client-side navigation.
Your additional project only loads when VERCEL_ENV === "production". It uses a separate SDK instance, so it cannot replace the shared project. Selecting the blode.co project key does not send duplicate pageviews.
PostHog project keys are public client-side tokens: they are designed to be shipped to the browser. Edda treats them as tenant configuration, not secrets, and surfaces them in the dashboard as-is.
Published with Edda