PostHog integration for Ruby on Rails applications
This skill helps you add PostHog analytics to Ruby on Rails applications.
Follow these steps in order to complete the integration:
basic-integration-1.0-begin.md - PostHog Setup - Begin ← Start herebasic-integration-1.1-edit.md - PostHog Setup - Editbasic-integration-1.2-revise.md - PostHog Setup - Revisebasic-integration-1.3-conclude.md - PostHog Setup - Conclusionreferences/EXAMPLE.md - Ruby on Rails example project codereferences/ruby-on-rails.md - Ruby on rails - docsreferences/ruby.md - Ruby - docsreferences/identify-users.md - Identify users - docsreferences/basic-integration-1.0-begin.md - PostHog setup - beginreferences/basic-integration-1.1-edit.md - PostHog setup - editreferences/basic-integration-1.2-revise.md - PostHog setup - revisereferences/basic-integration-1.3-conclude.md - PostHog setup - conclusionThe example project shows the target implementation pattern. Consult the documentation for API details.
rails generate posthog:install to create the initializer, or manually create config/initializers/posthog.rbposthog_distinct_id ->(user) { user.email } or pass user_id: in a hash argumentgem 'posthog-ruby' to Gemfile) but require it with require 'posthog' (NOT require 'posthog-ruby')distinct_id: keyword syntaxIdentify 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.
Add PostHog error tracking to relevant files, particularly around critical user flows and API boundaries.