Weave Code
Google Analytics Server Side Tracking Bundle Laravel Package
setono/google-analytics-server-side-tracking-bundle
A Symfony bundle for sending Google Analytics events server-side via the Measurement Protocol, helping you capture purchases, conversions, and interactions from your backend even when client-side JavaScript tracking is blocked or unavailable.
A Symfony bundle that allows you to track your visitors server side instead of client side
Frequently asked questions about Google Analytics Server Side Tracking Bundle
- Can I use setono/google-analytics-server-side-tracking-bundle in a Laravel application?
- It is a Symfony bundle, not a Laravel package. Laravel does not consume Symfony bundles, and there is no service provider bridge or config translation layer. The realistic path is to extract the core client-ID, payload, and dispatch logic into a Laravel-native service. Budget for this as a port, not an install.
- What does this bundle actually do for server-side Google Analytics tracking?
- It sends Measurement Protocol hits to Google Analytics from your PHP backend, bypassing ad blockers and client-side script limitations. It integrates with Setono's server-side tracking library and is configured through Symfony services and bundle configuration. Typical uses are conversions, orders, and other server-side events that need reliable measurement.
- Does this bundle support GA4 Measurement Protocol?
- The provided notes do not confirm GA4 Measurement Protocol support. The last functional release before v0.3.9 was in 2022, predating the Universal Analytics sunset, so the bundle was likely designed around UA's Measurement Protocol. v0.3.9 adds user-agent filtering only and does not change the protocol question. Confirm GA4 endpoint and payload requirements, including measurement_id, api_secret, client_id, and events[], before adopting it.
- How do I install and configure it in Symfony?
- Install it with Composer and register the bundle in your Symfony kernel. Then configure the tracking service and bundle options for your Google Analytics properties. The provided context does not list exact configuration keys, so review the repository README and config tree before wiring production credentials.
- What Laravel versions does it support?
- There is no official Laravel version support because this is not a Laravel package. Laravel version compatibility is therefore not applicable in its current form. If you port the core logic, target the Laravel version used by your application and test the HTTP client, queue, and configuration integration yourself.
- Is it suitable for tracking purchases and conversions in production?
- Conceptually yes, but it is not a drop-in production solution for a Laravel app. The bundle can send server-side hits for purchases and conversions, but you must still handle consent, PII and IP handling, dispatch queuing, retries, dead-lettering, and client-ID persistence. v0.3.9 only partially addresses bot filtering through user-agent checks. Treat bot filtering as a small safeguard, not a substitute for real traffic-quality controls.
- How does the new user-agent filtering in v0.3.9 work?
- v0.3.9 adds an empty-user-agent filter and a configurable user-agent filter. These features help reduce bot and low-quality traffic before hits are sent. Filter correctness becomes your responsibility: aggressive rules can drop legitimate privacy-hardened browsers, while weak rules allow bot inflation. User-Agent is easily spoofed, so do not treat this as full bot detection.
- What are the GDPR and ePrivacy implications of server-side tracking?
- Sending user data from your servers to Google is a GDPR and ePrivacy decision, not a library choice. Server-side tracking shifts consent capture, IP handling, PII scrubbing, and bot filtering from the browser to your backend. v0.3.9 helps only with the bot-filtering part and does not add consent gating. You need explicit consent handling, data minimization, and a documented legal basis before sending production events.
- What alternatives should I consider for Laravel server-side Google Analytics tracking?
- For Laravel, prefer a Laravel-native GA4 Measurement Protocol client or a small custom service built on Laravel's HTTP client and queue. The functional core is small: assemble the payload, manage client IDs, dispatch the request, and handle retries. Use this Symfony bundle as a reference implementation and design input rather than a Composer dependency. If you need a package, choose one that explicitly supports GA4 and Laravel.
- Is this package actively maintained and safe to depend on?
- It is best described as alive but low-cadence, not actively maintained. v0.3.9 follows a gap of roughly two years, and the notes show a single-maintainer pattern with 4 stars, 0 dependents, and no clear PHP or Symfony version-bump or security-response commitment. Protocol obsolescence and low maintenance remain the dominant risks. For a Laravel codebase, port the useful core logic instead of depending on the bundle.
Weaver
How can I help you explore Laravel packages today?