Generated banner for Integration React React Router 7 Data
Generated logo for Integration React React Router 7 Data

Integration React React Router 7 Data

PostHogOfficialCreated by PostHog

  • Skill
  • Tool integration
  • Software development
  • MIT
  • No issues found

From the author

PostHog integration for React Router v7 - Data mode 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 workflow for adding PostHog analytics to React Router v7 applications using Data mode. It covers the full lifecycle of integration, including client-side initialization, user identification, event tracking, and error handling. The guide emphasizes maintaining clean code by using environment variables for configuration, avoiding unnecessary useEffect hooks for event logic, and following established patterns for feature flags and exception capture.

What it does

  • Provides a step-by-step workflow for PostHog integration.
  • Demonstrates client-side initialization using PostHogProvider.
  • Outlines patterns for user identification during login flows.
  • Shows how to implement manual event tracking for user actions.
  • Details error tracking using error boundaries and manual capture.
  • Provides best practices for feature flag usage and state management.

When to use it

  • When you need to add product analytics to a React Router v7 Data mode project.
  • When you want to implement session replay and error tracking in your React application.
  • When you need to identify users and track specific business events.
  • When you are looking for standardized patterns for feature flag implementation.

Advantages

  • Follows a structured, multi-step integration process.
  • Promotes clean code by discouraging misuse of useEffect.
  • Includes clear patterns for both client-side and server-side event correlation.
  • Provides a reference example project for implementation guidance.

Usage examples

“How do I initialize PostHog in my React Router 7 app?”
The skill directs you to wrap your application in the PostHogProvider and initialize the client in your entry point using environment variables.
“Where should I place my event tracking logic?”
The skill advises placing capture calls directly within event handlers rather than using useEffect hooks.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/posthog/integration-react-react-router-7-data/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip integration-react-react-router-7-data.zip -d .agents/skills

Documentation by PostHog

PostHog integration for React Router v7 - Data mode

This skill helps you add PostHog analytics to React Router v7 - Data mode 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 - React Router v7 - Data mode example project code

  • references/react-router-v7-data-mode.md - React router v7 data mode - 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

  • For feature flags, use useFeatureFlagEnabled() or useFeatureFlagPayload() hooks - they handle loading states and external sync automatically

  • Add analytics capture in event handlers where user actions occur, NOT in useEffect reacting to state changes

  • Do NOT use useEffect for data transformation - calculate derived values during render instead

  • Do NOT use useEffect to respond to user events - put that logic in the event handler itself

  • Do NOT use useEffect to chain state updates - calculate all related updates together in the event handler

  • Do NOT use useEffect to notify parent components - call the parent callback alongside setState in the event handler

  • To reset component state when a prop changes, pass the prop as the component's key instead of using useEffect

  • useEffect is ONLY for synchronizing with external systems (non-React widgets, browser APIs, network subscriptions)

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/react-router-v7-data-mode.md

React Router V7 data mode - Docs

This guide walks you through setting up PostHog for React Router V7 in data mode. If you're using React Router in another mode, find the guide for that mode in the React Router page. If you're using React with another framework, go to the React integration guide.

  1. 1

    Install client-side SDKs

    Required

    First, you'll need to install posthog-js and @posthog/react using your package manager. These packages allow you to capture client-side events.

    PostHog AI

    npm
    npm install --save posthog-js @posthog/react
    Yarn
    yarn add posthog-js @posthog/react
    pnpm
    pnpm add posthog-js @posthog/react
    Bun
    bun add posthog-js @posthog/react
  2. 2

    Add your environment variables

    Required

    Add your environment variables to your .env.local file and to your hosting provider (e.g. Vercel, Netlify, AWS). You can find your project token and host in your project settings. If you're using Vite, including VITE_PUBLIC_ in their names ensures they are accessible in the frontend.

    .env.local

    PostHog AI

    VITE_PUBLIC_POSTHOG_TOKEN=<ph_project_token>
    VITE_PUBLIC_POSTHOG_HOST=https://us.i.posthog.com
  3. 3

    Add the PostHogProvider to your app

    Required

    In data mode, you'll need to wrap your RouterProvider with the PostHogProvider context. This passes an initialized PostHog client to your app.

    app/index.tsx

    PostHog AI

    import { StrictMode } from "react";
    import { createRoot } from "react-dom/client";
    import { createBrowserRouter, RouterProvider } from "react-router";
    import Root, { RootErrorBoundary } from "./app/root";
    import posthog from 'posthog-js';
    import { PostHogProvider } from '@posthog/react'
    posthog.init(import.meta.env.VITE_PUBLIC_POSTHOG_TOKEN, {
      api_host: import.meta.env.VITE_PUBLIC_POSTHOG_HOST,
      defaults: '2026-01-30',
    });
    const router = createBrowserRouter([...]);
    createRoot(document.getElementById("root")!).render(
      <StrictMode>
        {/* Pass PostHog client through PostHogProvider */}
        <PostHogProvider client={posthog}>
          <RouterProvider router={router} />
        </PostHogProvider>,
      );
    });

    This initializes PostHog and passes it to your app through the PostHogProvider context.

    TypeError: Cannot read properties of undefined

    If you see the error TypeError: Cannot read properties of undefined (reading '...') this is likely because you tried to call a posthog function when posthog was not initialized (such as during the initial render). On purpose, we still render the children even if PostHog is not initialized so that your app still loads even if PostHog can't load.

    To fix this error, add a check that posthog has been initialized such as:

    React

    PostHog AI

    useEffect(() => {
      posthog?.capture('test') // using optional chaining (recommended)
      if (posthog) {
        posthog.capture('test') // using an if statement
      }
    }, [posthog])

    Typescript helps protect against these errors.

  4. Verify client-side events are captured

    Checkpoint

    Confirm that you can capture client-side events and see them in your PostHog project

    At this point, you should be able to capture client-side events and see them in your PostHog project. This includes basic events like page views and button clicks that are autocaptured.

    You can also try to capture a custom event to verify it's working. You can access PostHog in any component using the usePostHog hook.

    TSX

    PostHog AI

    import { usePostHog } from '@posthog/react'
    function App() {
      const posthog = usePostHog()
      return <button onClick={() => posthog?.capture('button_clicked')}>Click me</button>
    }

    You should see these events in a minute or two in the activity tab.

  5. 4

    Access PostHog methods

    Required

    On the client-side, you can access the PostHog client using the usePostHog hook. This hook returns the initialized PostHog client, which you can use to call PostHog methods. For example:

    TSX

    PostHog AI

    import { usePostHog } from '@posthog/react'
    function App() {
      const posthog = usePostHog()
      return <button onClick={() => posthog?.capture('button_clicked')}>Click me</button>
    }

    For a complete list of available methods, see the posthog-js documentation.

  6. 5

    Identify your user

    Recommended

    Now that you can capture basic client-side events, you'll want to identify your user so you can associate users with captured events.

    Generally, you identify users when they log in or when they input some identifiable information (e.g. email, name, etc.). You can identify users by calling the identify method on the PostHog client:

    TSX

    PostHog AI

    export default function Login() {
      const { user, login } = useAuth();
      const posthog = usePostHog();
      const handleLogin = async (e: React.FormEvent) => {
        // existing code to handle login...
        const user = await login({ email, password });
        posthog?.identify(user.email,
          {
            email: user.email,
            name: user.name,
          }
        );
        posthog?.capture('user_logged_in');
      };
      return (
        <div>
          {/* ... existing code ... */}
          <button onClick={handleLogin}>Login</button>
        </div>
      );
    }

    PostHog automatically generates anonymous IDs for users before they're identified. When you call identify, a new identified person is created. All previous events tracked with the anonymous ID link to the new identified distinct ID, and all future captures on the same browser associate with the identified person.

  7. 6

    Create an error boundary

    Recommended

    PostHog can capture exceptions thrown in your app through an error boundary. React Router in data mode has a built-in error boundary that you can use to capture exceptions. You can create an error boundary by exporting RootErrorBoundary from your app/root.tsx file.

    app/root.tsx

    PostHog AI

    import { usePostHog } from '@posthog/react'
    export function RootErrorBoundary() {
      const error = useRouteError();
      const posthog = usePostHog();
      if (error) {
        posthog.captureException(error);
      }
      // other error handling code...
    }

    This automatically captures exceptions thrown in your React Router app using the posthog.captureException() method.

  8. 7

    Tracking element visibility

    Recommended

    The PostHogCaptureOnViewed component enables you to automatically capture events when elements scroll into view in the browser. This is useful for tracking impressions of important content, monitoring user engagement with specific sections, or understanding which parts of your page users are actually seeing.

    The component wraps your content and sends a $element_viewed event to PostHog when the wrapped element becomes visible in the viewport. It only fires once per component instance.

    Basic usage:

    React

    PostHog AI

    import { PostHogCaptureOnViewed } from '@posthog/react'
    function App() {
        return (
            <PostHogCaptureOnViewed name="hero-banner">
                <div>Your important content here</div>
            </PostHogCaptureOnViewed>
        )
    }

    With custom properties:

    You can include additional properties with the event to provide more context:

    React

    PostHog AI

    <PostHogCaptureOnViewed
        name="product-card"
        properties={{
            product_id: '123',
            category: 'electronics',
            price: 299.99
        }}
    >
        <ProductCard />
    </PostHogCaptureOnViewed>

    Tracking multiple children:

    Use trackAllChildren to track each child element separately. This is useful for galleries or lists where you want to know which specific items were viewed:

    React

    PostHog AI

    <PostHogCaptureOnViewed
        name="product-gallery"
        properties={{ gallery_type: 'featured' }}
        trackAllChildren
    >
        <ProductCard id="1" />
        <ProductCard id="2" />
        <ProductCard id="3" />
    </PostHogCaptureOnViewed>

    When trackAllChildren is enabled, each child element sends its own event with a child_index property indicating its position.

    Custom intersection observer options:

    You can customize when elements are considered "viewed" by passing options to the IntersectionObserver:

    React

    PostHog AI

    <PostHogCaptureOnViewed
        name="footer"
        observerOptions={{
            threshold: 0.5,  // Element is 50% visible
            rootMargin: '0px'
        }}
    >
        <Footer />
    </PostHogCaptureOnViewed>

    The component passes all other props to the wrapper div, so you can add styling, classes, or other HTML attributes as needed.

  9. 8

    Set up server-side analytics

    Recommended

    Now that you've set up PostHog for React Router V7 in data mode, you can continue to set up server-side analytics. You can find our other SDKs in the SDKs page.

    To help PostHog track your user sessions across the client and server, you'll need to add the __add_tracing_headers: ['your-backend-domain1.com', 'your-backend-domain2.com', ...] option to your PostHog initialization:

    TSX

    PostHog AI

    posthog.init(import.meta.env.VITE_PUBLIC_POSTHOG_TOKEN, {
      api_host: import.meta.env.VITE_PUBLIC_POSTHOG_HOST,
      defaults: '2026-01-30',
      __add_tracing_headers: [ window.location.host, 'localhost' ],
    });

    This adds the X-POSTHOG-DISTINCT-ID and X-POSTHOG-SESSION-ID headers to your requests, which you can later use on the server-side.

  10. 9

    Next steps

    Recommended

    Now that you've set up PostHog for React Router, you can start capturing events and exceptions in your app.

    To get the most out of PostHog, you should familiarize yourself with the following:

    • PostHog Web SDK docs: Learn more about the PostHog Web SDK and how to use it on the client-side.

    • PostHog Node SDK docs: Learn more about the PostHog Node SDK and how to use it on the server-side.

    • Identify users: Learn more about how to identify users in your app.

    • Group analytics: Learn more about how to use group analytics in your app.

    • PostHog AI: After capturing events, use PostHog AI to help you understand your data and build insights.

    • Feature flags and experiments: Feature flag and experiment setup is the same as React. You can find more details in the React integration guide.

Community questions

Ask a question

Was this page useful?

HelpfulCould be better

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.

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/react-react-router-7-data · 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 or PostHog.

Download ZIP

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