PHPackages                             gustavoh3nryk/mail-tracker - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Mail & Notifications](/categories/mail)
4. /
5. gustavoh3nryk/mail-tracker

ActiveLibrary[Mail & Notifications](/categories/mail)

gustavoh3nryk/mail-tracker
==========================

Logs and tracks all outgoing emails from Laravel

1.0.2(1y ago)0507MITPHPPHP ^8.0

Since May 23Pushed 1y ago1 watchersCompare

[ Source](https://github.com/gustavoh3nryk/mail-tracker)[ Packagist](https://packagist.org/packages/gustavoh3nryk/mail-tracker)[ Docs](https://github.com/gustavoh3nryk/MailTracker)[ RSS](/packages/gustavoh3nryk-mail-tracker/feed)WikiDiscussions master Synced 1mo ago

READMEChangelogDependenciesVersions (4)Used By (0)

MailTracker
===========

[](#mailtracker)

[![Latest Version on Packagist](https://camo.githubusercontent.com/df34329406abcde7ec2d0c1661e12c6cf70e6a2d2780b710d6002822318e30f7/68747470733a2f2f696d672e736869656c64732e696f2f7061636b61676973742f762f6775737461766f68336e72796b2f6d61696c2d747261636b65722e7376673f7374796c653d666c61742d737175617265)](https://packagist.org/packages/gustavoh3nryk/mail-tracker)[![Software License](https://camo.githubusercontent.com/55c0218c8f8009f06ad4ddae837ddd05301481fcf0dff8e0ed9dadda8780713e/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f6c6963656e73652d4d49542d627269676874677265656e2e7376673f7374796c653d666c61742d737175617265)](LICENSE.md)[![Total Downloads](https://camo.githubusercontent.com/b320721d9eda39184b488790966d798cc292a09d5c9b4ec99459997630981114/68747470733a2f2f696d672e736869656c64732e696f2f7061636b61676973742f64742f6775737461766f68336e72796b2f6d61696c2d747261636b65722e7376673f7374796c653d666c61742d737175617265)](https://packagist.org/packages/gustavoh3nryk/mail-tracker)

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.

NOTE: If you are using Laravel 9.x you MUST be on version 9.6.0 or higher.
--------------------------------------------------------------------------

[](#note-if-you-are-using-laravel-9x-you-must-be-on-version-960-or-higher)

Install
-------

[](#install)

Via Composer

```
composer require gustavoh3nryk/mail-tracker
```

Publish the config file and migration

```
php artisan vendor:publish --provider="gustavoh3nryk\MailTracker\MailTrackerServiceProvider"
```

Run the migration

```
php artisan migrate
```

Note: If you would like to use a different connection to store your models, you should update the mail-tracker.php config entry `connection` before running the migrations.

If you would like to use your own migrations, you can skip this library migrations by calling `MailTracker::ignoreMigrations()`. For example:

```
// In AppServiceProvider

public function boot()
{
    MailTracker::ignoreMigrations();
}
```

Usage
-----

[](#usage)

Once installed, all outgoing mail will be logged to the database. The following config options are available in config/mail-tracker.php:

- **name**: set your App Name.
- **inject-pixel**: set to true to inject a tracking pixel into all outgoing html emails.
- **track-links**: set to true to rewrite all anchor href links to include a tracking link. The link will take the user back to your website which will then redirect them to the final destination after logging the click.
- **expire-days**: How long in days that an email should be retained in your database. If you are sending a lot of mail, you probably want it to eventually expire. Set it to zero to never purge old emails from the database.
- **route**: The route information for the tracking URLs. Set the prefix and middlware as desired.
- **admin-route**: The route information for the admin. Set the prefix and middleware.
- **admin-template**: The params for the Admin Panel and Views. You can integrate your existing Admin Panel with the MailTracker admin panel.
- **date-format**: You can define the format to show dates in the Admin Panel.
- **content-max-size**: You can overwrite default maximum length limit for `content` database field. Do not forget update it's type from `text` if you need to make it longer.

If you do not wish to have an email tracked, then you can add the `X-No-Track` header to your message. Put any random string into this header to prevent the tracking from occurring. The header will be removed from the email prior to being sent.

```
\Mail::send('email.test', [], function ($message) {
    // ... other settings here
    $message->getHeaders()->addTextHeader('X-No-Track',Str::random(10));
});
```

Note on dev testing
-------------------

[](#note-on-dev-testing)

Several people have reported the tracking pixel not working while they were testing. What is happening with the tracking pixel is that the email client is connecting to your website to log the view. In order for this to happen, images have to be visible in the client, and the client has to be able to connect to your server.

When you are in a dev environment (i.e. using the `.test` domain with Valet, or another domain known only to your computer) you must have an email client on your computer. Further complicating this is the fact that Gmail and some other web-based email clients don't connect to the images directly, but instead connect via proxy. That proxy won't have a connection to your `.test` domain and therefore will not properly track emails. I always recommend using [mailtrap.io](https://mailtrap.io) for any development environment when you are sending emails. Not only does this solve the issue (mailtrap.io does not use a proxy service to forward images in the emails) but it also protects you from accidentally sending real emails from your test environment.

Events
------

[](#events)

When an email is sent, viewed, or a link is clicked, its tracking information is counted in the database using the gustavoh3nryk\\MailTracker\\Model\\SentEmail model. This processing is done via dispatched jobs to the queue in order to prevent the database from being overwhelmed in an email blast situation. You may choose the queue that these events are dispatched via the `mail-tracker.tracker-queue` config setting, or leave it `null` to use the default queue. By using a non-default queue, you can prioritize application-critical tasks above these tracking tasks.

You may want to do additional processing on these events, so an event is fired in these cases:

- gustavoh3nryk\\MailTracker\\Events\\EmailSentEvent
    - Public attribute `sent_email` contains the `SentEmail` model
- gustavoh3nryk\\MailTracker\\Events\\ViewEmailEvent
    - Public attribute `sent_email` contains the `SentEmail` model
    - Public attribute `ip_address` contains the IP address that was used to trigger the event
- gustavoh3nryk\\MailTracker\\Events\\LinkClickedEvent
    - Public attribute `sent_email` contains the `SentEmail` model
    - Public attribute `ip_address` contains the IP address that was used to trigger the event
    - Public attribute `link_url` contains the clicked URL

If you are using the Amazon SNS notification system, these events are fired so you can do additional processing.

- gustavoh3nryk\\MailTracker\\Events\\EmailDeliveredEvent (when you received a "message delivered" event, you may want to mark the email as "good" or "delivered" in your database)
    - Public attribute `sent_email` contains the `SentEmail` model
    - Public attribute `email_address` contains the specific address that was used to trigger the event
- gustavoh3nryk\\MailTracker\\Events\\ComplaintMessageEvent (when you received a complaint, ex: marked as "spam", you may want to remove the email from your database)
    - Public attribute `sent_email` contains the `SentEmail` model
    - Public attribute `email_address` contains the specific address that was used to trigger the event
- gustavoh3nryk\\MailTracker\\Events\\PermanentBouncedMessageEvent (when you receive a permanent bounce, you may want to mark the email as bad or remove it from your database) gustavoh3nryk\\MailTracker\\Events\\TransientBouncedMessageEvent (when you receive a transient bounce. Check the event's public attributes for `bounce_sub_type` and `diagnostic_code` to determine if you want to do additional processing when this event is received.)
    - Public attribute `sent_email` contains the `SentEmail` model
    - Public attribute `email_address` contains the specific address that was used to trigger the event

To install an event listener, you will want to create a file like the following:

```