Linking Plausible as a source

The Plausible connector syncs your web analytics into PostHog, so you can analyze it alongside your product data. It works with both Plausible Cloud and self-hosted instances.

Prerequisites

You need a Plausible account with access to create an API key, and the domain of the site you want to sync.

Adding a data source

1. In PostHog, go to the Sources tab of the data pipeline section.
2. Click + New source and click Link next to this source.
3. Enter your credentials (see Configuration below) and click Next.
4. Select the tables you want to sync, choose a sync method and frequency, then click Import.

Once the syncs are complete, you can start querying this data in PostHog.

When linking Plausible, you'll need:

• API key – create an API key under Account settings → API keys with the stats read scope.
• Site domain – enter your site's domain (for example example.com).
• Host – self-hosted only. Set it to your instance URL (for example https://plausible.example.com). Leave it blank for Plausible Cloud.

Sync modes

Each table can be synced in one of several modes, depending on what the source supports:

• Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
• Incremental – only new or updated rows are synced on each run, using a cursor field (such as an updated_at timestamp). Cheaper than a full refresh, but deletes aren't captured.
• Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
• Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.

See sync methods for a full explanation of how each mode works and how to choose between them.

Configuration

Supported tables

The tables available from this source are discovered from your account when you connect it, so the exact list depends on your data. Once connected, you can pick which tables to sync from the sources tab.

Some tables are off by default. The operating_system_versions table is not synced unless you enable it, since the operating_systems table already covers most use cases.

Event-scoped tables – such as hostnames, pages, and custom property tables – don't include bounce_rate or visit_duration metrics. Plausible's API rejects these session-level metrics for event-scoped breakdowns.

Custom property tables

You can sync custom event properties from Plausible by adding a comma-separated list of property keys in the Custom property keys sync setting (for example plan, signup_method). Each key creates its own table named custom_property_<key>.

Plausible's Stats API can't list a site's property keys, so you need to enter them manually. Your Plausible plan must include custom properties for this to work.

Troubleshooting

• If you see an invalid or revoked key error, create a new key in your Plausible account settings, then reconnect.
• If a table fails with a missing scope error, grant the stats read scope in your Plausible account settings, then reconnect.

If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.