AutoGineer
Generated banner for Integration Laravel
Generated logo for Integration Laravel

Integration Laravel

PostHogOfficialCreated by PostHog

  • Skill
  • Tool integration
  • Data and AI
  • MIT
  • No issues found
Download ZIP

From the author

PostHog integration for Laravel applications
— the description by PostHog

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a systematic approach to integrating PostHog into Laravel applications. It emphasizes a clean architecture by utilizing a dedicated PostHogService class to wrap the PHP SDK, ensuring that analytics logic remains decoupled from business controllers. The guide covers user identification, custom event tracking, feature flag implementation, and error tracking, while strictly adhering to Laravel best practices such as using environment variables for configuration and avoiding the use of event observers for analytics.

What it does

  • Provides a step-by-step workflow for PostHog integration
  • Defines patterns for user identification and custom event capture
  • Demonstrates how to implement feature flags and payload support
  • Outlines methods for capturing exceptions and errors
  • Establishes a centralized service-based architecture for analytics
  • Includes reference examples for Laravel-specific implementation

When to use it

  • When you need to add analytics to a new or existing Laravel application
  • When you want to implement feature flags within a Laravel project
  • When you need to track user behavior and conversion funnels server-side
  • When you want to standardize error tracking across your Laravel codebase

Advantages

  • Promotes clean code by centralizing analytics in a service class
  • Ensures secure configuration management using environment variables
  • Provides clear patterns for identifying users during authentication
  • Reduces code duplication by following established implementation examples

Usage examples

“How do I set up PostHog in my new Laravel project?”
The agent will guide you through the four-step integration workflow, starting with project analysis and event planning, followed by configuration and implementation.
“Where should I place my PostHog capture calls in Laravel?”
The agent will instruct you to create a PostHogService class in app/Services/ and call capture methods explicitly within your application logic.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/posthog/integration-laravel/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip integration-laravel.zip -d .agents/skills

Documentation by PostHog

PostHog integration for Laravel

This skill helps you add PostHog analytics to Laravel applications.

Workflow

Follow these steps in order to complete the integration:

  1. basic-integration-1.0-begin.md - PostHog Setup - Begin ← Start here

  2. basic-integration-1.1-edit.md - PostHog Setup - Edit

  3. basic-integration-1.2-revise.md - PostHog Setup - Revise

  4. basic-integration-1.3-conclude.md - PostHog Setup - Conclusion

Reference files

  • references/EXAMPLE.md - Laravel example project code

  • references/laravel.md - Laravel - docs

  • references/identify-users.md - Identify users - docs

  • references/basic-integration-1.0-begin.md - PostHog setup - begin

  • references/basic-integration-1.1-edit.md - PostHog setup - edit

  • references/basic-integration-1.2-revise.md - PostHog setup - revise

  • references/basic-integration-1.3-conclude.md - PostHog setup - conclusion

The example project shows the target implementation pattern. Consult the documentation for API details.

Key principles

  • Environment variables: Always use environment variables for PostHog keys. Never hardcode them.

  • Minimal changes: Add PostHog code alongside existing integrations. Don't replace or restructure existing code.

  • Match the example: Your implementation should follow the example project's patterns as closely as possible.

Framework guidelines

  • Create a dedicated PostHogService class in app/Services/ - do NOT scatter PostHog::capture calls throughout controllers

  • Register PostHog configuration in config/posthog.php using env() for all settings (api_key, host, disabled)

  • Do NOT use Laravel's event system or observers for analytics - call capture explicitly where actions occur

  • Remember that source code is available in the vendor directory after composer install

  • posthog/posthog-php is the PHP SDK package name

  • Check composer.json for existing dependencies and autoload configuration before adding new files

  • The PHP SDK uses static methods (PostHog::capture, PostHog::identify) - initialize once with PostHog::init()

  • PHP SDK methods take associative arrays with 'distinctId', 'event', 'properties' keys - not positional arguments

Identifying users

Identify users during login and signup events. Refer to the example code and documentation for the correct identify pattern for this framework. If both frontend and backend code exist, pass the client-side session and distinct ID using X-POSTHOG-DISTINCT-ID and X-POSTHOG-SESSION-ID headers to maintain correlation.

Error tracking

Add PostHog error tracking to relevant files, particularly around critical user flows and API boundaries.

Files

references/basic-integration-1.1-edit.md

title: PostHog Setup - Edit description: Implement PostHog event tracking in the identified files, following best practices and the example project

For each of the files and events noted in .posthog-events.json, make edits to capture events using PostHog. Make sure to set up any helper files needed. Carefully examine the included example project code: your implementation should match it as closely as possible. Do not spawn subagents.

Use environment variables for PostHog keys. Do not hardcode PostHog keys.

If a file already has existing integration code for other tools or services, don't overwrite or remove that code. Place PostHog code below it.

For each event, add useful properties, and use your access to the PostHog source code to ensure correctness. You also have access to documentation about creating new events with PostHog. Consider this documentation carefully and follow it closely before adding events. Your integration should be based on documented best practices. Carefully consider how the user project's framework version may impact the correct PostHog integration approach.

Remember that you can find the source code for any dependency in the node_modules directory. This may be necessary to properly populate property names. There are also example project code files available via the PostHog MCP; use these for reference.

Where possible, add calls for PostHog's identify() function on the client side upon events like logins and signups. Use the contents of login and signup forms to identify users on submit. If there is server-side code, pass the client-side session and distinct ID to the server-side code to identify the user. On the server side, make sure events have a matching distinct ID where relevant.

It's essential to do this in both client code and server code, so that user behavior from both domains is easy to correlate.

You should also add PostHog exception capture error tracking to these files where relevant.

Remember: Do not alter the fundamental architecture of existing files. Make your additions minimal and targeted.

Remember the documentation and example project resources you were provided at the beginning. Read them now.

Status

Status to report in this phase:

  • Inserting PostHog capture code

  • A status message for each file whose edits you are planning, including a high level summary of changes

  • A status message for each file you have edited

Upon completion, continue with: basic-integration-1.2-revise.md

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs an API key

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
PostHog
Publisher
PostHog (Official)
Source
PostHog/skills · skills/posthog/integration/skills/laravel · commit a5d30e7
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced
Also distributed in
PostHog/skills

AutoGineer is not affiliated with or endorsed by PostHog.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download integration-laravel.zip