PostHog

Conversion Bridge adds your PostHog tracking code and sends conversion events directly to PostHog using posthog.capture(). Every event tracked by your WordPress plugin integrations is sent to PostHog with a custom label, value, and any additional data collected by the integration.

PostHog supports both cloud-hosted (US and EU regions) and self-hosted deployments. Conversion Bridge works with all of them.

Setting Up PostHog

1. Go to Conversion Bridge > Platforms and enable PostHog.
2. Enter your API Key. You can find this in your PostHog project settings.
3. Select your Host URL — choose US, EU, or Self-hosted depending on where your PostHog instance is running.
4. If you selected Self-hosted, enter your Host URL (the reverse proxy URL where PostHog receives data) and your UI Host URL (the URL where you log in to PostHog).
5. Configure any additional options (described in the sections below).
6. Click Save Changes to start tracking.

Person Profiles

PostHog uses person profiles to associate events with identified users. You can choose how Conversion Bridge configures this:

• Identified Only (default) — Person profiles are only created when a user is explicitly identified (e.g., when a logged-in user is tracked). Anonymous events are not linked to a profile.
• Always — Every event creates or updates a person profile, even for anonymous visitors.

Choose the option that matches your PostHog plan and privacy requirements.

Tracking Logged In Users

When you enable Track logged in users, Conversion Bridge identifies logged-in WordPress users in PostHog with their user ID, email address, and display name. This lets you tie conversion events to specific people in your PostHog dashboard.

This feature may have privacy implications — make sure it aligns with your site's privacy policy.

User Info

Some plugin integrations collect additional details about logged-in users — like membership plans, course enrollments, or subscription levels. When you enable Include user info, this data is sent to PostHog as super properties so it's included with every event on the page.

Learn more about User Info.

Persistence and Cookies

PostHog needs to persist data across page loads to track sessions and identify returning visitors. You can choose how it stores this data:

• Local Storage and CookiesA small piece of data stored in a user’s browser that helps websites remember user activity, preferences, or sessions across visits. (default) — Uses both localStorage and cookies. Best for most sites.
• Cookies — Uses cookies only.
• Local Storage — Uses localStorage only. No cookies are set.
• Session Storage — Data is cleared when the browser tab closes. No cookies are set.
• Memory — Data is only kept in memory and lost on every page load. No cookies are set.

If you're working toward a cookieless setup, choose Local Storage, Session Storage, or Memory. When one of these is selected, Conversion Bridge automatically marks PostHog as not using cookies for consent purposes.

Learn more about PostHog persistence.

Extra Properties

You can include additional WordPress data with every page view as PostHog super properties. These properties are registered once per page load and attached to all events on that page. Available properties:

• Author — The display name of the post/page author
• Category — The post categories (comma-separated)
• Tags — The post tags (comma-separated)
• Logged In — Whether the current visitor is logged in (yes or no)
• Role — The current user's WordPress role
• Language — The site language/locale
• Post Type — The current post type (e.g., post, page, product)

These properties show up in PostHog and can be used to filter and segment your analytics data.

No-Code Web Experiments (Beta)

PostHog offers no-code web experiments that let you run A/B tests directly from the PostHog toolbar without writing code. By default, this feature is opt-in.

When you enable this option in Conversion Bridge, it tells PostHog to allow toolbar-managed experiments on your site. You'll also need to enable the feature preview inside PostHog itself.

Dashboard Embed

PostHog lets you create shared dashboards with a public URL. If you paste your public dashboard URL into the Dashboard URL field, Conversion Bridge embeds it in your WordPress admin so you can view your PostHog analytics without leaving your site.

How Events Are Tracked

When a plugin integration detects an event (like a form submission or purchase), Conversion Bridge sends it to PostHog using posthog.capture(). Each event includes:

• A conversion label — the name of the event as it will appear in PostHog
• A conversion value — the monetary value (if applicable), along with the currency
• Additional properties — any extra data the integration collects, such as transaction IDs, item names, or customer details

Learn more about conversion labels and values.

All events appear in PostHog as custom events and can be used in funnels, trends, cohorts, and other PostHog tools.

Consent Handling

PostHog has native consent handling built in. When a cookie consent banner is active on your site and Conversion Bridge is managing consent signals for PostHog:

• PostHog loads with capturing opted out by default
• When a visitor grants analytics consent through your cookie banner, Conversion Bridge tells PostHog to opt in
• If a visitor denies consent, PostHog stays opted out and no data is collected

This uses PostHog's own opt_in_capturing and opt_out_capturing methods, so consent is handled natively rather than by blocking the script entirely.

Excluding the Script Tag

By default, Conversion Bridge adds the PostHog JavaScript snippet to your site. If you've already added PostHog through another method (another plugin, manual code, or a tag manager), you can check the Exclude script tag option to prevent Conversion Bridge from adding a duplicate. Conversion Bridge will still send conversion events to the existing PostHog instance on the page.