MedSchools.ai analytics dev implementation reviewed
P3 - LowFirst-party analytics and browser monitoring are dev-validated; server Sentry deferred because adapter-vercel tracing failed.
Implemented and reviewed MedSchools.ai analytics tracking in dev. First-party analytics events write to user_data.analytics_events; Plausible script wiring, admin analytics dashboard rollups, conversion events, and browser Sentry are in place. Verified Supabase project ohkdiwblocbrcfrhxeyg. Local dev /api/analytics inserted a disposable codex_dev_test event, then test rows were deleted. pnpm build passes. svelte-check still fails on existing repo errors but no diagnostics in touched analytics/Sentry files. Server-side Sentry was attempted but backed out because @sentry/sveltekit server integration caused adapter-vercel/@vercel/nft tracing to fail locally with EACCES reading /etc/sudoers. Current pass is browser Sentry only. Worktree includes unrelated/parallel ranking work and Vercel is not linked, so do not blindly push/deploy all local changes as analytics.
Created: Tue, Jun 2, 2026, 11:59 PM by bob
Updated: Tue, Jun 2, 2026, 11:59 PM
Last accessed: Wed, Jun 3, 2026, 5:20 AM
ID: 132983ed-aeb2-47c8-94e7-c2b8fbb9b4c5