Discover accessible GA4 properties
The Admin API lists account summaries so an operator can select the property ID shared with the service account.
Evidence: Verified in the Routeless GA4 collection script.
Verified integrations · Google data and advertising
Google Analytics 4 API integration
Routeless connects GA4 reporting data to internal analysis and public case-study workflows. The verified implementation uses the Data API for channel, source, user, session, and event reports and the Admin API to discover accessible properties. It excludes partial months from comparisons and does not treat GA4 sessions as interchangeable with Search Console clicks.
Evidence verified 2026-09-28 · Vendor facts reviewed 2026-09-28
Evidence boundary
What the implementation proves.
Routeless contains GA4 Data API and Admin API collection, client-side event contracts, frozen permissioned artifacts, coverage checks, and case-study rendering for VisaMind and Analytics Engineering.
The evidence supports GA4 collection and reporting. It does not establish perfect attribution, consent compliance for an unrelated client setup, or access to properties that have not been shared.
Verified capabilities
- GA4 Data API runReport queries
- GA4 Admin API account and property discovery
- Channel, source, session, user, and key-event reporting
- Dated case-study artifacts and partial-period controls
Implemented workflows
Workflow 01
Workflow 02
Workflow 03
How data moves through the integration.
Build channel and source reports
Data API runReport requests group sessions and users by channel or referrer over a defined period, including an explicit view of traffic classified as AI Assistant.
Evidence: Verified in the Routeless case-study data collector and frozen GA4 artifacts.
Publish comparable case-study periods
Collected monthly rows are reduced to full months before comparisons. Key-event reporting publishes users where repeat events would otherwise overstate the number of people who converted.
Evidence: Verified in the GA4 collector and case-study rendering model.
Authentication and operations
Access, secrets, and recovery are part of the build.
Authentication model
The reporting script uses a Google service account with the analytics.readonly scope and requires Viewer access to the GA4 property. Browser measurement uses a public measurement ID, which is not an API secret.
Credential handling
The service-account file remains outside the application repository and receives read-only property access. The collection tool reads the key path from server or operator configuration. Public GA4 measurement IDs are kept separate from private API credentials.
Failure behavior
Missing credentials, unavailable client libraries, inaccessible properties, and non-success API responses stop collection with an explicit message. A property with no report rows fails the coverage check instead of generating an empty success artifact.
Vendor and implementation constraints
Limits that affect the scope.
- The Data API and Admin API serve different jobsThe Data API reads report data. The Admin API manages or discovers configuration. Access to one API surface does not imply permission to modify the other.
- GA4 attribution follows property settingsThe API respects the property's reporting identity and configured dimensions. A custom report cannot recover identity or attribution data the property did not collect.
- GA4 and Search Console use different measurementsA Search Console click and a GA4 session are produced by different systems and should not be presented as equal counts.
Related production proof
Projects behind the claim.
VisaMind
Permissioned GA4 channel and conversion measurements used with search evidence.
Analytics Engineering
Permissioned GA4 product and acquisition measurements.
Google Analytics 4 integration FAQ
Questions that change the implementation.
Yes. Routeless has implemented Data API reports for channels, sources, sessions, users, and selected events, with dated artifacts and full-period checks suitable for internal reporting or permissioned case studies.
The Data API returns reporting data such as sessions, users, events, and dimensions. The Admin API exposes property and configuration resources. Reporting access and configuration access should be scoped separately.
No. The API reports what the property collected and retained. A new event, dimension, consent setting, or property cannot recreate data that was never recorded.
The systems observe different events and apply different processing. One search click can fail to start an analytics session, and one user can create multiple sessions. Comparisons need aligned dates and an explanation of both measures.
Official sources
Vendor facts checked against current documentation.
- Google Analytics Data API overview Reviewed 2026-09-28
- Google Analytics Data API quotas Reviewed 2026-09-28
- Google Analytics Admin API overview Reviewed 2026-09-28
Google Analytics 4 official site. The Google Analytics 4 name and logo belong to their owner. Inclusion documents Routeless implementation experience and does not imply partnership, certification, or endorsement.
Scope a Google Analytics 4 integration.
Share the account access, records, expected events, and the workflow that must recover when delivery fails.