AnalyticsService: page_view double-counted when apps also call trackPageView

Problem

AnalyticsService.initializeGtag (packages/utils/src/AnalyticsService.ts, line ~175) calls gtag('config', tagId) without send_page_view: false, so gtag emits its automatic page_view on load. Apps that also track route changes via trackPageView (Role Manager and RWA Wizard both mount a TrackedRoute component) therefore send two page_view events on first landing — inflating page-view counts in GA4 by one per session. UI Builder is unaffected because it never calls trackPageView.

Surfaced while wiring GA4 custom dimensions for the analytics pipeline (OpenZeppelin/rwa-wizard#63).

Suggested fix

Either:

• Add a sendPageView option (default true to preserve current behaviour) to AnalyticsService.initialize / AnalyticsProvider, passed through as gtag('config', tagId, { send_page_view }), so apps with route tracking can opt out; or
• Flip the default to send_page_view: false and document that apps must call trackPageView (breaking for apps relying on the automatic hit).

Consumers to update after release: role-manager and rwa-wizard TrackedRoute usages.

Start in packages/utils/src/AnalyticsService.ts at AnalyticsService.initializeGtag around line 175, then trace initialize, AnalyticsProvider, and trackPageView. Inspect the TrackedRoute usages in Role Manager and RWA Wizard, while noting that UI Builder does not call trackPageView. Done means the chosen behavior is supported and those route-tracking apps no longer send a duplicate first-landing page_view without breaking existing automatic tracking.