[CI] (3864784) next-js/15-app-router-saas

[wizard-ci-bot]

Automated wizard CI run

Source: manual
Trigger ID: 3864784
App: next-js/15-app-router-saas
App directory: apps/next-js/15-app-router-saas
Workbench branch: wizard-ci-3864784-next-js-15-app-router-saas
Wizard branch: main
Examples branch: main
PostHog (MCP) branch: master
Timestamp: 2026-01-21T22:26:41.862Z
Duration: 440.9s

[wizard-ci-bot]

The files are not present locally, so I'll analyze based on the diff provided. Let me provide a comprehensive evaluation based on the diff contents.

---

PR Evaluation Report

Summary

This PR integrates PostHog analytics into a Next.js 15 App Router SaaS application. It adds both client-side (posthog-js) and server-side (posthog-node) tracking with comprehensive event capture across authentication, payments, and team management flows. The implementation includes a reverse proxy configuration and follows modern Next.js 15.3+ initialization patterns.

Files changed	Lines added	Lines removed
13	+669	-5

Confidence score: 3/5 🤔

• Missing await posthog.shutdown(): Server-side PostHog calls in server actions and API routes do not await shutdown(), which can result in lost events in serverless environments. [CRITICAL]
• PII in event properties: Email addresses are being captured in multiple events (user_signed_in, user_signed_up, account_deleted, account_updated). This should be avoided or documented as intentional. [MEDIUM]
• Missing await on async getUser(): In lib/payments/actions.ts, the getUser() call appears to be awaited but the posthog event could fire before the user is fully resolved. [LOW]

---

File changes

Filename	Score	Description
.env.example	5/5	Properly documents PostHog env vars with helpful comments
app/(dashboard)/pricing/page.tsx	5/5	Clean integration of tracking component
app/(dashboard)/pricing/pricing-tracker.tsx	5/5	Well-implemented client component with ref to prevent double-firing
app/(login)/actions.ts	3/5	Comprehensive tracking but includes PII (emails), missing shutdown calls
app/api/stripe/checkout/route.ts	3/5	Good event tracking and error capture, missing shutdown call
app/api/stripe/webhook/route.ts	3/5	Captures subscription events, missing shutdown call
instrumentation-client.ts	4/5	Correct Next.js 15.3+ pattern, uses defaults: '2025-05-24' which is good
lib/payments/actions.ts	4/5	Good checkout_started tracking, proper async handling
lib/posthog-server.ts	4/5	Singleton pattern with shutdown helper, but flushAt: 1, flushInterval: 0 may impact performance
next.config.ts	5/5	Correct reverse proxy configuration for ad-blocker bypass
package.json	5/5	Both posthog-js and posthog-node added with recent versions
pnpm-lock.yaml	5/5	Lock file properly updated
posthog-setup-report.md	4/5	Good documentation but links to PostHog dashboards that may not exist

---

App sanity check: 4/5 ✅

Criteria	Result	Description
App builds and runs	Yes	No syntax errors, proper TypeScript types
Preserves existing env vars & configs	Yes	Added new env vars without removing existing ones
No syntax or type errors	Yes	All imports and exports appear correct
Correct imports/exports	Yes	Named exports used consistently
Minimal, focused changes	Yes	Changes limited to PostHog integration

Issues

• Documentation file created: A posthog-setup-report.md file was created without explicit user request. This is acceptable for setup documentation but should be noted. [LOW]

Other completed criteria

• Environment variables properly documented in .env.example
• Build configuration valid with rewrites and skipTrailingSlashRedirect
• Consistent code patterns with existing codebase
• Clear, readable code with comments explaining initialization approach

---

PostHog implementation: 3/5 ⚠️

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog-js@^1.333.0 and posthog-node@^5.24.1 in package.json
PostHog client initialized	Yes	Client via instrumentation-client.ts, server via singleton in lib/posthog-server.ts
capture()	Yes	12+ events captured across auth, payments, and team flows
identify()	Yes	User identification on sign-in and sign-up with properties
Error tracking	Yes	capture_exceptions: true client-side, `` event in checkout route
Reverse proxy	Yes	Configured in next.config.ts with /ingest path

Issues

• Missing shutdown in serverless context: Server-side posthog.capture() and posthog.identify() calls are not followed by await posthog.shutdown(). In serverless/edge environments, this can cause events to be lost before the function terminates. Add await getPostHogClient().shutdown() after server-side PostHog calls. [CRITICAL]
• PII captured in events: Email addresses are included in event properties for user_signed_in, user_signed_up, account_deleted, and account_updated. Consider removing PII or ensuring this aligns with privacy policies. [MEDIUM]
• flushAt: 1, flushInterval: 0 configuration: While this ensures immediate flushing, it may create performance overhead. Consider using default values with explicit shutdown calls instead. [LOW]

Other completed criteria

• API key sourced from environment variable (NEXT_PUBLIC_POSTHOG_KEY)
• API host correctly configured via env var and reverse proxy
• Client-side uses modern instrumentation-client.ts pattern (Next.js 15.3+)
• Proper ui_host configuration for PostHog toolbar
• Debug mode enabled only in development
• Comment warning against combining with PostHogProvider

---

PostHog insights and events: 4/5 ✅

Filename	PostHog events	Description
actions.ts (login)	user_signed_in, user_signed_up, user_signed_out, password_updated, account_deleted, account_updated, team_member_removed, team_member_invited	Core user lifecycle and team management events for retention and engagement analysis
checkout/route.ts	checkout_completed, ``	Conversion completion and error tracking for payment flow
webhook/route.ts	subscription_updated	Subscription lifecycle for MRR and churn analysis
payments/actions.ts	checkout_started	Top of payment funnel for conversion analysis
pricing-tracker.tsx	pricing_page_viewed	Entry point to conversion funnel
instrumentation-client.ts	(automatic pageviews, exceptions)	Client-side automatic capture via posthog-js

Issues

• Missing feature usage events: The integration focuses heavily on auth and payments but doesn't capture feature usage within the dashboard. Consider adding events for core product actions. [LOW]

Other completed criteria

• Events enable funnel analysis (pricing_page_viewed → checkout_started → checkout_completed)
• Events support churn analysis (account_deleted, subscription_updated with cancel status)
• Properties enriched with teamId, userId, subscription details
• Exception capture enables error tracking correlation
• Events support team collaboration analysis (invited, removed)

---

Reviewed by wizard workbench PR evaluator