- How do I install michaelgrimshaw/laravel-email-tracker in a Laravel app?
- Install it with Composer using composer require michaelgrimshaw/laravel-email-tracker. After that, publish the package configuration and migrations, run your database migrations, and follow the README for wiring it into Laravel's mail system. Verify your app's Laravel and PHP versions against the package's Composer constraints before installing.
- Does this package track email opens and link clicks automatically?
- The package is designed to record opens and link clicks for outgoing emails by integrating with Laravel's mail system. Opens are generally detected through a tracking pixel and clicks through tracked links or redirects. You still need to install, migrate, and configure it, and you should verify behavior in your own mail flow.
- Where does laravel-email-tracker store its tracking data?
- Tracking data is stored in your application's database using tables created by the package migrations. Run the migrations after installation and review the published configuration for any table or connection settings. This keeps email analytics data within your Laravel app rather than an external service.
- Which Laravel versions are supported by michaelgrimshaw/laravel-email-tracker?
- The package integrates with Laravel's mail system, but the exact supported Laravel and PHP versions are defined by its Composer constraints. Check the repository README or Packagist metadata for the current version matrix before installing. If you maintain older Laravel apps, confirm compatibility rather than assuming support.
- Can I use it with Laravel notifications and Mailables?
- Yes, because it hooks into Laravel's mail system, it can be used with Mailables and notifications that send email. Apply the package's tracking configuration to the mailables or notification channels you want to monitor. Start with a single notification in staging to confirm opens and clicks are recorded.
- Is this package suitable for campaigns and transactional emails?
- The package is intended for adding simple email analytics to notifications, campaigns, and transactional messages. It records opens and link clicks and stores the results in your database. For campaigns, consider queueing and privacy requirements; for transactional mail, make sure tracking does not interfere with critical delivery.
- What configuration is needed after installing laravel-email-tracker?
- After installing, publish the package configuration and migrations, then run migrate to create tracking tables. You will also need to configure the mail integration and any tracking routes or domains described in the README. Review environment variables and middleware so tracking endpoints are reachable but not abused.
- How can I test email open and click tracking locally?
- Use Laravel's mail testing helpers to assert messages are sent, then inspect the package's tracking tables for recorded events. Because opens and clicks depend on HTTP requests to tracking endpoints, you may need to request the pixel or redirect URL manually in local tests. Check the package's own tests and README for the supported testing approach.
- What are the production concerns with email open and click tracking?
- Open tracking is approximate because many mail clients block images or proxy content, while link clicks are usually more reliable. In production, plan for privacy and consent requirements, use a stable tracking domain, and ensure tracking routes are performant. Avoid letting tracking failures break critical transactional email delivery.
- What alternatives exist and how do I evaluate maintenance for this package?
- Alternatives include email service providers with built-in analytics and other Laravel packages that add open and click tracking; compare data ownership, features, and Laravel version support. For this package, check the GitHub repository's recent commits, releases, and issue activity to judge maintenance. Keeping tracking data in your own database is a key advantage if that fits your privacy and reporting needs.