Weave Code
Client Id Bundle Laravel Package
setono/client-id-bundle
A Symfony bundle that generates and persists a unique client ID, helping identify anonymous visitors across requests for analytics, tracking, or personalization without requiring users to log in.
A Symfony bundle that provides a simple, reliable way to obtain a persistent client ID for anonymous visitors. It generates and stores a unique identifier (typically in a cookie) and exposes it through a convenient service, so you can recognize returning users without requiring authentication.
- Generates a unique, persistent client identifier
- Stores the ID in a cookie for future requests
- Injectable service for easy use anywhere
- Sensible defaults with configurable options
Frequently asked questions about Client Id Bundle
- Can I use setono/client-id-bundle in a Laravel application?
- No, not practically. It is a Symfony bundle that depends on Symfony's bundle registration, DI container, configuration tree, and event dispatcher, so a Laravel app would need a Symfony runtime or bridge just to boot it. That overhead is disproportionate for a feature this small. The recommended approach is to treat the repository as a design reference and reimplement the identifier logic in Laravel middleware plus a small service.
- What does setono/client-id-bundle actually do?
- It generates a unique client ID server-side for each visitor, persists it in a cookie, and exposes it through a Symfony service so your application can recognize returning clients across requests. It does not ship a full analytics pipeline, a consent management layer, or database storage by default. Its value is the pattern: a stable first-party identifier available to server-side code on every request.
- Which PHP and Symfony versions does setono/client-id-bundle support?
- You must check the composer.json constraints and tagged releases in the repository before relying on it, because the last release was around April 2024. Confirm the supported PHP range, Symfony major versions, and any PSR dependencies. If you are on a newer Symfony or PHP release, verify compatibility yourself rather than assuming it is maintained.
- Is setono/client-id-bundle safe to depend on in production?
- Code risk is low: it is MIT licensed and narrow in scope, so there is little surface area for bugs. Adoption and sustainability risk are high, with roughly one GitHub star, zero dependents, a single vendor maintainer, and sparse releases. For a Laravel stack the safer model is internal ownership of a ported implementation rather than an upstream dependency with no ecosystem validation.
- How do I implement the same client ID pattern in Laravel without the bundle?
- Register a middleware that reads a first-party cookie, and if it is missing or invalid, generates a UUIDv4 server-side and queues the cookie on the response. Bind an identifier service in the container that returns the resolved ID to controllers and jobs. The expected effort is roughly one to three engineering days including tests, consent gating, and cookie flag configuration.
- Does setono/client-id-bundle handle GDPR consent and cookie compliance for me?
- No. Server-side tracking still requires consent handling, first-party cookie disclosure, retention rules, and GDPR or CCPA review, and the bundle does not own that lifecycle. You must gate ID creation and persistence on consent state, define expiry and rotation, and document retention. Treat privacy and legal review as a prerequisite, not a follow-up task.
- How do I send a server-generated client ID to GA4 or a GTM server container?
- The bundle only produces the identifier, so wiring it to a destination is your responsibility. Read the ID from your Laravel service and pass it as the client_id parameter in GA4 Measurement Protocol calls, or forward it to your GTM server container as an event parameter. Keep these outbound calls off the critical render path and budget for added latency and egress at peak traffic.
- Are there Laravel alternatives to setono/client-id-bundle?
- There is no direct Laravel port of this bundle, so the usual choice is a small custom middleware and service, which is fast and fully under your control. You can pair that with a consent package to gate cookie creation and with your analytics vendor's server-side SDK for dispatch. Avoid framework bridges that pull Symfony components into Laravel purely to reuse a few lines of ID generation.
- How do I test client ID generation in a Laravel application?
- Write feature tests that assert the cookie is set on a first request and reused unchanged on the next, and assert that no cookie is issued when consent is denied. Cover the cases where cookies are blocked, where Laravel's cookie encryption is enabled, and where a reverse proxy or CDN caches responses. Also verify that your middleware does not break for API routes, queued jobs, or requests without an existing session.
- What cookie attributes should a first-party client ID cookie use?
- Use a first-party cookie with Secure and SameSite set appropriately for your flows, a bounded lifetime, and a clear name, and prefer server-side storage over the session if you need horizontal scale. HttpOnly is a tradeoff: it protects the value from script access but blocks client-side analytics tags from reading it, so decide based on whether the ID is consumed server-side only. Cookie-based persistence scales cheaply, while session or database storage adds write load per visitor.
Weaver
How can I help you explore Laravel packages today?