Generated banner for Integration Javascript Web
Generated logo for Integration Javascript Web

Integration Javascript Web

PostHogOfficialCreated by PostHog

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

From the author

PostHog integration for client-side web JavaScript applications using posthog-js
— the description by PostHog

AutoGineer summary

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

This skill provides a systematic, four-phase workflow for developers to integrate PostHog analytics into JavaScript web applications. It emphasizes best practices such as using environment variables for configuration, maintaining minimal code changes, and ensuring proper user identification and error tracking. The skill guides the user through planning event tracking, implementing capture calls, revising the implementation, and concluding the setup, while strictly adhering to data privacy guidelines regarding PII.

What it does

  • Provides a step-by-step procedure for setting up PostHog in web projects.
  • Guides the creation of an event tracking plan via a JSON configuration file.
  • Ensures correct implementation of user identification and session management.
  • Directs the addition of error tracking at critical application boundaries.
  • Enforces security best practices like avoiding hardcoded keys and PII in event properties.
  • Facilitates correlation between client-side and server-side event data.

When to use it

  • When you need to add PostHog analytics to a new or existing JavaScript web application.
  • When you want to ensure your analytics implementation follows standard industry patterns.
  • When you need to track user behavior across both client-side and server-side environments.
  • When you need to implement robust error tracking alongside standard event capture.

Advantages

  • Promotes consistent and maintainable analytics code across the project.
  • Reduces the risk of exposing sensitive user data (PII) in event properties.
  • Ensures critical business events are captured on both client and server sides.
  • Provides a clear, repeatable process for scaling analytics coverage.

Usage examples

“Integrate PostHog into my React web application.”
The agent will initiate the four-phase workflow, starting with an analysis of your project structure to create a .posthog-events.json plan before implementing the tracking code.
“How do I identify users in my PostHog setup?”
The agent will guide you to use posthog.identify() during login and signup, ensuring you pass the correct user properties while maintaining session correlation.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/posthog/integration-javascript-web/download
  2. Unzip it into the cross-client skills folder of your project:

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

Documentation by PostHog

PostHog integration for JavaScript Web

This skill helps you add PostHog analytics to JavaScript Web 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/js.md - JavaScript web - docs

  • references/posthog-js.md - PostHog JavaScript web SDK

  • 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

  • Remember that source code is available in the node_modules directory

  • Check package.json for type checking or build scripts to validate changes

  • posthog-js is the JavaScript SDK package name

  • posthog.init() MUST be called before any other PostHog methods (capture, identify, etc.)

  • posthog-js is browser-only — do NOT import it in Node.js or server-side contexts (use posthog-node instead)

  • Autocapture is ON by default with posthog-js (tracks clicks, form submissions, pageviews). Do NOT disable autocapture unless the user explicitly requests it.

  • NEVER send PII in posthog.capture() event properties — no emails, full names, phone numbers, physical addresses, IP addresses, or user-generated content

  • PII belongs in posthog.identify() person properties (email, name, role), NOT in capture() event properties

  • Call posthog.identify(userId, { email, name, role }) on login AND on page refresh if the user is already logged in

  • Call posthog.reset() on logout to unlink future events from the current user

  • For SPAs without a framework router, capture pageviews with posthog.capture($pageview) or use the capture_pageview history_change option in init for History API routing

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/posthog-js.md

PostHog JavaScript Web SDK

SDK Version: 1.363.4

Posthog-js allows you to automatically capture usage and send events to PostHog.

Categories

  • Initialization

  • Identification

  • Capture

  • Surveys

  • Error tracking

  • LLM analytics

  • Privacy

  • Session replay

  • Feature flags

  • Toolbar

PostHog

This is the SDK reference for the PostHog JavaScript Web SDK. You can learn more about example usage in the JavaScript Web SDK documentation. You can also follow framework specific guides to integrate PostHog into your project. This SDK is designed for browser environments. Use the PostHog Node.js SDK for server-side usage.

Other methods
PostHog()

Release Tag: public

Constructs a new instance of the PostHog class

Returns
  • any

Examples
// Generated example for PostHog
posthog.PostHog();

Release Tag: public

Returns the explicit consent status of the user.

Notes:

This can be used to check if the user has explicitly opted in or out of data capturing, or neither. This does not take the default config options into account, only whether the user has made an explicit choice, so this can be used to determine whether to show an initial cookie banner or not.

Returns

Union of:

  • 'granted'

  • 'denied'

  • 'pending'

Examples
const consentStatus = posthog.get_explicit_consent_status()
if (consentStatus === "granted") {
    // user has explicitly opted in
} else if (consentStatus === "denied") {
    // user has explicitly opted out
} else if (consentStatus === "pending"){
    // user has not made a choice, show consent banner
}

get_session_id()

Release Tag: public

Returns the current session_id.

Notes:

This should only be used for informative purposes. Any actual internal use case for the session_id should be handled by the sessionManager.

Returns
  • string

Examples
// Generated example for get_session_id
posthog.get_session_id();

push()

Release Tag: public

push() keeps the standard async-array-push behavior around after the lib is loaded. This is only useful for external integrations that do not wish to rely on our convenience methods (created in the snippet).

Parameters
  • item (SnippetArrayItem) - A [function_name, args...] array to be executed

Returns
  • void

Examples
posthog.push(['register', { a: 'b' }]);

Identification methods
alias()

Release Tag: public

Creates an alias linking two distinct user identifiers. Learn more about identifying users

Notes:

PostHog will use this to link two distinct_ids going forward (not retroactively). Call this when a user signs up to connect their anonymous session with their account.

Parameters
  • alias (string) - A unique identifier that you want to use for this user in the future.

  • original? (string) - The current identifier being used for this user.

Returns

Union of:

  • CaptureResult

  • void

  • number

Examples
// link anonymous user to account on signup
posthog.alias('user_12345')
explicit alias with original ID
// explicit alias with original ID
posthog.alias('user_12345', 'anonymous_abc123')

createPersonProfile()

Release Tag: public

Creates a person profile for the current user, if they don't already have one and config.person_profiles is set to 'identified_only'. Produces a warning and does not create a profile if config.person_profiles is set to 'never'. Learn more about person profiles

Returns
  • void

Examples
posthog.createPersonProfile()

get_distinct_id()

Release Tag: public

Returns the current distinct ID for the user.

Notes:

This is either the auto-generated ID or the ID set via identify(). The distinct ID is used to associate events with users in PostHog.

Returns
  • string

Examples
get the current user ID
// get the current user ID
const userId = posthog.get_distinct_id()
console.log('Current user:', userId)
use in loaded callback
// use in loaded callback
posthog.init('token', {
    loaded: (posthog) => {
        const id = posthog.get_distinct_id()
        // use the ID
    }
})

get_property()

Release Tag: public

Returns the value of a super property. Returns undefined if the property doesn't exist.

Notes:

get_property() can only be called after the PostHog library has finished loading. init() has a loaded function available to handle this automatically.

Parameters
  • property_name (string) - The name of the super property you want to retrieve

Returns

Union of:

  • Property

  • undefined

Examples
// grab value for '$user_id' after the posthog library has loaded
posthog.init('<YOUR PROJECT TOKEN>', {
    loaded: function(posthog) {
        user_id = posthog.get_property('$user_id');
    }
});

getGroups()

Release Tag: public

Returns the current groups.

Returns
  • Record<string, any>

Examples
// Generated example for getGroups
posthog.getGroups();

getSessionProperty()

Release Tag: public

Returns the value of the session super property named property_name. If no such property is set, getSessionProperty() will return the undefined value.

Notes:

This is based on browser-level sessionStorage, NOT the PostHog session. getSessionProperty() can only be called after the PostHog library has finished loading. init() has a loaded function available to handle this automatically.

Parameters
  • property_name (string) - The name of the session super property you want to retrieve

Returns

Union of:

  • Property

  • undefined

Examples
// grab value for 'user_id' after the posthog library has loaded
posthog.init('YOUR PROJECT TOKEN', {
    loaded: function(posthog) {
        user_id = posthog.getSessionProperty('user_id');
    }
});

group()

Release Tag: public

Associates the user with a group for group-based analytics. Learn more about groups

Notes:

Groups allow you to analyze users collectively (e.g., by organization, team, or account). This sets the group association for all subsequent events and reloads feature flags.

Parameters
  • groupType (string) - Group type (example: 'organization')

  • groupKey (string) - Group key (example: 'org::5')

  • groupPropertiesToSet? (Properties) - Optional properties to set for group

Returns
  • void

Examples
associate user with an organization
// associate user with an organization
posthog.group('organization', 'org_12345', {
    name: 'Acme Corp',
    plan: 'enterprise'
})
associate with multiple group types
// associate with multiple group types
posthog.group('organization', 'org_12345')
posthog.group('team', 'team_67890')

identify()

Release Tag: public

Associates a user with a unique identifier instead of an auto-generated ID. Learn more about identifying users

Notes:

By default, PostHog assigns each user a randomly generated distinct_id. Use this method to replace that ID with your own unique identifier (like a user ID from your database).

Parameters
  • new_distinct_id? (string) - A string that uniquely identifies a user. If not provided, the distinct_id currently in the persistent store (cookie or localStorage) will be used.

  • userPropertiesToSet? (Properties) - Optional: An associative array of properties to store about the user. Note: For feature flag evaluations, if the same key is present in the userPropertiesToSetOnce, it will be overwritten by the value in userPropertiesToSet.

  • userPropertiesToSetOnce? (Properties) - Optional: An associative array of properties to store about the user. If property is previously set, this does not override that value.

Returns
  • void

Examples
basic identification
// basic identification
posthog.identify('user_12345')
identify with user properties
// identify with user properties
posthog.identify('user_12345', {
    email: '[email protected]',
    plan: 'premium'
})
identify with set and set_once properties
// identify with set and set_once properties
posthog.identify('user_12345',
    { last_login: new Date() },  // updates every time
    { signup_date: new Date() }  // sets only once
)

onSessionId()

Release Tag: public

Register an event listener that runs whenever the session id or window id change. If there is already a session id, the listener is called immediately in addition to being called on future changes. Can be used, for example, to sync the PostHog session id with a backend session.

Parameters
  • callback (SessionIdChangedCallback) - The callback function will be called once a session id is present or when it or the window id are updated.

Returns
  • () => void

Examples
posthog.onSessionId(function(sessionId, windowId) { // do something })

reset()

Release Tag: public

Resets all user data and starts a fresh session. ⚠️ Warning: Only call this when a user logs out. Calling at the wrong time can cause split sessions. This clears: - Session ID and super properties - User identification (sets new random distinct_id) - Cached data and consent settings

Parameters
  • reset_device_id? (boolean)

Returns
  • void

Examples
reset on user logout
// reset on user logout
function logout() {
    posthog.reset()
    // redirect to login page
}
reset and generate new device ID
// reset and generate new device ID
posthog.reset(true)  // also resets device_id

resetGroups()

Release Tag: public

Resets only the group properties of the user currently logged in. Learn more about groups

Returns
  • void

Examples
posthog.resetGroups()

setInternalOrTestUser()

Release Tag: public

Marks the current user as a test user by setting the $internal_or_test_user person property to true. This also enables person processing for the current user. This is useful for using in a cohort your internal/test filters for your posthog org.

Returns
  • void

Examples
// Manually mark as test user
posthog.setInternalOrTestUser()

// Or use internal_or_test_user_hostname config for automatic detection
posthog.init('token', { internal_or_test_user_hostname: 'localhost' })

setPersonProperties()

Release Tag: public

Sets properties on the person profile associated with the current distinct_id. Learn more about identifying users

Notes:

Updates user properties that are stored with the person profile in PostHog. If person_profiles is set to identified_only and no profile exists, this will create one.

Parameters
  • userPropertiesToSet? (Properties) - Optional: An associative array of properties to store about the user. Note: For feature flag evaluations, if the same key is present in the userPropertiesToSetOnce, it will be overwritten by the value in userPropertiesToSet.

  • userPropertiesToSetOnce? (Properties) - Optional: An associative array of properties to store about the user. If property is previously set, this does not override that value.

Returns
  • void

Examples
set user properties
// set user properties
posthog.setPersonProperties({
    email: '[email protected]',
    plan: 'premium'
})
set properties
// set properties
posthog.setPersonProperties(
    { name: 'Max Hedgehog' },  // $set properties
    { initial_url: '/blog' }   // $set_once properties
)

Surveys methods
cancelPendingSurvey()

Release Tag: public

Cancels a pending survey that is waiting to be displayed (e.g., due to a popup delay).

Parameters
  • surveyId (string)

Returns
  • void

Examples
// Generated example for cancelPendingSurvey
posthog.cancelPendingSurvey();

canRenderSurvey()

Release Tag: deprecated

Checks the feature flags associated with this Survey to see if the survey can be rendered. This method is deprecated because it's synchronous and won't return the correct result if surveys are not loaded. Use canRenderSurveyAsync instead.

Parameters
  • surveyId (string) - The ID of the survey to check.

Returns

Union of:

  • SurveyRenderReason

  • null

Examples
// Generated example for canRenderSurvey
posthog.canRenderSurvey();

canRenderSurveyAsync()

Release Tag: public

Checks the feature flags associated with this Survey to see if the survey can be rendered.

Parameters
  • surveyId (string) - The ID of the survey to check.

  • forceReload? (boolean) - If true, the survey will be reloaded from the server, Default: false

Returns
  • Promise<SurveyRenderReason>

Examples
posthog.canRenderSurveyAsync(surveyId).then((result) => {
    if (result.visible) {
        // Survey can be rendered
        console.log('Survey can be rendered')
    } else {
        // Survey cannot be rendered
        console.log('Survey cannot be rendered:', result.disabledReason)
    }
})

displaySurvey()

Release Tag: public

Display a survey programmatically as either a popover or inline element.

Parameters
  • surveyId (string) - The survey ID to display

  • options? (DisplaySurveyOptions) - Display configuration

Returns
  • void

Examples
Display as popover (respects all conditions defined in the dashboard)
// Display as popover (respects all conditions defined in the dashboard)
posthog.displaySurvey('survey-id-123')
Display inline in a specific element
// Display inline in a specific element
posthog.displaySurvey('survey-id-123', {
  displayType: DisplaySurveyType.Inline,
  selector: '#survey-container'
})
Force display ignoring conditions and delays
// Force display ignoring conditions and delays
posthog.displaySurvey('survey-id-123', {
  displayType: DisplaySurveyType.Popover,
  ignoreConditions: true,
  ignoreDelay: true
})

getActiveMatchingSurveys()

Release Tag: public

Get surveys that should be enabled for the current user. See fetching surveys documentation for more details.

Parameters
  • callback (SurveyCallback) - The callback function will be called when the surveys are loaded or updated.

  • forceReload? (boolean) - Whether to force a reload of the surveys.

Returns
  • void

Examples
posthog.getActiveMatchingSurveys((surveys) => {
     // do something
})

getSurveys()

Release Tag: public

Get list of all surveys.

Parameters
  • callback (SurveyCallback) - Function that receives the array of surveys

  • forceReload? (boolean) - Optional boolean to force an API call for updated surveys

Returns
  • void

Examples
function callback(surveys, context) {
  // do something
}

posthog.getSurveys(callback, false)

onSurveysLoaded()

Release Tag: public

Register an event listener that runs when surveys are loaded. Callback parameters: - surveys: Survey[]: An array containing all survey objects fetched from PostHog using the getSurveys method - context: isLoaded: boolean, error?: string : An object indicating if the surveys were loaded successfully

Parameters
  • callback (SurveyCallback) - The callback function will be called when surveys are loaded or updated.

Returns
  • () => void

Examples
posthog.onSurveysLoaded((surveys, context) => { // do something })

renderSurvey()

Release Tag: deprecated

Although we recommend using popover surveys and display conditions, if you want to show surveys programmatically without setting up all the extra logic needed for API surveys, you can render surveys programmatically with the renderSurvey method. This takes a survey ID and an HTML selector to render an unstyled survey.

Parameters
  • surveyId (string) - The ID of the survey to render.

  • selector (string) - The selector of the HTML element to render the survey on.

Returns
  • void

Examples
posthog.renderSurvey(coolSurveyID, '#survey-container')

Capture methods
capture()

Release Tag: public

Captures an event with optional properties and configuration.

Notes:

You can capture arbitrary object-like values as events. Learn about capture best practices

Parameters
  • event_name (EventName) - The name of the event (e.g., 'Sign Up', 'Button Click', 'Purchase')

  • properties? (Properties | null) - Properties to include with the event describing the user or event details

  • options? (CaptureOptions) - Optional configuration for the capture request

Returns

Union of:

  • CaptureResult

  • undefined

Examples
// basic event capture
posthog.capture('cta-button-clicked', {
    button_name: 'Get Started',
    page: 'homepage'
})

on()

Release Tag: public

Exposes a set of events that PostHog will emit. e.g. eventCaptured is emitted immediately before trying to send an event Unlike onFeatureFlags and onSessionId these are not called when the listener is registered, the first callback will be the next event after registering a listener Available events: - eventCaptured: Emitted immediately before trying to send an event - featureFlagsReloading: Emitted when feature flags are being reloaded (e.g. after identify(), group(), or reloadFeatureFlags())

Parameters
  • event ('eventCaptured' | 'featureFlagsReloading') - The event to listen for.

  • cb ((...args: any[]) => void) - The callback function to call when the event is emitted.

Returns
  • () => void

Examples
posthog.on('eventCaptured', (event) => {
  console.log(event)
})
Track when feature flags are reloading to show a loading state
// Track when feature flags are reloading to show a loading state
posthog.on('featureFlagsReloading', () => {
  console.log('Feature flags are being reloaded...')
})

register_for_session()

Release Tag: public

Registers super properties for the current session only.

Notes:

Session super properties are automatically added to all events during the current browser session. Unlike regular super properties, these are cleared when the session ends and are stored in sessionStorage.

Parameters
  • properties (Properties) - An associative array of properties to store about the user

Returns
  • void

Examples
register session-specific properties
// register session-specific properties
posthog.register_for_session({
    current_page_type: 'checkout',
    ab_test_variant: 'control'
})
register properties for user flow tracking
// register properties for user flow tracking
posthog.register_for_session({
    selected_plan: 'pro',
    completed_steps: 3,
    flow_id: 'signup_flow_v2'
})

register_once()

Release Tag: public

Registers super properties only if they haven't been set before.

Notes:

Unlike register(), this method will not overwrite existing super properties. Use this for properties that should only be set once, like signup date or initial referrer.

Parameters
  • properties (Properties) - An associative array of properties to store about the user

  • default_value? (Property) - Value to override if already set in super properties (ex: 'False') Default: 'None'

  • days? (number) - How many days since the users last visit to store the super properties

Returns
  • void

Examples
register once-only properties
// register once-only properties
posthog.register_once({
    first_login_date: new Date().toISOString(),
    initial_referrer: document.referrer
})
override existing value if it matches default
// override existing value if it matches default
posthog.register_once(
    { user_type: 'premium' },
    'unknown'  // overwrite if current value is 'unknown'
)

register()

Release Tag: public

Registers super properties that are included with all events.

Notes:

Super properties are stored in persistence and automatically added to every event you capture. These values will overwrite any existing super properties with the same keys.

Parameters
  • properties (Properties) - properties to store about the user

  • days? (number) - How many days since the user's last visit to store the super properties

Returns
  • void

Examples
register a single property
// register a single property
posthog.register({ plan: 'premium' })
register multiple properties
// register multiple properties
posthog.register({
    email: '[email protected]',
    account_type: 'business',
    signup_date: '2023-01-15'
})
register with custom expiration
// register with custom expiration
posthog.register({ campaign: 'summer_sale' }, 7) // expires in 7 days

unregister_for_session()

Release Tag: public

Removes a session super property from the current session.

Notes:

This will stop the property from being automatically included in future events for this session. The property is removed from sessionStorage.

Parameters
  • property (string) - The name of the session super property to remove

Returns
  • void

Examples
// remove a session property
posthog.unregister_for_session('current_flow')

unregister()

Release Tag: public

Removes a super property from persistent storage.

Notes:

This will stop the property from being automatically included in future events. The property will be permanently removed from the user's profile.

Parameters
  • property (string) - The name of the super property to remove

Returns
  • void

Examples
// remove a super property
posthog.unregister('plan_type')

Error tracking methods
captureException()

Release Tag: public

Capture a caught exception manually

Parameters
  • error (unknown) - The error to capture

  • additionalProperties? (Properties) - Any additional properties to add to the error event

Returns

Union of:

  • CaptureResult

  • undefined

Examples
Capture a caught exception
// Capture a caught exception
try {
  // something that might throw
} catch (error) {
  posthog.captureException(error)
}
With additional properties
// With additional properties
posthog.captureException(error, {
  customProperty: 'value',
  anotherProperty: ['I', 'can be a list'],
  ...
})

startExceptionAutocapture()

Release Tag: public

turns exception autocapture on, and updates the config option capture_exceptions to the provided config (or true)

Parameters
  • config? (ExceptionAutoCaptureConfig) - optional configuration option to control the exception autocapture behavior

Returns
  • void

Examples
Start with default exception autocapture rules. No-op if already enabled
// Start with default exception autocapture rules. No-op if already enabled
posthog.startExceptionAutocapture()
Start and override controls
// Start and override controls
posthog.startExceptionAutocapture({
  // you don't have to send all of these (unincluded values will use the default)
  capture_unhandled_errors: true || false,
  capture_unhandled_rejections: true || false,
  capture_console_errors: true || false
})

stopExceptionAutocapture()

Release Tag: public

turns exception autocapture off by updating the config option capture_exceptions to false

Returns
  • void

Examples
// Stop capturing exceptions automatically
posthog.stopExceptionAutocapture()

LLM analytics methods
captureTraceFeedback()

Release Tag: public

Capture written user feedback for a LLM trace. Numeric values are converted to strings.

Parameters
  • traceId (string | number) - The trace ID to capture feedback for.

  • userFeedback (string) - The feedback to capture.

Returns
  • void

Examples
// Generated example for captureTraceFeedback
posthog.captureTraceFeedback();

captureTraceMetric()

Release Tag: public

Capture a metric for a LLM trace. Numeric values are converted to strings.

Parameters
  • traceId (string | number) - The trace ID to capture the metric for.

  • metricName (string) - The name of the metric to capture.

  • metricValue (string | number | boolean) - The value of the metric to capture.

Returns
  • void

Examples
// Generated example for captureTraceMetric
posthog.captureTraceMetric();

Privacy methods
clear_opt_in_out_capturing()

Release Tag: public

Clear the user's opt in/out status of data capturing and cookies/localstorage for this PostHog instance

Returns
  • void

Examples
// Generated example for clear_opt_in_out_capturing
posthog.clear_opt_in_out_capturing();

has_opted_in_capturing()

Release Tag: public

Checks if the user has opted into data capturing.

Notes:

Returns the current consent status for event tracking and data persistence.

Returns
  • boolean

Examples
if (posthog.has_opted_in_capturing()) {
    // show analytics features
}

has_opted_out_capturing()

Release Tag: public

Checks if the user has opted out of data capturing.

Notes:

Returns the current consent status for event tracking and data persistence.

Returns
  • boolean

Examples
if (posthog.has_opted_out_capturing()) {
    // disable analytics features
}

is_capturing()

Release Tag: public

Checks whether the PostHog library is currently capturing events. Usually this means that the user has not opted out of capturing, but the exact behaviour can be controlled by some config options. Additionally, if the cookieless_mode is set to 'on_reject', we will capture events in cookieless mode if the user has explicitly opted out.

Returns
  • boolean

Examples
// Generated example for is_capturing
posthog.is_capturing();

opt_in_capturing()

Release Tag: public

Opts the user into data capturing and persistence.

Notes:

Enables event tracking and data persistence (cookies/localStorage) for this PostHog instance. By default, captures an $opt_in event unless disabled.

Parameters
  • options? ({ captureEventName?: EventName | null | false; /** event name to be used for capturing the opt-in action */ captureProperties?: Properties; /** set of properties to be captured along with the opt-in action */ })

Returns
  • void

Examples
simple opt-in
// simple opt-in
posthog.opt_in_capturing()
opt-in with custom event and properties
// opt-in with custom event and properties
posthog.opt_in_capturing({
    captureEventName: 'Privacy Accepted',
    captureProperties: { source: 'banner' }
})
opt-in without capturing event
// opt-in without capturing event
posthog.opt_in_capturing({
    captureEventName: false
})

opt_out_capturing()

Release Tag: public

Opts the user out of data capturing and persistence.

Notes:

Disables event tracking and data persistence (cookies/localStorage) for this PostHog instance. If opt_out_persistence_by_default is true, SDK persistence will also be disabled.

Returns
  • void

Examples
// opt user out (e.g., on privacy settings page)
posthog.opt_out_capturing()

Initialization methods
debug()

Release Tag: public

Enables or disables debug mode for detailed logging.

Notes:

Debug mode logs all PostHog calls to the browser console for troubleshooting. Can also be enabled by adding ?__posthog_debug=true to the URL.

Parameters
  • debug? (boolean) - If true, will enable debug mode.

Returns
  • void

Examples
enable debug mode
// enable debug mode
posthog.debug(true)
disable debug mode
// disable debug mode
posthog.debug(false)

getPageViewId()

Release Tag: public

Returns the current page view ID.

Returns

Union of:

  • string

  • undefined

Examples
// Generated example for getPageViewId
posthog.getPageViewId();

init()

Release Tag: public

Initializes a new instance of the PostHog capturing object.

Notes:

All new instances are added to the main posthog object as sub properties (such as posthog.library_name) and also returned by this function. Learn more about configuration options

Parameters
  • token (string) - Your PostHog API token

  • config? (OnlyValidKeys<Partial<PostHogConfig>, Partial<PostHogConfig>>) - A dictionary of config options to override

  • name? (string) - The name for the new posthog instance that you want created

Returns
  • PostHog

Examples
basic initialization
// basic initialization
posthog.init('<ph_project_api_key>', {
    api_host: '<ph_client_api_host>'
})
multiple instances
// multiple instances
posthog.init('<ph_project_api_key>', {}, 'project1')
posthog.init('<ph_project_api_key>', {}, 'project2')

set_config()

Release Tag: public

Updates the configuration of the PostHog instance.

Parameters
  • config (Partial<PostHogConfig>) - A dictionary of new configuration values to update

Returns
  • void

Examples
// Generated example for set_config
posthog.set_config();

Session replay methods
get_session_replay_url()

Release Tag: public

Returns the Replay url for the current session.

Parameters
  • options? ({ withTimestamp?: boolean; timestampLookBack?: number; }) - Options for the url

Returns
  • string

Examples
// basic usage
posthog.get_session_replay_url()

@example

js // timestamp posthog.get_session_replay_url({ withTimestamp: true })


@example

js // timestamp and lookback posthog.get_session_replay_url({ withTimestamp: true, timestampLookBack: 30 // look back 30 seconds }) ```

sessionRecordingStarted()

Release Tag: public

returns a boolean indicating whether session recording is currently running

Returns
  • boolean

Examples
// Stop session recording if it's running
if (posthog.sessionRecordingStarted()) {
  posthog.stopSessionRecording()
}

startSessionRecording()

Release Tag: public

turns session recording on, and updates the config option disable_session_recording to false

Parameters
  • override? ({ sampling?: boolean; linked_flag?: boolean; url_trigger?: true; event_trigger?: true; } | true) - optional boolean to override the default sampling behavior - ensures the next session recording to start will not be skipped by sampling or linked_flag config. true is shorthand for sampling: true, linked_flag: true

Returns
  • void

Examples
Start and ignore controls
// Start and ignore controls
posthog.startSessionRecording(true)
Start and override controls
// Start and override controls
posthog.startSessionRecording({
  // you don't have to send all of these
  sampling: true || false,
  linked_flag: true || false,
  url_trigger: true || false,
  event_trigger: true || false
})

stopSessionRecording()

Release Tag: public

turns session recording off, and updates the config option disable_session_recording to true

Returns
  • void

Examples
// Stop session recording
posthog.stopSessionRecording()

Feature flags methods
getEarlyAccessFeatures()

Release Tag: public

Get the list of early access features. To check enrollment status, use isFeatureEnabled. Learn more in the docs

Parameters
  • callback (EarlyAccessFeatureCallback) - The callback function will be called when the early access features are loaded.

  • force_reload? (boolean) - Whether to force a reload of the early access features.

  • stages? (EarlyAccessFeatureStage[]) - The stages of the early access features to load.

Returns
  • void

Examples
const posthog = usePostHog()
const activeFlags = useActiveFeatureFlags()

const [activeBetas, setActiveBetas] = useState([])
const [inactiveBetas, setInactiveBetas] = useState([])
const [comingSoonFeatures, setComingSoonFeatures] = useState([])

useEffect(() => {
  posthog.getEarlyAccessFeatures((features) => {
    // Filter features by stage
    const betaFeatures = features.filter(feature => feature.stage === 'beta')
    const conceptFeatures = features.filter(feature => feature.stage === 'concept')

    setComingSoonFeatures(conceptFeatures)

    if (!activeFlags || activeFlags.length === 0) {
      setInactiveBetas(betaFeatures)
      return
    }

    const activeBetas = betaFeatures.filter(
            beta => activeFlags.includes(beta.flagKey)
        );
    const inactiveBetas = betaFeatures.filter(
            beta => !activeFlags.includes(beta.flagKey)
        );
    setActiveBetas(activeBetas)
    setInactiveBetas(inactiveBetas)
  }, true, ['concept', 'beta'])
}, [activeFlags])

getFeatureFlag()

Release Tag: public

Gets the value of a feature flag for the current user.

Notes:

Returns the feature flag value which can be a boolean, string, or undefined. Supports multivariate flags that can return custom string values.

Parameters
  • key (string)

  • options? (FeatureFlagOptions) - (optional) If send_event: false, we won't send an $feature_flag_call event to PostHog. If fresh: true, we won't return cached values from localStorage - only values loaded from the server.

Returns

Union of:

  • boolean

  • string

  • undefined

Examples
check boolean flag
// check boolean flag
if (posthog.getFeatureFlag('new-feature')) {
    // show new feature
}
check multivariate flag
// check multivariate flag
const variant = posthog.getFeatureFlag('button-color')
if (variant === 'red') {
    // show red button
}

getFeatureFlagPayload()

Release Tag: deprecated

Get feature flag payload value matching key for user (supports multivariate flags).

Parameters
  • key (string)

Returns
  • JsonType

Examples
if(posthog.getFeatureFlag('beta-feature') === 'some-value') {
     const someValue = posthog.getFeatureFlagPayload('beta-feature')
     // do something
}

getFeatureFlagResult()

Release Tag: public

Get a feature flag evaluation result including both the flag value and payload. By default, this method emits the $feature_flag_called event.

Parameters
  • key (string) - Key of the feature flag.

  • options? (FeatureFlagOptions) - Options for the feature flag lookup.

Returns

Union of:

  • FeatureFlagResult

  • undefined

Examples
const result = posthog.getFeatureFlagResult('my-flag')
if (result?.enabled) {
    console.log('Flag is enabled with payload:', result.payload)
}
multivariate flag
// multivariate flag
const result = posthog.getFeatureFlagResult('button-color')
if (result?.variant === 'red') {
    showRedButton(result.payload)
}

isFeatureEnabled()

Release Tag: public

Checks if a feature flag is enabled for the current user.

Notes:

Returns true if the flag is enabled, false if disabled, or undefined if not found. This is a convenience method that treats any truthy value as enabled.

Parameters
  • key (string)

  • options? (FeatureFlagOptions) - (optional) If send_event: false, we won't send an $feature_flag_call event to PostHog. If fresh: true, we won't return cached values from localStorage - only values loaded from the server.

Returns

Union of:

  • boolean

  • undefined

Examples
simple feature flag check
// simple feature flag check
if (posthog.isFeatureEnabled('new-checkout')) {
    showNewCheckout()
}
disable event tracking
// disable event tracking
if (posthog.isFeatureEnabled('feature', { send_event: false })) {
    // flag checked without sending $feature_flag_call event
}

onFeatureFlags()

Release Tag: public

Register an event listener that runs when feature flags become available or when they change. If there are flags, the listener is called immediately in addition to being called on future changes. Note that this is not called only when we fetch feature flags from the server, but also when they change in the browser.

Parameters
  • callback (FeatureFlagsCallback) - The callback function will be called once the feature flags are ready or when they are updated. It'll return a list of feature flags enabled for the user, the variants, and also a context object indicating whether we succeeded to fetch the flags or not.

Returns
  • () => void

Examples
posthog.onFeatureFlags(function(featureFlags, featureFlagsVariants, { errorsLoading }) {
    // do something
})

reloadFeatureFlags()

Release Tag: public

Feature flag values are cached. If something has changed with your user and you'd like to refetch their flag values, call this method.

Returns
  • void

Examples
posthog.reloadFeatureFlags()

resetGroupPropertiesForFlags()

Release Tag: public

Resets the group properties for feature flags.

Parameters
  • group_type? (string)

Returns
  • void

Examples
posthog.resetGroupPropertiesForFlags()

resetPersonPropertiesForFlags()

Release Tag: public

Resets the person properties for feature flags.

Returns
  • void

Examples
posthog.resetPersonPropertiesForFlags()

setGroupPropertiesForFlags()

Release Tag: public

Set override group properties for feature flags. This is used when dealing with new groups / where you don't want to wait for ingestion to update properties. Takes in an object, the key of which is the group type.

Parameters
  • properties ({ [type: string]: Properties; }) - The properties to override, the key of which is the group type.

  • reloadFeatureFlags? (boolean) - Whether to reload feature flags.

Returns
  • void

Examples
Set properties with reload
// Set properties with reload
posthog.setGroupPropertiesForFlags({'organization': { name: 'CYZ', employees: '11' } })
Set properties without reload
// Set properties without reload
posthog.setGroupPropertiesForFlags({'organization': { name: 'CYZ', employees: '11' } }, false)

setPersonPropertiesForFlags()

Release Tag: public

Sometimes, you might want to evaluate feature flags using properties that haven't been ingested yet, or were set incorrectly earlier. You can do so by setting properties the flag depends on with these calls:

Parameters
  • properties (Properties) - The properties to override.

  • reloadFeatureFlags? (boolean) - Whether to reload feature flags.

Returns
  • void

Examples
Set properties
// Set properties
posthog.setPersonPropertiesForFlags({'property1': 'value', property2: 'value2'})
Set properties without reloading
// Set properties without reloading
posthog.setPersonPropertiesForFlags({'property1': 'value', property2: 'value2'}, false)

updateEarlyAccessFeatureEnrollment()

Release Tag: public

Opt the user in or out of an early access feature. Learn more in the docs

Parameters
  • key (string) - The key of the feature flag to update.

  • isEnrolled (boolean) - Whether the user is enrolled in the feature.

  • stage? (string) - The stage of the feature flag to update.

Returns
  • void

Examples
const toggleBeta = (betaKey) => {
  if (activeBetas.some(
    beta => beta.flagKey === betaKey
  )) {
    posthog.updateEarlyAccessFeatureEnrollment(
      betaKey,
      false
    )
    setActiveBetas(
      prevActiveBetas => prevActiveBetas.filter(
        item => item.flagKey !== betaKey
      )
    );
    return
  }

  posthog.updateEarlyAccessFeatureEnrollment(
    betaKey,
    true
  )
  setInactiveBetas(
    prevInactiveBetas => prevInactiveBetas.filter(
      item => item.flagKey !== betaKey
    )
  );
}

const registerInterest = (featureKey) => {
  posthog.updateEarlyAccessFeatureEnrollment(
    featureKey,
    true
  )
  // Update UI to show user has registered
}

updateFlags()

Release Tag: public

Manually update feature flag values without making a network request. This is useful when you have feature flag values from an external source (e.g., server-side evaluation, edge middleware) and want to inject them into the client SDK.

Parameters
  • flags (Record<string, boolean | string>) - An object mapping flag keys to their values (boolean or string variant)

  • payloads? (Record<string, JsonType>) - Optional object mapping flag keys to their JSON payloads

  • options? ({ merge?: boolean; }) - Optional settings. Use { merge: true } to merge with existing flags instead of replacing.

Returns
  • void

Examples
// Replace all flags with server-evaluated values
posthog.updateFlags({
  'my-flag': true,
  'my-experiment': 'variant-a'
})

// Merge with existing flags (update only specified flags)
posthog.updateFlags(
  { 'my-flag': true },
  undefined,
  { merge: true }
)

// With payloads
posthog.updateFlags(
  { 'my-flag': true },
  { 'my-flag': { some: 'data' } }
)

Toolbar methods
loadToolbar()

Release Tag: public

returns a boolean indicating whether the toolbar loaded

Parameters
  • params (ToolbarParams)

Returns
  • boolean

Examples
// Generated example for loadToolbar
posthog.loadToolbar();

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

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/javascript_web · 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-javascript-web.zip