[CI] (afd8cc2) react-router/saas-template

[wizard-ci-bot]

Automated wizard CI run

Source: manual
Trigger ID: afd8cc2
App: react-router/saas-template
App directory: apps/react-router/saas-template
Workbench branch: wizard-ci-afd8cc2-react-router-saas-template
Wizard branch: main
Examples branch: main
PostHog (MCP) branch: master
Timestamp: 2026-01-16T14:04:30.475Z
Duration: 608.3s

[wizard-ci-bot]

Now I have read all the key files. Let me compile the PR evaluation report.

---

PR Evaluation Report

Summary

This PR integrates PostHog analytics into a React Router 7 SaaS template application. It adds both client-side (posthog-js, @posthog/react) and server-side (posthog-node) tracking with middleware for session correlation, error boundary exception capture, and 13 business events covering user authentication, billing/subscriptions, and organization management.

Files changed	Lines added	Lines removed
26	+978	-151

Confidence score: 4/5 👍

• No reverse proxy configured: The integration does not include a reverse proxy setup to circumvent ad blockers, which is a PostHog best practice for ensuring event delivery. [MEDIUM]
• Missing posthog.identify() calls: No user identification is implemented. Events are captured but users are not explicitly identified with their user ID/email, limiting analytics accuracy. [MEDIUM]
• No automatic pageview tracking: The client-side initialization doesn't enable capture_pageview: true or use a manual pageview tracking mechanism for SPA navigation. [MEDIUM]

---

File changes

Filename	Score	Description
.env.example	5/5	Adds PostHog env vars with correct defaults
app/entry.client.tsx	4/5	PostHog client init with provider wrapper and tracing headers
app/lib/posthog-middleware.server.ts	4/5	New server-side middleware with session correlation via withContext
app/root.tsx	4/5	Adds middleware registration and error boundary with captureException
app/utils/env.server.ts	5/5	Adds PostHog env validation schema
vite.config.ts	5/5	Adds SSR noExternal config for PostHog packages
package.json	5/5	Adds required PostHog dependencies
app/features/billing/stripe-event-handlers.server.ts	4/5	Adds 4 billing events with proper shutdown handling
app/features/billing/contact-sales/contact-sales-action.server.ts	5/5	Adds contact sales event tracking
app/features/user-authentication/login/login-action.server.ts	4/5	Adds login tracking with method property
app/features/user-authentication/registration/register-action.server.ts	4/5	Adds signup tracking with method property
app/routes/_user-authentication+/logout.ts	5/5	Adds logout event tracking
app/features/organizations/create-organization/create-organization-action.server.ts	5/5	Adds organization creation tracking
app/features/organizations/accept-invite-link/accept-invite-link-action.server.ts	5/5	Adds invite acceptance tracking
app/features/user-accounts/settings/account/account-settings-action.server.ts	5/5	Adds account update and deletion tracking
app/features/onboarding/user-account/onboarding-user-account-action.server.ts	5/5	Adds onboarding completion tracking
app/features/pastebin/paste-helpers.server.ts	5/5	Code formatting changes only (Infinity → Number.POSITIVE_INFINITY)
app/features/organizations/layout/app-sidebar.tsx	5/5	Minor import reordering
app/routes/...dashboard.tsx	5/5	Code formatting and Number.POSITIVE_INFINITY updates
app/routes/...pastes.tsx	5/5	Code formatting changes
app/routes/...pastes..tsx	5/5	Code formatting changes
app/routes/..._sidebar-layout.tsx	5/5	Minor formatting change
app/routes/p..tsx	5/5	Code formatting changes
app/routes/paste..tsx	5/5	Code formatting changes
posthog-setup-report.md	5/5	Documentation of integration

---

App sanity check: 4/5 ✅

Criteria	Result	Description
App builds and runs	Yes	PostHog packages properly added, SSR config correct
Preserves existing env vars & configs	Yes	Only adds new PostHog vars, existing configs untouched
No syntax or type errors	Yes	TypeScript types properly defined with PostHogContext interface
Correct imports/exports	Yes	All imports correctly reference posthog-js, posthog-node, and @posthog/react
Minimal, focused changes	Yes	Most non-PostHog changes are code formatting (Biome auto-fixes)

Issues

• package.json key reordering: The package.json was reformatted with keys alphabetized. While this doesn't break functionality, it creates unnecessary diff noise. [LOW]

Other completed criteria

• Environment variables properly documented in .env.example
• Server environment schema validates PostHog vars at startup
• Vite SSR configuration prevents bundling issues
• PostHog middleware properly shuts down after each request
• Error handling preserved in all modified action files

---

PostHog implementation: 3/5 ⚠️

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog-js@^1.325.0, posthog-node@^5.21.0, @posthog/react@^1.5.2
PostHog client initialized	Yes	Client init in entry.client.tsx with tracing headers, middleware for server-side
capture()	Yes	13 events tracked across auth, billing, org management
identify()	No	No posthog.identify() calls to link anonymous users to authenticated users
Error tracking	Yes	captureException() in root ErrorBoundary
Reverse proxy	No	No proxy configuration to circumvent ad blockers

Issues

• Missing user identification: No posthog.identify() implementation. Users are tracked with session/distinct IDs from headers but never explicitly identified with their user account ID or email. This limits user-level analytics and prevents proper user journey tracking across sessions. [CRITICAL]
• No reverse proxy: Events sent directly to PostHog can be blocked by ad blockers, reducing data accuracy. The api_host points directly to us.i.posthog.com. [MEDIUM]
• No automatic pageview tracking: Client-side init uses defaults: "2025-11-30" but doesn't explicitly configure pageview tracking. For SPAs, capture_pageview should be set or manual tracking added on navigation. [MEDIUM]
• Tracing headers may not work without additional setup: The __add_tracing_headers config references window.location.host but the middleware reads X-POSTHOG-SESSION-ID and X-POSTHOG-DISTINCT-ID headers that may not be automatically added by posthog-js without proper configuration. [LOW]

Other completed criteria

• PostHogProvider wraps the app correctly
• Server-side PostHog instances properly shutdown after each request
• Middleware extracts session/distinct IDs from headers
• withContext used for session correlation
• Events don't contain PII (only organization names, company names - business data)

---

PostHog insights and events: 4/5 ✅

Filename	PostHog events	Description
register-action.server.ts	user_signed_up	Tracks signup with `method: 'email'
login-action.server.ts	user_logged_in	Tracks login with auth method
logout.ts	user_logged_out	Tracks logout action
create-organization-action.server.ts	organization_created	Tracks org creation with name and ID
accept-invite-link-action.server.ts	invite_link_accepted	Tracks invite acceptance with org details
onboarding-user-account-action.server.ts	onboarding_user_completed	Tracks onboarding with avatar status
contact-sales-action.server.ts	contact_sales_submitted	Tracks sales form submission
stripe-event-handlers.server.ts	checkout_completed, subscription_created, subscription_cancelled, subscription_updated	Full billing lifecycle tracking with revenue properties
account-settings-action.server.ts	user_account_updated, user_account_deleted	Tracks account changes and churn
root.tsx	captureException	Error tracking in ErrorBoundary

Issues

• Missing pastebin feature events: The app's core feature (pastebin) has no event tracking. Events like paste_created, paste_viewed, paste_deleted would provide valuable product usage insights. [MEDIUM]
• Stripe events use customer ID as distinctId: The billing events use Stripe customer ID rather than user/organization ID, which may not correlate well with user sessions tracked on the client. [LOW]

Other completed criteria

• Events cover complete user lifecycle (signup → login → onboarding → usage → churn)
• Billing events track revenue-related properties (amount, currency)
• Auth events track method used (email vs OAuth)
• Subscription events track cancellation reasons for churn analysis
• Events are semantically named with underscores for consistency

---

Reviewed by wizard workbench PR evaluator