qodenl/laravel-posthog is a Laravel package for laravel implementation for posthog.
It currently has 35 GitHub stars and 95.426 downloads on Packagist (latest version 1.3.2).
Install it with composer require qodenl/laravel-posthog.
Discover more Laravel packages by qodenl
or browse all Laravel packages to compare alternatives.
Last updated
This package provides a simple integration of Posthog in Laravel applications.
The package covers both Identify as Capture (events) requests which can be triggered manual or automatically using an Event Listener.
You can also easily integrate Feature Flags within your application.
This package uses the PostHog / posthog-php package. For more information about Posthog, check their documentation.
You can install the package via composer:
composer require qodenl/laravel-posthog
You can publish the config file with:
php artisan vendor:publish --provider="QodeNL\LaravelPosthog\PosthogServiceProvider"
After publishing the content, set your API key and Host in your .env file:
POSTHOG_KEY=
POSTHOG_HOST=https://posthog.com
POSTHOG_ENABLED=true
Make sure you copy the correct host from Posthog.
Posthog is enabled by default, but you can disable it with the POSTHOG_ENABLED env variable.
Make sure to disable Posthog for local/testing environments.
use QodeNL\LaravelPosthog\Facades\Posthog;
Posthog::capture('event name', ['property' => 'value']);
You can add the PosthogListener::class listener to your EventServiceProvider. The package will create an capture automatically when the event happens.
By default, all fillable attributes from a model (available in the event) will be sent to Posthog as properties.
You can specify which attributes you want to send to Posthog by adding a PosthogAttributes property to your Model.
public $posthogAttributes = [
'first_name',
'last_name',
];
Attributes in the hidden property will always be ignored.
Events will be sent to Posthog with a unique ID for anonymous users. When the user is recognized (usually on log in),
you should trigger the identify method to link the unique ID to the user.
You can pass additional information about the user to be stored in his profile.
use QodeNL\LaravelPosthog\Facades\Posthog;
Posthog::identify('[email protected]', ['first_name' => 'John', 'last_name' => 'Doe']);
If you want to assign a session ID to a user (for example a front-end session ID) you can use the alias method.
The Session ID argument will be assigned to the auto-generated ID of the user.
Posthog::alias('Session ID here');
You can associate events with a group (e.g. a company, team or project) by setting the group type and key. Once set, all subsequent capture calls will include the group automatically.
use QodeNL\LaravelPosthog\Facades\Posthog;
Posthog::setGroup('company', 'company_id_5');
Posthog::capture('page_view', ['url' => '/dashboard']); // includes the group
You can set multiple groups at once by chaining the method:
Posthog::setGroup('company', 'company_id_5')->setGroup('project', 'project_id_8');
To create a new group, or update properties on a group, by using the updateOrCreateGroup method:
Posthog::updateOrCreateGroup('company', 'company_id_5', ['name' => 'Acme Inc', 'plan' => 'enterprise']);
You can also pass group properties as a third argument to setGroup. This will automatically call updateOrCreateGroup to sync the group properties with PostHog:
Posthog::setGroup('company', 'company_id_5', ['name' => 'Acme Inc', 'plan' => 'enterprise']);
For more information about group analytics, check the Posthog PHP documentation.
This package also includes a custom driver for the Laravel Pennant package. With this custom driver, you can use Laravel Pennant and listen to the feature flags set in Posthog.
To use this driver, simply add the following to your .env file. You don't need to create the database migration.
PENNANT_STORE=posthog
Also, add the store to the stores array in config/pennant.php:
'stores' => [
'posthog' => [
'driver' => 'posthog',
],
],
You can use the Laravel Pennant package as you would normally do. However, some features, like enabling a feature for a user, are not supported by the Posthog driver. A PosthogFeatureException will be thrown when you try to use these features.
Laravel\Pennant\Feature::active('myFeatureFlagKey'); // true
If you don't want to use Laravel Pennant, you can also implement the feature flags using our Facade:
use QodeNL\LaravelPosthog\Facades\Posthog;
Posthog::getAllFlags();
Get all feature flags with boolean if enabled for user or not.
use QodeNL\LaravelPosthog\Facades\Posthog;
Posthog::isFeatureEnabled('myFeatureFlagKey');
Check if feature is enabled for user. Returns boolean.
use QodeNL\LaravelPosthog\Facades\Posthog;
Posthog::getFeatureFlag('myFeatureFlagKey');
Get feature flag. Returns false if feature is disabled. Returns true (or payload if set).
You can pass groups, personProperties and groupProperties to the isFeatureEnabled and getFeatureFlag functions.
Please check the Posthog PHP documentation for more information.
In the Posthog config you can configure if events should be sent to Posthog and if you want to evaluate events locally.
By default, the package generates a distinct ID based on the authenticated user ID (with an optional prefix) or a hashed session ID for anonymous users.
If you want full control over the distinct ID, you can register a custom resolver. For example, in your AppServiceProvider:
use QodeNL\LaravelPosthog\Facades\Posthog;
public function boot(): void
{
Posthog::resolveDistinctIdUsing(function () {
return auth()->id() ?? session()->getId();
});
}
The capture, identify and alias actions are executed by jobs. Be sure you've enabled and configured queues for your applications.
Please see CHANGELOG for more information on what has changed recently.
The MIT License (MIT). Please see License File for more information.
