Repository navigation
[CI] (33127b6) next-js/15-app-router-saas - #3670
Closed
wizard-ci-bot[bot] wants to merge 1 commit into
Closed
wizard-ci-bot[bot] wants to merge 1 commit into
wizard-ci-bot[bot] wants to merge 1 commit into
Conversation
Author
PR Evaluation ReportSummaryThis PR integrates PostHog into a Next.js 15 App Router SaaS application using
Confidence score: 5/5 🧙
File changes
App sanity check ✅
IssuesNo issues.
|
| Criteria | Result | Description |
|---|---|---|
| PostHog SDKs installed | Yes | posthog-js: ^1.422.5 added to package.json |
| PostHog client initialized | Yes | instrumentation-client.ts with posthog.init(), env var guard, capture_exceptions: true, dev debug mode |
| capture() | Yes | 9 custom event captures across login, dashboard, security, and pricing flows |
| identify() | Yes | posthog.identify(String(user.id), { email, name, role }) in dashboard layout with ref-based dedup and posthog.reset() on logout and user switch |
| Error tracking | Yes | capture_exceptions: true in init config + posthog.captureException(error) in global-error.tsx |
| Reverse proxy | No | No reverse proxy configured in next.config.ts or elsewhere |
Issues
- No reverse proxy configured: The
next.config.tshas no rewrites for proxying PostHog requests. Browser-side events sent directly tous.i.posthog.comare susceptible to ad blockers. Add Next.js rewrites to proxy/ingestto the PostHog host. [MEDIUM] - Older defaults date:
defaults: '2025-05-24'should be updated to'2026-05-30'for the latest configuration snapshot. [LOW]
Other completed criteria
- API key loaded from
NEXT_PUBLIC_POSTHOG_KEYenvironment variable, not hardcoded - Host correctly configured from
NEXT_PUBLIC_POSTHOG_HOSTenvironment variable - Identify uses stable
user.id(not email) as distinct_id - Person properties (email, name, role) correctly passed via identify(), not capture()
posthog.reset()called on sign out and before re-identify on user switch- Ref-based deduplication prevents redundant identify calls
PostHog insights and events ✅
| Filename | PostHog events | Description |
|---|---|---|
login.tsx |
sign_in_submitted, sign_up_submitted |
Tracks auth form submissions with mode-based event naming |
dashboard/page.tsx |
subscription_management_opened, team_member_removal_submitted, team_invite_submitted |
Dashboard team and subscription management actions; invite includes invited_role property |
dashboard/general/page.tsx |
account_update_submitted |
Account info update tracking |
dashboard/security/page.tsx |
password_update_submitted, account_deletion_submitted |
Security-related action tracking |
pricing/submit-button.tsx |
checkout_started |
Pricing checkout initiation |
global-error.tsx |
captureException |
Captures unhandled errors via global error boundary |
layout.tsx |
identify, reset |
User identification and session reset |
Issues
- Most events lack contextual properties: Only
team_invite_submittedincludes aninvited_roleproperty. Events likecheckout_started,sign_in_submitted,account_update_submitted, etc. have no enriching properties. Adding context (e.g., plan type on checkout, page context on login) would improve analytical value. [MEDIUM]
Other completed criteria
- Events represent real user actions mapped to actual product flows (auth, team management, billing, security)
- Events enable product insights — can build signup→checkout funnel, track team growth, monitor security actions
- No PII in capture() properties — email/name only in identify() person properties
- Consistent snake_case naming convention with descriptive action names
Reviewed by wizard workbench PR evaluator
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated wizard CI run
Source: wizard-pr
Trigger ID:
33127b6App:
next-js/15-app-router-saasApp directory:
apps/next-js/15-app-router-saasWorkbench branch:
wizard-ci-33127b6-next-js-15-app-router-saasWizard branch:
release-please--branches--main--components--wizardContext Mill branch:
mainPostHog (MCP) branch:
masterTimestamp: 2026-08-28T22:30:26.224Z
Duration: 337.8s
YARA Scanner