Package Data | |
---|---|
Maintainer Username: | jeylabs |
Maintainer Contact: | ratheep.ceymplon@jeylabs.com (jeylabs) |
Package Create Date: | 2017-02-01 |
Package Last Update: | 2017-09-07 |
Home Page: | https://jeylabs.github.io/mail-tracker/ |
Language: | PHP |
License: | MIT |
Last Refreshed: | 2024-11-19 03:15:12 |
Package Statistics | |
---|---|
Total Downloads: | 4,316 |
Monthly Downloads: | 2 |
Daily Downloads: | 0 |
Total Stars: | 14 |
Total Watchers: | 5 |
Total Forks: | 0 |
Total Open Issues: | 0 |
MailTracker will hook into all outgoing emails from Laravel and inject a tracking code into it. It will also store the rendered email in the database. There is also an interface to view sent emails.
Via Composer
$ composer require jeylabs/mail-tracker
Add the following to the providers array in config/app.php:
Jeylabs\MailTracker\MailTrackerServiceProvider::class,
Publish the config file and migration
$ php artisan vendor:publish
Run the migration
$ php artisan migrate
Once installed, all outgoing mail will be logged to the database. The following config options are available in config/mail-tracker.php:
When an email is sent, viewed, or a link is clicked, its tracking information is counted in the database using the Jeylabs\MailTracker\Model\SentEmail model. You may want to do additional processing on these events, so an event is fired in these cases:
If you are using the Amazon SNS notification system, an event is fired when you receive a permanent bounce. You may want to mark the email as bad or remove it from your database.
To install an event listener, you will want to create a file like the following:
<?php
namespace App\Listeners;
use Jeylabs\MailTracker\Events\ViewEmailEvent;
class EmailViewed
{
/**
* Create the event listener.
*
* @return void
*/
public function __construct()
{
//
}
/**
* Handle the event.
*
* @param ViewEmailEvent $event
* @return void
*/
public function handle(ViewEmailEvent $event)
{
// Access the model using $event->sent_email...
}
}
<?php
namespace App\Listeners;
use Jeylabs\MailTracker\Events\PermanentBouncedMessageEvent;
class BouncedEmail
{
/**
* Create the event listener.
*
* @return void
*/
public function __construct()
{
//
}
/**
* Handle the event.
*
* @param PermanentBouncedMessageEvent $event
* @return void
*/
public function handle(PermanentBouncedMessageEvent $event)
{
// Access the email address using $event->email_address...
}
}
Then you must register the event in your \App\Providers\EventServiceProvider $listen array:
/**
* The event listener mappings for the application.
*
* @var array
*/
protected $listen = [
'Jeylabs\MailTracker\Events\ViewEmailEvent' => [
'App\Listeners\EmailViewed',
],
'Jeylabs\MailTracker\Events\PermanentBouncedMessageEvent' => [
'App\Listeners\BouncedEmail',
],
];
Often times you may need to link a sent email to another model. The best way to handle this is to add a header to your outgoing email that you can retrieve in your event listener. Here is an example:
/**
* Send an email and do processing on a model with the email
*/
\Mail::send('email.test', [], function ($message) use($email, $subject, $name, $model) {
$message->from('info@jeylabs.com', 'From Name');
$message->sender('info@jeylabs.com', 'Sender Name');
$message->to($email, $name);
$message->subject($subject);
// Create a custom header that we can later retrieve
$message->getHeaders()->addTextHeader('X-Model-ID',$model->id);
});
and then in your event listener:
public function handle(EmailSentEvent $event)
{
$tracker = $event->sent_email;
$model_id = $event->getHeader('X-Model-ID');
$model = Model::find($model_id);
// Perform your tracking/linking tasks on $model knowing the SentEmail object
}
Note that the headers you are attaching to the email are actually going out with the message, so do not store any data that you wouldn't want to expose to your email recipients.
If you use Amazon SES, you can add some additional information to your tracking. To set up the SES callbacks, first set up SES notifications under your domain in the SES control panel. Then subscribe to the topic by going to the admin panel of the notification topic and creating a subscription for the URL you copied from the admin page. The system should immediately respond to the subscription request. If you like, you can use multiple subscriptions (i.e. one for delivery, one for bounces). See above for events that are fired on a failed message.