PR Custody

fix(analytics): explicit GA4 page_view on SPA navigations

@qdonohuechecks n/achecks…fix/ga4-spa-pageview-tracking → master2 files · +16 −0updated 1mo ago

▸Description · 1 noise

Problem: Blog pages (and other SPA-navigated pages) weren't being tracked by GA4. The @next/third-parties/google GoogleAnalytics component relies on GA4 enhanced measurement to detect client-side navigations, which misses Next.js App Router soft navigations.
Fix: Added trackGooglePageView() to the existing TrackPageView component so every page fires an explicit GA4 page_view event alongside the PostHog pageview — no per-page changes needed since every page already uses <TrackPageView>.
Scope: 2 files changed — src/lib/gtag.ts (new helper) and src/components/analytics/track-pageview.tsx (call it).

Deploy preview and open browser devtools Network tab
Navigate to /blog via client-side link — confirm a page_view event fires to GA4 (collect? request to google-analytics.com)
Navigate to an individual blog post — confirm another page_view fires
Hard-refresh a blog post directly — confirm page_view fires on initial load
Verify GA4 Realtime report shows blog page hits

🤖 Generated with Claude Code

▸ 1 bot/status comment hidden

@vercel[bot]1mo ago

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

Project	Deployment	Actions	Updated (UTC)
landing-new	Ready	Preview, Comment	Apr 20, 2026 8:42pm

loading diff…