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

[wizard-ci-bot]

Automated wizard CI run

Source: manual
Trigger ID: 3864784
App: react-router/saas-template
App directory: apps/react-router/saas-template
Workbench branch: wizard-ci-3864784-react-router-saas-template
Wizard branch: main
Examples branch: main
PostHog (MCP) branch: master
Timestamp: 2026-01-21T22:31:14.698Z
Duration: 705.6s

[wizard-ci-bot]

Now I have reviewed all the key files. Let me provide the evaluation report:

---

PR Evaluation Report

Summary

This PR integrates PostHog analytics into a React Router 7 SaaS template, adding comprehensive event tracking for user authentication, organization management, subscription billing, and Stripe webhook events. The implementation includes both client-side (posthog-js, @posthog/react) and server-side (posthog-node) SDKs with proper middleware setup and error tracking.

Files changed	Lines added	Lines removed
23	+484	-12

Confidence score: 4/5 👍

• Missing user identification: posthog.identify() is never called on the client side after login/signup to link anonymous sessions to authenticated users. [MEDIUM]
• Missing reverse proxy: No reverse proxy configuration to circumvent ad-blocker issues when sending events to PostHog. [MEDIUM]
• Email PII in events: The user_logged_in and user_signed_up events capture email as a property, which could be considered PII. [LOW]

---

File changes

Filename	Score	Description
app/entry.client.tsx	4/5	Properly initializes PostHog client-side with PostHogProvider wrapper and tracing headers. Missing identify() call setup.
app/lib/posthog-middleware.server.ts	5/5	Clean server-side middleware implementation using posthog-node with proper context passing and shutdown handling.
app/root.tsx	4/5	Correctly adds PostHog middleware and error boundary exception capture.
app/features/billing/billing-action.server.ts	5/5	Comprehensive tracking for subscription lifecycle events with proper error capture.
app/features/billing/stripe-event-handlers.server.ts	4/5	Good webhook event tracking with dedicated PostHog client instances and proper shutdown.
app/routes/_user-authentication+/_anonymous-routes+/auth.callback.ts	4/5	Tracks signup, login, and invite acceptance events. Missing identify() integration.
app/routes/pricing.tsx	5/5	Clean pricing page view tracking with ref to prevent duplicate events.
app/features/billing/contact-sales/contact-sales-action.server.ts	5/5	Simple, focused tracking for contact sales submissions.
app/features/onboarding/organization/onboarding-organization-action.server.ts	5/5	Good organization creation tracking with relevant properties.
app/features/organizations/create-organization/create-organization-action.server.ts	5/5	Consistent organization creation tracking.
vite.config.ts	5/5	Correct SSR noExternal configuration for PostHog packages.
package.json	5/5	Required dependencies properly added. Alphabetical sorting applied.
.env.example	5/5	Environment variables properly documented.
Other files	4/5	Mostly code formatting/cleanup changes (import sorting, Infinity → Number.POSITIVE_INFINITY).

---

App sanity check: 4/5 ✅

Criteria	Result	Description
App builds and runs	Yes	No syntax errors, proper imports, dependencies installed
Preserves existing env vars & configs	Yes	Only adds new PostHog env vars, doesn't modify existing ones
No syntax or type errors	Yes	TypeScript types properly used with PostHogContext interface
Correct imports/exports	Yes	All imports are correct and packages are installed
Minimal, focused changes	Partial	Some unrelated formatting changes (import sorting, Infinity refactors)

Issues

• Non-essential refactoring: Changes to paste-helpers.server.ts, dashboard.tsx, pastes.tsx, and sidebar files include import re-ordering and Infinity → Number.POSITIVE_INFINITY changes unrelated to PostHog. These are minor but add noise. [LOW]

Other completed criteria

• Clear, readable code with consistent patterns
• Proper TypeScript typing for PostHog context
• Graceful handling when PostHog env vars are not set
• Appropriate error handling with captureException

---

PostHog implementation: 4/5 ✅

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog-js, @posthog/react, posthog-node added to dependencies
PostHog client initialized	Yes	Client-side in entry.client.tsx with Provider; Server-side via middleware in posthog-middleware.server.ts
capture()	Yes	13+ events tracked across auth, billing, organization, and pricing flows
identify()	No	posthog.identify() is never called to link anonymous sessions to authenticated users
Error tracking	Yes	captureException() in error boundary and catch blocks
Reverse proxy	No	No reverse proxy configured to bypass ad blockers

Issues

• Missing posthog.identify(): After user login or signup, there is no posthog.identify(userId) call to link the anonymous session to the authenticated user. This is critical for accurate user journey tracking. Add identify call in auth callback or upon successful authentication. [MEDIUM]
• No reverse proxy setup: Events sent directly to us.i.posthog.com will be blocked by ad blockers. Recommend adding a reverse proxy route in the React Router app to proxy /ingest to PostHog. [MEDIUM]
• Email in event properties: The user_logged_in and user_signed_up events include email in properties. Consider using posthog.identify() instead to set user properties separately. [LOW]

Other completed criteria

• API key from environment variable (not hardcoded)
• Correct API host configuration (us.i.posthog.com)
• PostHog Provider wraps application correctly
• Server-side middleware with proper shutdown
• Tracing headers enabled for client-server correlation
• Proper context passing via middleware
• Webhook handlers create dedicated PostHog instances and shut down properly

---

PostHog insights and events: 5/5 ✅

Filename	PostHog events	Description
auth.callback.ts	user_signed_up, user_logged_in, invite_link_accepted	Full auth funnel tracking with invite type differentiation
pricing.tsx	pricing_page_viewed	Top-of-funnel conversion tracking
billing-action.server.ts	subscription_cancelled, checkout_session_started, subscription_resumed, subscription_plan_switched, captureException	Complete billing action tracking
stripe-event-handlers.server.ts	checkout_completed, subscription_created, subscription_updated, subscription_deleted, captureException	Webhook event tracking for subscription lifecycle
onboarding-organization-action.server.ts	organization_created	Onboarding funnel with company size, types, referral sources
create-organization-action.server.ts	organization_created	Post-onboarding org creation tracking
contact-sales-action.server.ts	contact_sales_form_submitted	Enterprise lead tracking
root.tsx	captureException	Global error boundary tracking

Issues

None - the events are well-designed for building funnels and answering product questions.

Other completed criteria

• Events capture real user actions and product flows
• Events enriched with relevant properties (organization_id, subscription_id, etc.)
• Full signup → organization → checkout funnel trackable
• Subscription lifecycle fully instrumented
• Error tracking across all critical paths
• Differentiates between onboarding and post-onboarding org creation
• Tracks invite acceptance with type (email vs link) and new user flag

---

Reviewed by wizard workbench PR evaluator