[CI] (1776c51) astro/astro-view-transitions-marketing

[wizard-ci-bot]

Automated wizard CI run

Source: wizard-pr
Trigger ID: 1776c51
App: astro/astro-view-transitions-marketing
App directory: apps/astro/astro-view-transitions-marketing
Workbench branch: wizard-ci-1776c51-astro-astro-view-transitions-marketing
Wizard branch: release-please--branches--main--components--wizard
Context Mill branch: main
PostHog (MCP) branch: master
Timestamp: 2026-07-10T23:20:00.897Z
Duration: 493.5s

YARA Scanner

✓ 60 tool calls scanned, 0 violations detected

No violations: ✓ 60 clean scans

[wizard-ci-bot]

PR Evaluation Report

Summary

This PR integrates PostHog into an Astro marketing site with View Transitions by adding a reusable posthog.astro component using the HTML snippet approach, wiring it into the shared layout, and instrumenting click/view events across homepage CTAs, pricing, features, docs, navigation, footer, and about page sections. The View Transitions guard and capture_pageview: 'history_change' are correctly implemented.

Files changed	Lines added	Lines removed
11	+281	-43

Confidence score: 3/5 🤔

• No user identification: No posthog.identify() call exists anywhere in the codebase. For a client-only marketing site, identify should be called when users log in or provide identifiable info (e.g., "Get Started" / "Start Free Trial" flows). [CRITICAL]
• No error tracking: No captureException or error boundary setup is implemented. [MEDIUM]
• No reverse proxy configured: No reverse proxy is set up, making tracking susceptible to ad blockers on this client-only site. [MEDIUM]
• Redundant posthog-js in package.json: The npm package is added but never imported — the integration exclusively uses the HTML snippet approach. This is unnecessary. [MEDIUM]
• No .env.example for environment variables: PUBLIC_POSTHOG_PROJECT_TOKEN and PUBLIC_POSTHOG_HOST are not documented anywhere for collaborators. [MEDIUM]

---

File changes

Filename	Score	Description
src/components/posthog.astro	4/5	New PostHog initialization component using HTML snippet with View Transitions guard and is:inline directive
src/layouts/Layout.astro	5/5	Imports and adds PostHog component to the shared layout head
package.json	3/5	Adds posthog-js to dependencies but it's never imported (snippet used instead)
src/pages/index.astro	4/5	Adds CTA click tracking with data attributes and inline script
src/pages/pricing.astro	4/5	Adds pricing plan selection and enterprise contact tracking
src/pages/features.astro	3/5	Adds feature card click tracking but unnecessarily changes div to button elements
src/pages/docs.astro	4/5	Adds docs topic selection tracking
src/pages/about.astro	5/5	Adds IntersectionObserver-based visibility tracking for team section
src/components/Navigation.astro	4/5	Adds nav link and CTA click tracking
src/components/Footer.astro	4/5	Adds footer link click tracking
posthog-setup-report.md	4/5	Setup report with event table and next steps

---

App sanity check ⚠️

Criteria	Result	Description
App builds and runs	Yes	No syntax errors; all scripts use is:inline correctly
Preserves existing env vars & configs	No	features.astro changes div elements to button elements, altering existing HTML structure
No syntax or type errors	Yes	All inline scripts are valid JavaScript
Correct imports/exports	Yes	PostHog component import in Layout is correct
Minimal, focused changes	No	posthog-js added to package.json but unused; div→button changes in features page
Pre-existing issues	None	No pre-existing issues identified

Issues

• Redundant npm dependency: posthog-js is added to package.json but the integration uses the HTML snippet approach exclusively. The package is never imported anywhere. Remove it or switch to the npm import pattern. [MEDIUM]
• Unnecessary HTML structure changes: features.astro changes 9 div.feature-card elements to button.feature-card elements. While arguably better for accessibility with click handlers, this alters the existing DOM structure and could affect styling (buttons have different default styles than divs). [MEDIUM]
• Missing environment variable documentation: PUBLIC_POSTHOG_PROJECT_TOKEN and PUBLIC_POSTHOG_HOST are not documented in any .env.example file. [MEDIUM]

Other completed criteria

• All changes are related to PostHog integration
• Correct Astro files modified (component, layout, pages)
• Code follows existing Astro patterns with is:inline scripts and data attributes
• Build configuration is valid

---

PostHog implementation ⚠️

Criteria	Result	Description
PostHog SDKs installed	Yes	HTML snippet added via posthog.astro component (npm package also added but unused)
PostHog client initialized	Yes	Correctly initialized with is:inline, define:vars, View Transitions guard (window.__posthog_initialized), and capture_pageview: 'history_change'
capture()	Yes	10 distinct events captured across pages and components
identify()	No	No posthog.identify() call anywhere in the codebase
Error tracking	No	No captureException or error handling setup
Reverse proxy	No	No reverse proxy configured; client-side tracking vulnerable to ad blockers

Issues

• Missing user identification: No posthog.identify() call exists. For a marketing site with "Get Started" and "Start Free Trial" CTAs, identify should be called when users authenticate or provide identifying information. Without it, all events are anonymous and cannot be linked to known users. [CRITICAL]
• No error tracking: No captureException setup. The snippet does include captureException in the stub methods, but no actual error boundary or try/catch handling is implemented. [MEDIUM]
• No reverse proxy: No proxy configured to circumvent ad blockers. For a marketing site where tracking accuracy matters, this is a notable gap. [MEDIUM]
• Older snippet version: The snippet uses s.api_host+'/static/array.js' instead of the newer pattern s.api_host.replace(".i.posthog.com", "-assets.i.posthog.com") + "/static/array.js" which routes through the assets CDN. Functional but not optimal. [LOW]

Other completed criteria

• API key loaded from environment variable (PUBLIC_POSTHOG_PROJECT_TOKEN via define:vars)
• API host correctly configured from environment variable (PUBLIC_POSTHOG_HOST)
• Uses PUBLIC_ prefix as required by Astro for client-side env vars
• View Transitions compatibility correctly handled with initialization guard and astro:page-load listeners
• All scripts use is:inline directive as required by Astro

---

PostHog insights and events ✅

Filename	PostHog events	Description
src/pages/index.astro	cta_clicked, docs_cta_clicked	Tracks hero CTA clicks with location and CTA name properties
src/pages/pricing.astro	pricing_plan_selected, enterprise_contact_clicked	Tracks plan selection with plan name and billing period
src/pages/features.astro	feature_card_selected	Tracks which feature cards visitors click with feature name
src/pages/docs.astro	docs_topic_selected	Tracks documentation topic selection with topic name
src/pages/about.astro	about_team_section_viewed	IntersectionObserver tracks when team section scrolls into view (50% threshold)
src/components/Navigation.astro	nav_link_clicked, nav_cta_clicked	Tracks navigation usage with link name and destination
src/components/Footer.astro	footer_link_clicked	Tracks footer link clicks with link name and destination

Issues

• No critical or medium issues with event quality.

Other completed criteria

• Events represent real user actions (CTA clicks, navigation, content views)
• Events enable product insights (homepage→pricing funnel, feature interest, navigation patterns)
• Events include contextual properties (plan_name, feature_name, page_path, destination_path)
• No PII in event properties
• Event names are descriptive and follow consistent snake_case convention
• Duplicate binding prevented via data-posthogBound flag across all scripts
• Both DOMContentLoaded and astro:page-load listeners ensure tracking works with View Transitions

---

Reviewed by wizard workbench PR evaluator