AutoGineer
Generated banner for Integration Expo
Generated logo for Integration Expo

Integration Expo

PostHogOfficialCreated by PostHog

  • Skill
  • Tool integration
  • Data and AI
  • MIT
  • Low risk
Download ZIP

From the author

PostHog integration for Expo 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 implementing PostHog analytics within Expo-based React Native projects. It covers the full lifecycle of integration, from initial setup and configuration to advanced user identification, screen tracking, and error reporting. The skill emphasizes modern best practices, such as using environment variables for sensitive keys, leveraging Expo-specific configuration, and maintaining consistent event tracking patterns across both client-side and server-side logic.

What it does

  • Provides a step-by-step workflow for integrating PostHog into Expo projects.
  • Defines patterns for user identification during login and signup flows.
  • Outlines methods for manual screen tracking using Expo Router.
  • Details how to implement error tracking for critical user flows.
  • Specifies configuration requirements for environment variables and peer dependencies.
  • Includes reference patterns for consistent event naming and implementation.

When to use it

  • When you need to add product analytics to a new or existing Expo application.
  • When you want to ensure your PostHog integration follows established best practices for React Native.
  • When you need to track specific user actions, errors, or conversion funnels in an Expo project.
  • When you are setting up user identification and session correlation across client and server boundaries.

Advantages

  • Ensures consistent implementation patterns across the codebase.
  • Promotes secure handling of API keys via environment variables.
  • Provides clear guidance on handling Expo-specific routing and configuration.
  • Reduces integration errors by following a structured, multi-step process.

Usage examples

“How do I start integrating PostHog into my new Expo project?”
The agent will guide you through the initial setup, including dependency installation and the creation of an event tracking plan.
“How should I track user logins in my Expo app using PostHog?”
The agent will provide the identify pattern, showing how to use posthog.identify with user properties and session management.

Install

  1. Download the skill as a ZIP:

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

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

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

Documentation by PostHog

PostHog integration for Expo

This skill helps you add PostHog analytics to Expo 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 - Expo example project code

  • references/react-native.md - React native - 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

  • posthog-react-native is the React Native SDK package name (same as bare RN)

  • Use expo-constants with app.config.js extras for POSTHOG_PROJECT_TOKEN and POSTHOG_HOST (NOT react-native-config)

  • Access config via Constants.expoConfig?.extra?.posthogProjectToken in your posthog.ts config file

  • For expo-router, wrap PostHogProvider in app/_layout.tsx and manually track screens with posthog.screen(pathname, params) in a useEffect

  • posthog-react-native is the React Native SDK package name

  • Use react-native-config to load POSTHOG_PROJECT_TOKEN and POSTHOG_HOST from .env (variables are embedded at build time, not runtime)

  • react-native-svg is a required peer dependency of posthog-react-native (used by the surveys feature) and must be installed alongside it

  • Place PostHogProvider INSIDE NavigationContainer for React Navigation v7 compatibility

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.0-begin.md

title: PostHog Setup - Begin description: Start the event tracking setup process by analyzing the project and creating an event tracking plan

We're making an event tracking plan for this project.

Before proceeding, find any existing posthog.capture() code. Make note of event name formatting.

From the project's file list, select between 10 and 15 files that might have interesting business value for event tracking, especially conversion and churn events. Also look for additional files related to login that could be used for identifying users, along with error handling. Read the files. If a file is already well-covered by PostHog events, replace it with another option. Do not spawn subagents.

Look for opportunities to track client-side events.

IMPORTANT: Server-side events are REQUIRED if the project includes any instrumentable server-side code. If the project has API routes (e.g., app/api/**/route.ts) or Server Actions, you MUST include server-side events for critical business operations like:

  • Payment/checkout completion

  • Webhook handlers

  • Authentication endpoints

Do not skip server-side events - they capture actions that cannot be tracked client-side.

Create a new file with a JSON array at the root of the project: .posthog-events.json. It should include one object for each event we want to add: event name, event description, and the file path we want to place the event in. If events already exist, don't duplicate them; supplement them.

Track actions only, not pageviews. These can be captured automatically. Exceptions can be made for "viewed"-type events that correspond to the top of a conversion funnel.

As you review files, make an internal note of opportunities to identify users and catch errors. We'll need them for the next step.

Status

Before beginning a phase of the setup, you will send a status message with the exact prefix '[STATUS]', as in:

[STATUS] Checking project structure.

Status to report in this phase:

  • Checking project structure

  • Verifying PostHog dependencies

  • Generating events based on project

Upon completion, continue with: basic-integration-1.1-edit.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.

Security

What our scanner noticed· Low risk

  • Instructions that use the network

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/expo · 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-expo.zip