- Is gordalina/mixpanel-bundle compatible with Laravel?
- No, gordalina/mixpanel-bundle is a Symfony bundle rather than a Laravel package. It depends on Symfony kernel bundle discovery, a DependencyInjection extension, and container compilation, none of which Laravel runs. Composer may install it into a Laravel app, but it will not wire up a usable Mixpanel service.
- Can I install gordalina/mixpanel-bundle in a Laravel app?
- You can require it with Composer, but installation alone gives you no working Mixpanel integration in Laravel. The bundle expects Symfony bundle registration and configuration merging through Symfony's container. For Laravel you should bind the Mixpanel client yourself in a service provider or use the Mixpanel PHP SDK directly.
- What Laravel versions does gordalina/mixpanel-bundle support?
- None are declared, because the package targets Symfony rather than Laravel. Release 7.0.0 adds Symfony 8 support and pins Symfony 7 to ^7.4. It does not ship Laravel service providers, facades, or Laravel version constraints.
- What does gordalina/mixpanel-bundle actually do?
- It integrates the Mixpanel PHP library into Symfony applications and exposes a configured Mixpanel client as a dependency-injection service. You set the Mixpanel project token through bundle configuration and inject the tracker into controllers or services to track events and user profiles. It is a lightweight wrapper, not a standalone analytics SDK.
- Can I track Mixpanel events and identify users with this bundle in Laravel?
- Not through the bundle's Symfony wiring. You can still track events and identify users in Laravel by using the underlying Mixpanel PHP SDK or Mixpanel's HTTP API and wrapping client creation in a Laravel service provider. Port the bundle's configuration shape only if it saves you design time.
- What changed in gordalina/mixpanel-bundle 7.0.0?
- Version 7.0.0 is Symfony ecosystem housekeeping: Symfony 8 support, Symfony 7 pinned to ^7.4, Doctrine annotation reading removed, the Annotation namespace renamed to Attribute, the bundled Rector set removed, and symfony/yaml made an explicit dependency. It does not change Mixpanel event semantics, endpoints, payloads, transport, retries, deduplication, or PII handling. For Laravel teams it is functionally a non-event.
- Should I use gordalina/mixpanel-bundle or mixpanel/mixpanel-php directly?
- Prefer mixpanel/mixpanel-php or the raw Mixpanel HTTP API directly in Laravel. The bundle's value is Symfony container integration, which Laravel cannot reuse, leaving only its configuration schema and thin service wiring as reference material. Choose the bundle only when you are building a Symfony application.
- Is gordalina/mixpanel-bundle actively maintained and production-ready?
- Maintenance is visible through the coordinated 7.0.0 Symfony migration, but adoption is very low at around 14 stars and zero dependents. That means little production signal and no community to surface regressions. Verify freshness on Packagist and in commit history because the release notes cited here lack a publication date.
- How do I configure the Mixpanel project token in Laravel if I port this bundle?
- Put the Mixpanel project token in an environment variable and expose it through Laravel configuration, then bind a singleton Mixpanel client in a service provider. The bundle's Symfony configuration and attribute-based style do not transfer directly, so translate rather than copy it. Inject the client into controllers, jobs, or listeners where tracking is needed.
- Does gordalina/mixpanel-bundle work with Symfony autowiring?
- Yes, in Symfony it exposes the Mixpanel client as a dependency-injection service that can be autowired into controllers and services. That autowiring relies on Symfony's container compilation. Laravel's container does not discover or compile Symfony bundles, so the same autowiring behavior does not carry over.