Use google-analytics for read-only GA4 evidence tied to one property and date window. It preserves compatibility checks, metric definitions, sampling or thresholding warnings, source endpoint, and observation time.
Evidence example
Method date: 2026-08-26. Source: the traffic_acquisition manifest example and mocked GA4 response asserted in tests/unit/google-analytics.test.ts; this is a schema example, not live analytics or a customer result.
Input:
{"property_id":"123456789","start_date":"2026-07-01","end_date":"2026-07-31","row_limit":25}Output: Representative schema example; property and measured values are [redacted], while the channel and evidence fields follow the test fixture.
{"available":true,"property":"properties/[redacted]","query_dates":{"start_date":"2026-07-01","end_date":"2026-07-31"},"compatibility":{"checked":true,"incompatible_fields":[]},"rows":[{"session_default_channel_group":"Organic Search","sessions":"[redacted]"}],"source_endpoint":"properties/[redacted]:runReport"}Limitations: GA4 sampling, thresholding, attribution, consent, time zone, data retention, and event configuration affect interpretation; conversion_funnel compares aggregate event counts rather than user-level sequences, and content_roi is explicitly non-monetary.
Permissions: A read-only Google Analytics connector and explicit access to the chosen GA4 property are required; the tool never infers a property from another account relationship.
Cost/latency: These skills are listed as free in the manifest, but Google quotas and account terms apply; compatibility and report calls add variable provider/network latency with no stated SLA.
Safe next action: Verify the numeric property with property_summary, then run one bounded traffic_acquisition report and read its compatibility and data-quality warnings first.
See what a connector can access and the Google Analytics tool.