project creatortrack analytics architecture split 20260715T154750

name: CreatorTrack analytics: operator (PostHog) vs creator-facing (native) split, unify via shared dimensional model description: Decision: PostHog stays operator-only analytics; native engine is creator-facing; Links/Social/Campaigns stay separate apps but conform to a shared dimensional model + metrics registry so a rollup dashboard is possible. type: project

Justin was uneasy that CreatorTrack has analytics scattered across the Links app, a Social Analytics app, and Campaigns, with no coherent model. Resolved architecture:

Operator layer (PostHog): internal product analytics for Justin only (signups, activation, retention, feature usage). No native-analytics ambitions here; don't try to make PostHog multi-tenant/creator-facing.
Creator-facing layer (native engine): what each creator sees about their own business (page views, clicks, funnels, sales, journeys). This is a paid-tier feature, not deferrable, and its capture pipeline must be built broadly from day one since the event store is append-only (cannot backfill).
Links, Social, Campaigns stay as separate apps (they measure genuinely different channel shapes: owned web / external platform APIs / email), but must conform to a shared dimensional model (creator/profile/workspace, time, channel, campaign), a common metrics registry, and shared chart conventions (extend the existing Finance chart-convention pattern).
A top-level Command Center dashboard rolls up headline metrics from each source and links into each app's deep-dive lens, giving the unified view Justin wants without merging storage.
For the ~3-month launch: build capture fully + core dashboards now; defer A/B funnel analytics, server CAPI, cross-channel attribution, ad-report imports (Pro/Scale upsells) to post-launch.

Why: Justin explicitly asked to make sure the analytics build makes sense as a business, given the existing app sprawl, and wants max capture now with the option to pare down later. How to apply: when building or extending CreatorTrack analytics (native engine, Links, Social, Campaigns), require conformance to the shared dimensional model/metrics registry before shipping a new metric or app, rather than bolting on another isolated silo. See [[creatortrack_public_platform_overhaul_scoping]] for the related phasing decisions.

[auto-memory session 577603bc-d3a9-4b19-bb8e-6db80243b054, confidence 0.75, mode staged]