Connect PostHog to Rig

    Sync PostHog events, persons, cohorts, feature flags and dashboards into Rig, so product usage sits beside revenue and support data. PostHog connects with a personal API key and your project ID.

    Before you start

    • You need a PostHog account that can see the project you want to sync. A personal API key reaches what its owner can reach.
    • Know your region. US cloud projects live on us.posthog.com, EU cloud projects on eu.posthog.com, and self-hosted projects on your own domain.

    Step 1: Create a PostHog personal API key

    1. Sign in to PostHog and open your account settings.
    2. Go to the Personal API keys section.
    3. Click Create a personal API Key and name it, for example Rig.
    4. Choose the scopes for the key. PostHog recommends only the scopes you need, so pick read access to the data Rig syncs.
    5. Copy the key. A personal API key starts with phx_.

    Find your project ID
    Open Settings and then Project in PostHog. The numeric Project ID is on that page.

    Step 2: Connect it in Rig

    Adding a source needs a workspace owner, or a role with the Manage connections permission, on a workspace where you manage your own connections. If the Connectors tab says “Data ingestion for this workspace is managed by Rig”, ask an owner or Rig support to add the source.

    1. In Rig, open Connections, choose the Connectors tab and go to Sources & actions.
    2. Search for PostHog, open the card and click Connect.
    3. Personal API key: paste the key you created.
    4. Project ID: enter the numeric project ID.
    5. PostHog host: leave it as https://us.posthog.com for US cloud. Use https://eu.posthog.com for EU cloud, or your own URL when self-hosted.
    6. Click Continue. Rig checks the credentials and lists the streams it can reach, so choose the ones you want and click Connect.
    7. The source then syncs on its schedule, which is nightly unless you change it. To load data straight away, click Sync on its row; Test pulls a small sample first if you want to check the connection.

    What Rig pulls in

    PostHog lands in its own posthog schema in your warehouse:

    • Events: every captured event with its properties, read through PostHog's query endpoint so the history is complete and resumable.
    • Persons: people and their distinct IDs, in a child table.
    • Cohorts: your saved cohorts.
    • Feature flags: flag definitions.
    • Dashboards: dashboard definitions.

    Events sync incrementally by timestamp and merge on the event ID.

    Good to know

    • PostHog limits its query endpoint to 2,400 requests an hour and most analytics endpoints to 240 a minute. A first sync of a busy project can take a while.
    • Event properties are flattened into columns, but only two levels deep. Deeper nesting stays inside the parent column.
    • A personal API key belongs to a person. If its owner leaves the PostHog organisation, create a new key and update the source in Rig.
    • To disconnect PostHog, click the bin icon on the source's row under Sources & actions. Only whoever connected the source or a workspace owner can do this, and data already synced stays in the warehouse.

    What people use this for

    • Analyse funnels and conversion drop-off
    • Measure feature adoption and flag impact
    • Track activation and time to value
    • Measure retention and returning users

    More ideas for using PostHog

    Was this guide helpful?