PHPackages                             broken-titan/laravel-mparticle-channel - 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. broken-titan/laravel-mparticle-channel

ActiveLibrary

broken-titan/laravel-mparticle-channel
======================================

mParticle notification channel for Laravel.

v1.1.1(3y ago)06.6k1MITPHPPHP >=7.2CI failing

Since Feb 18Pushed 1y ago1 watchersCompare

[ Source](https://github.com/broken-titan/laravel-mparticle-channel)[ Packagist](https://packagist.org/packages/broken-titan/laravel-mparticle-channel)[ RSS](/packages/broken-titan-laravel-mparticle-channel/feed)WikiDiscussions master Synced 1mo ago

READMEChangelog (3)Dependencies (2)Versions (4)Used By (0)

Laravel mParticle Notification Channel
======================================

[](#laravel-mparticle-notification-channel)

This package makes it easy to integrate Laravel with mParticle for sending notifications.

Contents
--------

[](#contents)

- [Installation](#installation)
- [Configuration](#configuration)
- [Usage](#usage)
- [Testing](#testing)
- [Security](#security)
- [Contributing](#contributing)
- [Credits](#credits)
- [License](#license)

Installation
------------

[](#installation)

Install this package with Composer:

```
composer require broken-titan/laravel-mparticle-channel

```

Configuration
-------------

[](#configuration)

Before you may begin using the mParticle service, you must obtain authentication information from mParticle. The username and password must be assigned to MPARTICLE\_USERNAME and MPARTICLE\_PASSWORD in your .env file. You will also need to configure your mParticle pod using MPARTICLE\_POD if you are not on the US1 pod.

By default the config file is merged with services.php and are accessible using config("services.mparticle").

Usage
-----

[](#usage)

Once installation is complete, you can send events to mParticle by creating standard Laravel notifications. For example:

```
    namespace App\Notifications;

    use Illuminate\Notifications\Notification;
    use BrokenTitan\mParticle\Channels\MParticleChannel;
    use BrokenTitan\mParticle\Messages\MParticleEventMessage;

    class UserCreated extends Notification {
        public function via($notifiable) {
            return [MParticleChannel::class];
        }

        public function toMParticle($notifiable) : MParticleEventMessage {
            $data = [
                "property" => "value"
            ];

            return new MParticleEventMessage("user_created", MParticleEventMessage::TRANSACTON, $data);
        }
    }

```

You will also want to define a routeNotificationForMParticle() function on your Notifiable classes. They need to return an array with user identities that you want to send. For example:

```
public function routeNotificationForMParticle() {
    return ["customer_id" => 123, "email" => "example@domain.com"];
}

```

Testing
-------

[](#testing)

```
$ composer test

```

Security
--------

[](#security)

If you discover any security issues that would affect existing users, please email  instead of using the issue tracker.

Contributing
------------

[](#contributing)

Feel free to contribute to the package.

License
-------

[](#license)

The MIT License (MIT). Please see [License File](LICENSE.md) for more information.

###  Health Score

29

—

LowBetter than 60% of packages

Maintenance33

Infrequent updates — may be unmaintained

Popularity19

Limited adoption so far

Community8

Small or concentrated contributor base

Maturity46

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~104 days

Total

3

Last Release

1337d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/0349b2c67312de7cd10ed2a5f75a49cce795055f9f6697860c6f8335362425c1?d=identicon)[TheThird](/maintainers/TheThird)

---

Top Contributors

[![th3third](https://avatars.githubusercontent.com/u/7121736?v=4)](https://github.com/th3third "th3third (6 commits)")

###  Code Quality

TestsPHPUnit

### Embed Badge

![Health badge](/badges/broken-titan-laravel-mparticle-channel/health.svg)

```
[![Health](https://phpackages.com/badges/broken-titan-laravel-mparticle-channel/health.svg)](https://phpackages.com/packages/broken-titan-laravel-mparticle-channel)
```

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)