Skip to content

[CI] (624abe2) stripe/stripe-next-js-saas-starter - #4465

Closed
wizard-ci-bot[bot] wants to merge 1 commit into
mainfrom
wizard-ci-624abe2-stripe-stripe-next-js-saas-starter
Closed

wizard-ci-bot[bot] wants to merge 1 commit into
mainfrom
wizard-ci-624abe2-stripe-stripe-next-js-saas-starter

Conversation

@wizard-ci-bot

@wizard-ci-bot wizard-ci-bot Bot commented Oct 8, 2026

Copy link
Copy Markdown

Automated wizard CI run

Source: wizard-pr
Trigger ID: 624abe2
App: stripe/stripe-next-js-saas-starter
App directory: apps/stripe/stripe-next-js-saas-starter
Workbench branch: wizard-ci-624abe2-stripe-stripe-next-js-saas-starter
Wizard branch: release-please--branches--main--components--wizard
Context Mill branch: main
PostHog (MCP) branch: master
Timestamp: 2026-10-08T09:24:02.041Z
Duration: 129.2s

YARA Scanner

✓ 28 tool calls scanned, 0 violations detected

No violations: ✓ 28 clean scans

@wizard-ci-bot

wizard-ci-bot Bot commented Oct 8, 2026

Copy link
Copy Markdown
Author

PR Evaluation Report

Summary

This PR adds posthog_person_distinct_id metadata to Stripe Checkout Sessions and their associated subscription data, enabling PostHog's revenue analytics to link Stripe transactions back to PostHog persons. The change is minimal — two metadata objects added to createCheckoutSession — plus a report file. No PostHog SDK is installed or initialized; this PR only bridges Stripe metadata to PostHog.

Files changed Lines added Lines removed
2 +26 -1

Confidence score: 3/5 🤔

  • No PostHog SDK installed or initialized: The PR adds Stripe metadata only. Without the PostHog SDK present in the app, there is no event capture, no user identification, no error tracking, and no reverse proxy — none of the core PostHog integration criteria are met. [CRITICAL]
  • No capture() calls or analytics events: The revenue-analytics wizard produced no PostHog event instrumentation whatsoever. The Stripe metadata alone enables server-side revenue correlation only if PostHog is separately installed and configured, which this PR does not do. [CRITICAL]
  • No error tracking configured: No captureException or error boundary setup. [MEDIUM]

File changes

Filename Score Description
lib/payments/stripe.ts 4/5 Adds posthog_person_distinct_id metadata to both the Checkout Session and subscription_data using the stable database user ID. Clean, minimal change that follows existing code patterns.
posthog-revenue-report.md 3/5 Report documenting the changes and manual verification steps. Adequate but the PR itself is very narrow.

App sanity check ✅

Criteria Result Description
App builds and runs Yes Simple metadata addition to an existing Stripe API call; no syntax or type issues
Preserves existing env vars & configs Yes No env vars, configs, or existing functionality modified
No syntax or type errors Yes Valid TypeScript; metadata accepts arbitrary string key-value pairs in Stripe's API
Correct imports/exports Yes No new imports needed; uses existing user.id
Minimal, focused changes Yes Only 7 lines added to one source file — exactly what's needed for Stripe metadata
Pre-existing issues None —

Issues

No issues.

Other completed criteria

  • Environment variables: no new env vars introduced; existing user.id from auth context is used
  • Build configuration unchanged
  • All existing code paths preserved intact

PostHog implementation ❌

Criteria Result Description
PostHog SDKs installed No No posthog-js or posthog-node added to dependencies. No <script> tag snippet either.
PostHog client initialized No No posthog.init() or Node SDK initialization anywhere in the PR
capture() No No event capture calls added
identify() No No user identification implemented
Error tracking No No error tracking or exception capture configured
Reverse proxy N/A No client-side SDK present to proxy

Issues

  • No PostHog SDK present: The PR only adds Stripe metadata (posthog_person_distinct_id) but does not install or initialize any PostHog SDK. Without the SDK, this metadata can only work if PostHog is already integrated elsewhere — but there's no evidence of that in this PR's scope. The revenue-analytics wizard should ensure the SDK is available for the metadata linkage to be useful. [CRITICAL]
  • No event capture: Zero capture() calls. Revenue-related events like checkout_started, subscription_created, or payment_completed would provide immediate product insights when paired with the Stripe metadata. [CRITICAL]
  • No user identification: While user.id.toString() is correctly used as the distinct ID in Stripe metadata, posthog.identify() is never called to link the browser session to this user ID. [MEDIUM]

Other completed criteria

  • The posthog_person_distinct_id value uses a stable database user ID (not email or fabricated value) — correct choice for a distinct ID
  • Metadata is added to both the Checkout Session and subscription_data, ensuring subscriptions created via Checkout inherit the linkage

PostHog insights and events ❌

Filename PostHog events Description
lib/payments/stripe.ts None Only Stripe metadata added; no PostHog events captured. The posthog_person_distinct_id metadata enables PostHog revenue analytics to correlate Stripe data with PostHog persons, but no analytics events are instrumented.

Issues

  • No revenue analytics events: The wizard added Stripe metadata for person linkage but did not instrument any revenue-related events (e.g., checkout_initiated, subscription_activated, trial_started). These would provide immediate value for funnel analysis and revenue dashboards. [CRITICAL]
  • No event properties: With zero events, there are no enriched properties to evaluate. [MEDIUM]

Other completed criteria

  • No PII placed in Stripe metadata — user.id.toString() is a database integer ID, not an email or name
  • The metadata key posthog_person_distinct_id follows PostHog's expected naming convention for revenue analytics linkage

Reviewed by wizard workbench PR evaluator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants