- What is laravel-notification-channels/vwo-engage used for?
- This package is a Laravel notification channel for VWO Engage. It lets you send VWO Engage push notifications through a Laravel notification class instead of writing custom API code. Use it when your application already targets VWO Engage and you want notification delivery to follow Laravel conventions.
- How do I install laravel-notification-channels/vwo-engage?
- Install it with Composer using composer require laravel-notification-channels/vwo-engage. Then review the README for any config publishing, service provider, or migration steps. The package is designed for Composer-based Laravel integration, so confirm package discovery behavior in your app.
- How do I configure VWO Engage credentials in Laravel?
- Configure your VWO Engage credentials in the package config or environment variables as described in the README. Keep API keys out of source control and rebuild Laravel's config cache after changes. Confirm the exact credential key names in the package documentation before deploying.
- Does this package support Laravel 8 and Laravel 9?
- The v1.2.0 release notes explicitly add Laravel 8 support. They do not demonstrate support for Laravel 9 or newer. Check the package composer.json and README for the authoritative Laravel version constraint before installing, and test carefully on Laravel 9 or newer.
- How do I send a VWO Engage push notification from a Laravel notification?
- Create a Laravel notification class, add the VWO Engage channel to its via method, and implement the channel payload method documented by the package. Send the notification to a notifiable user as usual. The package handles the VWO Engage API call so you avoid custom HTTP code.
- Does this package require Guzzle 7?
- The v1.2.0 release notes explicitly mention Guzzle 7 support. Teams still on Guzzle 6 should plan an HTTP client upgrade and check dependency resolution. Review composer.json to see whether Guzzle 7 is required or allowed alongside other versions.
- Can I use this package in production?
- You can evaluate it for production where the application is on Laravel 8 and Guzzle 7, but Laravel 8 is end-of-life. Validate credentials, config, HTTP timeouts, retries, SSL and proxy behavior, and exception handling in a non-production environment first. Canary deploy and monitor outbound HTTP errors and latency.
- How do I test VWO Engage notifications in Laravel?
- Use Laravel notification fakes or HTTP client fakes to assert that the VWO Engage channel is selected and the outbound request payload is correct. Run the package tests plus your own integration tests, especially around credentials and HTTP behavior. Release notes alone do not confirm the package CI or test matrix, so verify coverage in the repository.
- What are alternatives to laravel-notification-channels/vwo-engage?
- Alternatives include calling the VWO Engage API directly with Laravel's HTTP client or choosing another maintained push notification channel that supports your Laravel version. Compare Laravel version support, maintenance cadence, credential handling, and test coverage. This package is a good fit when you want VWO Engage delivery through a familiar Laravel notification class.
- How is laravel-notification-channels/vwo-engage maintained?
- The available assessment is based only on v1.2.0 release notes and does not establish maintainer responsiveness or long-term support. Laravel 8 support is end-of-life, so confirm the package support window, security policy, and upgrade path. Check issue activity, release cadence, and CI status before relying on it.