Skip to content

Enable PostHog pageview and pageleave tracking #319

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Ganeshship wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Enable PostHog pageview and pageleave tracking #319

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions website/_layouts/default.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -455,6 +455,8 @@
api_host: 'https://us.i.posthog.com',
defaults: '2026-01-30',
person_profiles: 'identified_only',
capture_pageview: true,
capture_pageleave: true,
Comment on lines +458 to +459
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot Apr 24, 2026

Choose a reason for hiding this comment

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

high

The PostHog initialization and snippet are currently located at the bottom of the <body>. For more accurate tracking of 'total site traffic' and to ensure that $pageview and $pageleave events (as well as existing custom events like docs_download_click) are captured for users who interact with the page or navigate away before the script is reached, it is recommended to move the PostHog <script> block into the <head> section. Since the library is loaded asynchronously (p.async=!0), moving it to the head will not block page rendering but will significantly improve the reliability of your analytics data.

});
</script>
</body>
Expand Down
Loading