The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
stack-auth-hosted-components	Ready	Preview, Comment	Mar 13, 2026 6:48pm
stack-backend	Ready	Preview, Comment	Mar 13, 2026 6:48pm
stack-dashboard	Ready	Preview, Comment	Mar 13, 2026 6:48pm
stack-demo	Ready	Preview, Comment	Mar 13, 2026 6:48pm
stack-docs	Building	Preview, Comment	Mar 13, 2026 6:48pm

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Greptile Summary

This PR adds a new analytics documentation page, enriches the payments docs with Quick Setup and Core Concepts sections, and removes the projectId === "internal" guard in client-app-impl.ts so that the EventTracker (client-side $page-view / $click capture) runs for all non-internal projects — not just Stack's own internal project.

Key changes:

• New analytics.mdx: Covers Tables, Queries, and Session Replays features with a flowchart diagram, SDK code snippet for replay recording, and best-practice guidance.
• Updated payments.mdx: Adds a Quick Setup checklist, a Mermaid sequence diagram for the purchase flow, Core Concepts definitions, and new Product Lines / Payouts / Settings dashboard sections.
• meta.json / overview.mdx: Registers the new analytics guide in the sidebar and the overview AppGrid.
• client-app-impl.ts: Drops the if (... && this.projectId === "internal") guard, meaning EventTracker (DOM listeners + history patching) is now initialised for every StackClientApp running in a browser. The server still enforces ANALYTICS_NOT_ENABLED for projects that haven't opted in, but the client is unaware of this and will produce console.warn noise and waste network requests for those projects.

Confidence Score: 3/5

• Safe to merge for the documentation half; the SDK change is functional but will cause console warnings and unnecessary network traffic for any project that hasn't enabled the Analytics app.
• The docs additions are high quality and accurate. The SDK change achieves its stated goal (enabling events for non-internal projects), but the unconditional EventTracker initialization introduces observable side-effects — repeated console.warn messages and wasted HTTP calls — for every Stack Auth project that isn't using analytics. No data is leaked (server rejects events), but the developer experience degrades without a mitigation path (opt-out flag or silent failure for ANALYTICS_NOT_ENABLED).
• packages/template/src/lib/stack-app/apps/implementations/client-app-impl.ts

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant Browser as Browser (all projects)
    participant ET as EventTracker
    participant Server as Stack Auth Server

    Browser->>ET: start() — attach click/popstate/pagehide listeners,<br/>monkey-patch history.pushState/replaceState
    loop Every 10s (_tick)
        ET->>Server: getAccessToken()
        Server-->>ET: token (or null)
        alt User is authenticated AND events buffered
            ET->>Server: POST /analytics/events/batch
            alt Analytics app enabled
                Server-->>ET: 200 OK — events stored
            else Analytics app disabled
                Server-->>ET: 400 ANALYTICS_NOT_ENABLED
                ET-->>Browser: console.warn("EventTracker flush failed")
            end
        end
    end

_{Last reviewed commit: ee0277a}