Referable Bundle Laravel Package

Product Decisions This Supports

• First-touch acquisition attribution: Capturing referer values on the first request improves reliability for landing-page attribution, campaign/source tracking, and funnel analysis where the initial request is often the only chance to record the external referrer.
• Laravel-native integration: The RefererManager autowiring service lowers implementation cost for teams already using Laravel’s service container and dependency injection.
• Build vs. buy: This package is most relevant when the product needs lightweight referer capture rather than a full analytics, CDP, or attribution platform. It supports a “buy/integrate small package, build the product logic around it” decision.
• Use cases: Marketing attribution, referral-source segmentation, personalized landing experiences, fraud/abuse signals, partner/referral reporting, and internal analytics enrichment.
• Roadmap consideration: v2.0.0 is a compatibility/quality release rather than a major product feature release. It reduces risk for first-request attribution and service integration, but it also narrows supported legacy Symfony versions, which matters for platform modernization planning.

When to Consider This Package

• Consider it when the product needs to capture referer data at the earliest possible point in a Laravel request lifecycle, especially for first-touch attribution or landing-page source detection.
• Consider it when engineering wants a Laravel-friendly, autowirable service instead of custom request-level referer parsing.
• Consider it when the stack is on supported Symfony versions and can absorb the v2.0.0 removal of Symfony 4.4 support.
• Consider it when the team needs a focused referer utility, not a complete attribution suite. Pair it with analytics, consent management, and data-governance tooling as needed.
• Look elsewhere if the organization requires long-term support for Symfony 4.4, needs advanced multi-touch attribution, requires server-side enrichment from many sources, or has strict privacy/consent requirements that a lightweight referer package does not address.
• Treat v2.0.0 as a minor integration risk for legacy stacks: the dropped Symfony 4.4 support and Doctrine LifecycleEventArgs namespace update should be verified against existing dependencies before rollout.

How to Pitch It (Stakeholders)

Executive summary: This package supports reliable first-request referer capture and Laravel-native service integration, which can improve acquisition attribution and reduce custom plumbing for marketing and product analytics. v2.0.0 strengthens first-request behavior and service availability but drops Symfony 4.4 support, so adoption should be gated on stack compatibility. It is a low-level utility, not a replacement for a full analytics or consent platform.

For engineering: The new RefererManager autowiring support and first-request referer availability simplify integration in Laravel applications. Confirm Doctrine event-argument namespace compatibility and verify no services still depend on Symfony 4.4 before upgrading.

For product/marketing: This helps answer “where did this user first come from?” more reliably at the initial request, enabling better source reporting, referral segmentation, and landing-page personalization. It should be paired with clear consent and privacy controls.