Weave Code
Analytics Data Laravel Package
google/analytics-data
Idiomatic PHP client for Google Analytics Data, supporting REST and gRPC. Install via Composer, authenticate with Google Cloud, and query analytics reports with ready-made client classes.
At a glance
Frequently asked questions about Analytics Data
- How do I install google/analytics-data in a Laravel app?
- Run composer require google/analytics-data. There is no config file to publish or Artisan install command; after Composer resolves the package, instantiate Google\Analytics\Data\V1beta\Client\BetaAnalyticsDataClient in your own service or bind it in a Laravel service provider. Check that your runtime has the required PHP extensions, especially if you plan to use gRPC.
- Is google/analytics-data a Laravel package with a service provider or facade?
- No. It is a framework-agnostic Google Cloud PHP SDK with no service provider, facade, config file, queue integration, or caching layer. In Laravel you wrap it in your own adapter or reporting service and bind the client in a provider if you want dependency injection. That thin-adapter approach is usually cleaner than expecting Laravel-specific behavior from the SDK.
- Which Laravel versions and PHP versions does this package support?
- The package does not declare Laravel version constraints because it is not tied to Laravel. Compatibility is driven by its PHP requirement and by Composer resolving google/gax plus ext-grpc/ext-protobuf if you choose gRPC. Check the current composer.json and test on your app's PHP version before pinning it.
- How do I authenticate the Google Analytics Data client in Laravel?
- Authenticate with Google Cloud Application Default Credentials where possible, or pass an explicit service-account key configured through a secrets manager. Avoid committing long-lived service-account JSON to the repository or baking it into env vars on shared hosts. Scope the service account read-only to the specific GA4 properties and environments the app needs, and assign ownership for key rotation.
- Should I use REST or gRPC with google/analytics-data in Laravel?
- Use REST over HTTP/1.1 as the safe default in Laravel because ext-grpc and ext-protobuf are often missing from shared hosting and default Sail or Forge images. gRPC is available when those extensions are installed and may be useful for streaming-capable Google APIs, but the GA4 reporting calls you need are typically unary. Measure before adding extension and deployment complexity.
- How do I query GA4 reports such as runReport from Laravel?
- Instantiate BetaAnalyticsDataClient and call runReport, runPivotReport, or runRealtimeReport with a request built from Dimension, Metric, Filter, and OrderBy message types. The method returns typed response objects you can map into your own Laravel DTOs or arrays. Keep request construction in a dedicated class so report definitions are testable and reusable.
- How do I handle sampling, thresholding, and data freshness in production?
- GA4 can return sampled, thresholded, or data-limited results, so read ResponseMetaData such as sampling metadata and subjectToThresholding and surface it in logs or the UI. If you ignore that metadata, dashboards can quietly show wrong numbers. Also decide whether realtime data is required or nightly batch is sufficient, because quotas and freshness differ.
- How should I test GA4 reporting without hitting real analytics data?
- There is no GA4 sandbox, so use a dedicated non-production GA4 property for integration tests and keep live API calls out of the default unit test suite. Mock the client or your adapter for most tests, and run a small contract test against the test property in CI only when credentials are available. Assert that your wrapper exposes sampling and thresholding metadata correctly.
- What are the alternatives to google/analytics-data for Laravel GA4 reporting?
- spatie/laravel-analytics is a Laravel wrapper that already wraps this same GA4 Data API package and may be faster if you want a higher-level Laravel integration. This package is the lower-level official SDK, which is preferable when you need full control over runReport, runPivotReport, runRealtimeReport, filters, and response metadata. You can also call the REST API directly, but you lose the generated request and response types.
- Is google/analytics-data stable and how should I manage upgrades?
- It is explicitly beta with 0.x versioning, and the changelog has included breaking changes in minor releases plus generated-protobuf churn. Composer semver will not protect you, so pin an exact or tightly constrained version and commit the lockfile. Review release notes before upgrades and keep the integration behind your own adapter so SDK changes do not leak across the app.
Weaver
How can I help you explore Laravel packages today?