A transparent view of what this integration exposes now, what it costs, which plan it needs, and where a human approval is required.
Updated 1 August 2026 from the public registry.
These rows are projected from the same registry used by the API, workflows, agent, and MCP surfaces. Private or disabled operations cannot appear here.
List common Google Analytics 4 metrics and dimensions for ga4_get_report. Prefer keyEvents over the legacy conversions metric and sessionDefaultChannelGroup for reports built from session metrics.
ga4_fieldsFetch Google Analytics 4 metrics (e.g. activeUsers, sessions, conversions) optionally broken down by dimensions, over a date range.
ga4_get_reportList the Google Analytics 4 properties this connection can access. Use the returned property_id with ga4_get_report.
ga4_select_accountsExplore the complete executable definition before connecting a workspace.
Collect separate GA4 campaign and landing-page views for the current period and produce a cautious investigation brief without pretending the two reports form a row-level causal join.
ga4_select_accountsutil_date_rangega4_get_reportga4_get_reportai_analyze_datareport_renderRun three bounded GA4 acquisition breakdowns to review campaign naming, source and medium coverage, engagement, key events, and revenue. The final brief distinguishes tracking-hygiene findings from performance observations and does not assign a synthetic campaign quality score.
ga4_select_accountsutil_date_rangega4_get_reportai_analyze_datareport_renderReview current-period GA4 channel-group rows for observed traffic, engagement, key-event, and revenue patterns, then produce a measurement-safe quality brief without assigning channel causation.
ga4_select_accountsutil_date_rangega4_get_reportai_analyze_datareport_renderReview current-period GA4 country aggregates for observed traffic, engagement, key events, and revenue signals, then create localization questions without treating country as a causal or market-fit conclusion.
ga4_select_accountsutil_date_rangega4_get_reportai_analyze_datareport_renderCompare the latest seven complete days with the preceding seven days by GA4 session default channel group, then produce a concise, source-grounded brief of material traffic, engagement, conversion, and revenue changes. The workflow reports observed movement without claiming attribution or causes the data cannot establish.
ga4_select_accountsga4_get_reportga4_get_reportconditionai_analyze_datareport_renderReview current-period GA4 device-category aggregates for sessions, engagement, key events, and revenue, then create a responsive and instrumentation follow-up brief without device causation claims.
ga4_select_accountsutil_date_rangega4_get_reportai_analyze_datareport_renderReview current-period GA4 event-name aggregates for volume, engagement, key-event, and revenue signals, then identify event taxonomy and instrumentation checks without certifying tracking quality.
ga4_select_accountsutil_date_rangega4_get_reportai_analyze_datareport_renderRead daily GA4 engagement signals across the last 28 complete days and turn them into a compact trend brief. The analysis separates sustained movement from isolated daily variation, reports exact observed values, and avoids unsupported explanations for changes.
ga4_select_accountsutil_date_rangega4_get_reportai_analyze_datareport_renderReview a bounded set of GA4 landing-page rows for high-traffic pages with weak engagement or conversion signals, then create an investigation brief. Results are diagnostic candidates from observed analytics data, not proof that a page caused lost key events or revenue.
ga4_select_accountsutil_date_rangega4_get_reportconditionai_analyze_datareport_renderReview a bounded GA4 landing-page report for observed traffic, engagement, key-event, and revenue signals, then produce a measurement-safe page investigation brief without assigning lost value or causal blame.
ga4_select_accountsutil_date_rangega4_get_reportai_analyze_datareport_renderReview current-period GA4 page-path rows for sessions, key events, and recorded revenue, then produce a verification brief that avoids assigning revenue causation to pages.
ga4_select_accountsutil_date_rangega4_get_reportai_analyze_datareport_renderReview current-period GA4 source and medium rows for naming hygiene, engagement, key-event, and revenue signals, keeping observed analytics separate from attribution claims.
ga4_select_accountsutil_date_rangega4_get_reportai_analyze_datareport_renderPlace GA4 Organic Search rows beside daily Search Console performance for the same 28-day window and produce an executive scorecard. The workflow highlights directional patterns while keeping platform definitions separate and refusing to present correlation as attribution.
ga4_select_accountsgsc_select_accountsutil_date_rangega4_get_reportgsc_get_reportai_analyze_datareport_renderCompare bounded GA4 landing-page traffic rows with Search Console page visibility for the same period, then surface page-level mismatches worth checking. The workflow explicitly treats GA4 sessions and Search Console clicks as different measurements and does not manufacture a cross-platform attribution model.
ga4_select_accountsgsc_select_accountsutil_date_rangega4_get_reportgsc_get_reportconditionconditionai_analyze_datareport_renderCollect separate GA4 channel, source-medium, and campaign views plus a bounded Search Console query-page view for the last seven complete days. The final report summarizes acquisition mix and search demand while keeping channel performance, search visibility, and attribution claims distinct.
ga4_select_accountsgsc_select_accountsutil_date_rangega4_get_reportga4_get_reportga4_get_reportgsc_get_reportai_analyze_datareport_renderCompare the operating model or open a workspace and start with a visible requirement check.