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.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.

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