Weave Code
Laravel Referral Rewriter Tag Laravel Package
the-3labs-team/laravel-referral-rewriter-tag
A Laravel package for rewriting referral tags on incoming requests, helping standardize referral attribution and preserve campaign tracking across redirects. Lightweight, configurable, and easy to drop into existing Laravel applications.
🏷️ A simple solution for rewrite shop tags with your own tags and subtags
Frequently asked questions about Laravel Referral Rewriter Tag
- What does laravel-referral-rewriter-tag do?
- It is a Laravel package for rewriting referral tags on incoming requests so referral attribution can be standardized and campaign tracking can be preserved across redirects. It is config-driven and intended to be lightweight and easy to drop into existing Laravel applications. The v1.0.6 release also adds an optional instantgaming.subtag configuration key.
- How do I install laravel-referral-rewriter-tag with Composer?
- Install it as a Composer dependency in your Laravel application using composer require the-3labs-team/laravel-referral-rewriter-tag. The package is expected to integrate through standard Laravel package discovery and configuration. After installation, publish or merge the package config and clear the config cache before testing referral output.
- Does this package support Laravel 12 and PHP 8.2?
- The maintenance baseline described for v1.0.6 targets Laravel 12 through Orchestra Testbench 10 and requires PHP 8.2 or newer for local development and CI. Before production rollout, confirm the package's declared Composer constraints against your application's PHP and Laravel versions. This is especially important if your app runs on a different PHP minor version or an older Laravel release.
- How do I configure instantgaming.subtag?
- Publish or merge the package configuration file config/referral-rewriter-tag.php into your application. Set the instantgaming.subtag value to the subtag you want applied to Instant Gaming referral attribution. Then clear and rebuild the Laravel config cache and verify the rewritten referral output in staging.
- Does laravel-referral-rewriter-tag auto-register its service provider?
- The package follows standard Laravel package conventions, so it is expected to work with Laravel package discovery rather than requiring manual provider registration. Check the installed package's composer.json extra.laravel configuration to confirm the provider and any aliases. If discovery is disabled in your application, register the provider manually.
- Is upgrading from v1.0.5 to v1.0.6 low risk?
- Yes, v1.0.6 is described as a maintenance and stabilization release with an optional instantgaming.subtag config addition, so the consuming-application risk is low. No database migration is indicated. Refresh dependencies with composer update, add the optional config key if needed, and validate existing referral behavior before deploying.
- What changed in laravel-referral-rewriter-tag v1.0.6?
- v1.0.6 focuses on maintenance rather than new runtime capability. It adds an optional instantgaming.subtag configuration key and updates the development and CI toolchain, including Testbench 10, Pest 3, Larastan 3, PHPStan 2, Rector 2, and Collision 8. The standalone phpstan.yml workflow was removed and static analysis now runs inside run-tests.yml.
- Do I need to publish the referral rewriter config file?
- You need to make the package configuration available to your application, typically by publishing the package config or merging config/referral-rewriter-tag.php into an existing configuration file. Set the instantgaming.subtag value if you need Instant Gaming attribution rewriting. Clear the config cache after changing the file so Laravel reads the new values.
- Does laravel-referral-rewriter-tag make network calls or affect performance?
- The package is described as lightweight and config-driven, and the available evaluation does not indicate outbound network calls, redirects, cache interactions, or database migrations. Its main runtime effect is expected to be referral tag rewriting in URL or tag generation behavior. You should still validate performance and failure behavior in staging, especially if referral rewriting occurs on hot request paths.
- Is this package actively maintained and who owns Instant Gaming tag changes?
- The repository shows maintenance activity through dependency automation and a v1.0.6 stabilization release, but the package is niche, so long-term maintainer coverage should be verified before relying on it. Ownership of Instant Gaming tag changes and subtag values usually remains with your team unless the maintainer documents otherwise. Review repository activity and be prepared to manage configuration updates yourself.
Weaver
How can I help you explore Laravel packages today?