Connection flow
OAuth 2.0 with provider account discovery. Customers choose from accounts returned by the provider rather than entering an unverified inventory endpoint.
Google Analytics connector for governed marketing data.
Use curated Google Analytics 4 acquisition, page, event, ecommerce, and user-window reports with an explicit web-analytics semantic contract. This page is generated from the same customer catalog, source schemas, live-fetch classifier, semantic contracts, and export registry used by the product.
5Available, live-fetch-ready reports
925Verified report-field definitions
SemanticPublished semantic tier
Setup and fit
What the Google Analytics connection proves.
Registration alone is not enough for this page. The connector must be customer-discoverable, OAuth based, connectable at runtime, and backed by non-placeholder fetch implementations.
Best for
Growth and ecommerce teams that need governed GA4 reporting templates rather than an open-ended analytics-query builder.
Semantic coverage
4 declared base entities across the published reports: Item, Page, Session, Transaction.
ConnectableConnection provider and at least one live fetcher are registered.
5 availableHidden, planned, deferred, and catalog-unlisted reports are excluded.
1 eligible datasetEvery listed report passes the query and export registry contract checks; customer rollout is still gated.
Report contract
Supported Google Analytics reports, entities, and grains.
The grain column is the declared uniqueness contract for a report row. A semantic tier includes a base entity and full semantic contract; a basic tier defines a safe report grain and common mappings without promising complete relationships.
| Report | What it contains | Tier / entity | Declared grain | Field contract |
|---|---|---|---|---|
Acquisition and eventsacquisition_traffic |
Traffic acquisition, campaign, page, and event performance. | Semantic Session |
web_property_id, report_type, date, date_window, dimension_valuesTime key: date |
185 schema fields 51 report fields export-visible |
Ecommerce itemsecommerce_items |
Product and item revenue and funnel performance. | Semantic Item |
web_property_id, report_type, date, date_window, dimension_valuesTime key: date |
185 schema fields 51 report fields export-visible |
Ecommerce ordersecommerce_orders |
Order and revenue performance by traffic source and campaign. | Semantic Transaction |
web_property_id, report_type, date, date_window, dimension_valuesTime key: date |
185 schema fields 51 report fields export-visible |
Pages and eventspages_events |
Content, website behavior, and event tracking. | Semantic Page |
web_property_id, report_type, date, date_window, dimension_valuesTime key: date |
185 schema fields 51 report fields export-visible |
Users by windowusers_by_window |
Semi-additive user counts by selected reporting window. | Semantic Session |
web_property_id, report_type, date, date_window, dimension_valuesTime key: date |
185 schema fields 51 report fields export-visible |
Export contract
Modeled outputs, with blocked fields kept blocked.
Export eligibility is not inferred from a connector page. The generator resolves each report through the query catalog and requires a registry contract with allowlisted default columns and modes. Eligibility does not mean a destination or production export is enabled for a customer.
web_analytics
Public dataset contract covering 5 supported reports on this connector.
Eligibility255 report-field definitions are marked export-visible; 5 default columns pass the dataset registry policy.
ModesSource Replication, Source Replication With Semantic Views are contract-eligible, subject to destination support and rollout gates.
ReportsAcquisition and events, Ecommerce items, Ecommerce orders, Pages and events, Users by window
Truthful limitations
What this page does not promise.
A static contract page documents implemented product boundaries. It is not evidence that a specific tenant credential has permission to every provider account, that an upstream API is currently healthy, or that every provider field is publishable.
Provider-specific boundary
This page covers the five customer-visible curated GA4 templates. Attribution, MMM outcome, and BigQuery event-export contracts are not included here unless separately exposed through the customer catalog.
Export rollout remains gated
Registry eligibility is not customer enablement. Destination support, deployment rollout, plan entitlement, tenant and account scope, date behavior, selected-field validation, PII policies, provider-native restrictions, and raw-payload blocks still apply.
Runtime evidence, not a blanket SLA
“Live-fetch ready” means the implementation is not a detected placeholder. It does not replace provider permissions, production smoke evidence, upstream API limits, or plan entitlement checks.
Related diagnostics
Use the contract to explain the numbers.
Connector availability is only the first question. These guides show how definitions, identifiers, attribution, time, currency, and report grain can still create different answers.
Shopify vs. GA4 revenue
Reconcile transaction IDs, tracking coverage, revenue components, dates, scope, and currency.
Why marketing numbers disagree
Use the interactive decision tree to classify identity, definition, time, currency, attribution, and aggregation gaps.
Connector FAQ
Common Google Analytics connector questions.
These answers use the same verified contract data as the report table and the page’s structured data.
What Google Analytics data can Metric Hive load?
Metric Hive exposes 5 reviewed, live-fetch-ready Google Analytics reports. The exact reports, entities, grains, fields, and semantic tiers are listed on this page.
Does the Google Analytics connector use a semantic layer?
The published reports use the semantic tier. Semantic reports declare a base entity and complete semantic contract; basic reports declare a safe grain and common mappings without claiming complete relationship metadata.
Can I export modeled Google Analytics data?
Each report on this page passes the query and export registry eligibility checks. That does not prove a destination is enabled for a customer: plan entitlement, destination support, rollout gates, tenant scope, and field policies still apply.
Inspect the contract, then connect your account.
Browse the full connector catalog, review canonical semantic definitions, or check pricing before starting an OAuth connection. Provider setup documentation