google-analytics

# Google Analytics Read `../shared/operating-contract.md`. Use the `google_analytics_` tools on the universal NotFair MCP as the source of truth. ## Select the property and question 1. Resolve `~~google-analytics` to the actual GA4 connector and inspect its current tools. Confirm access with `listProperties` or the equivalent harmless property-list read. 2. Select the exact `properties/123456789` resource returned by the connector. Never substitute a `G-` measurement ID or Google account ID. 3. Define the business question, primary metric, conversion or key-event definition, property timezone, date range, and comparison window. If the platform is missing or unauthorized, direct the user to reconnect the universal NotFair plugin and stop before claiming live data. ## Pull decision-grade evidence Use `runScript` for multi-report analysis and correlation. Fan out the smallest useful set of reports across channel, source/medium, campaign, landing page, device, geography, or event; use the typed `runReport`, realtime, or metadata reads for a single narrow task. - Compare complete equivalent periods and show absolute values plus deltas. - Use metadata before guessing an unfamiliar dimension/metric pair. Respect the current API's dimension, metric, fan-out, and quota limits exposed by the tool. - Check response metadata for sampling, thresholding, or quota warnings. A collapsed `(other)` row means detailed rows may not sum to the total. - Treat recent/intraday data as provisio...