Weave Code
External Tracking Bundle Laravel Package
geekyhouse/external-tracking-bundle
A Symfony bundle for integrating external tracking and analytics services into your application. It provides configuration and service wiring for third-party tracking providers, making it easy to drop into existing Symfony projects with minimal setup.
Manager for trackers of external entities
Frequently asked questions about External Tracking Bundle
- Is geekyhouse/external-tracking-bundle a Laravel package or a Symfony bundle?
- It is a Symfony2 bundle, not a Laravel package. It depends on a Bundle class, a DI extension, and kernel.response listeners, none of which exist in Laravel. There is no bundle autodiscovery and no equivalent kernel event, so using it in Laravel is a port rather than an integration.
- Can I install this bundle in a Laravel 10 or Laravel 11 app with Composer?
- Unlikely. A Symfony2-era bundle typically pins symfony/dependency-injection and symfony/event-dispatcher at 2.x or 3.x and PHP at 5.x through 7.0, while Laravel 10 and 11 run on Symfony 6 and 7. Expect composer require to fail or to force ignore-platform-reqs hacks that pin your entire Symfony component tree. Check the composer.json constraints before scheduling any work.
- What does this package actually do, and how are tracking scripts injected into pages?
- It provides configuration and service wiring for third-party tracking and analytics providers, injecting config-declared tracking scripts or pixels into rendered pages. Injection is most likely done through a response listener or a Twig extension. Confirm in the source whether it emits client-side markup only or whether anything executes server-side.
- How do I add third-party tracking pixels to a Laravel app without this package?
- Build it directly: a config/tracking.php file with one array per tracker covering id, provider, position, enabled, and consent_category, plus a TrackingServiceProvider, a Blade component or directive for the markup, and middleware only if you need server-side decisioning. That is roughly 150 to 250 lines and avoids the Composer conflicts and licensing problems entirely.
- What license is this bundle released under, and can I use it commercially?
- GitHub reports the license as NOASSERTION, meaning it could not identify a recognized license. There is no clear grant to copy, modify, or redistribute the code, which makes this a legal review for a commercial product rather than an engineering decision. Check whether the repository actually contains a license file before assuming anything.
- Is this tracking bundle still maintained, and is it safe to run in production?
- No. Symfony2 reached end of life in November 2018, so there are no upstream fixes and no security disclosure path. The project has around two stars and zero dependents, with no evidence of production use on a modern stack. Treat it as a reference specification, not a dependency.
- Does the bundle handle GDPR or cookie consent before firing trackers?
- Nothing in the description suggests consent management hooks, so it likely assumes unconditional firing. Under GDPR you need consent gating that does not exist in the original bundle. Add it yourself rather than porting it: a consent_category per tracker plus a check before any markup is emitted.
- Which tracking providers does it support, and are they config-declared or hardcoded?
- The description does not enumerate providers, so a source audit is required to inventory tracker types, injection points for head, body and footer, and the config schema. Determine whether providers are config-declared or hardcoded, since that decides whether a rewrite from spec is cheap. Also check for any per-provider conditional logic.
- Should I fork and port this bundle or rewrite external tracking from scratch in Laravel?
- Rewriting in-house is usually better: the code is small and stateless, so there is no data or state to migrate. Fork-and-port only makes sense if the tracker support matrix turns out to be non-trivial with many per-provider quirks, and even then legal must clear the NOASSERTION license first. Either way you must re-validate output markup against each vendor's current snippet.
- How do I test that tracking markup renders correctly in Laravel?
- Write feature tests that assert the exact emitted markup per provider, and add tests asserting nothing is emitted when a tracker is disabled or consent is absent. Because the package is stateless, config in and markup out, these tests are straightforward in Laravel. Run them against each vendor's current snippet so tracking does not silently break.
Weaver
How can I help you explore Laravel packages today?