Linking Similarweb as a source
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
This source is currently in alpha. The interface and available tables may change.
The Similarweb connector syncs visits, page views, pages per visit, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- 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.
Sync estimated traffic, engagement and audience data for any set of domains. Generate an API key under API management in your Similarweb account settings. The API is a paid add-on, and your plan decides which countries, metrics and history are available.
You'll be asked for:
- API key
- Domains: comma-separated list of domains to sync. Similarweb has no way to list the domains on your account, so every table is built from this list. At most 50.
- Granularity: daily and weekly data need a plan that includes them.
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_attimestamp). 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.
All Similarweb tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Description |
|---|---|
API keyType: password Required: True | |
DomainsType: text Required: True | Comma-separated list of domains to sync. Similarweb has no way to list the domains on your account, so every table is built from this list. At most 50. |
CountryType: text Required: False | Two-letter country code to report on, or |
GranularityType: select Required: True | Daily and weekly data need a plan that includes them. |
Start monthType: text Required: False | Earliest month to sync (YYYY-MM). Leave empty to sync only the most recent period. How far back you can go depends on your plan. |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
visits | Estimated desktop and mobile web visits per period for each configured domain | Incremental, Full refresh | date | — |
page_views | Estimated desktop and mobile web page views per period for each configured domain | Incremental, Full refresh | date | — |
pages_per_visit | Average number of pages viewed per visit, per period, for each configured domain | Incremental, Full refresh | date | — |
average_visit_duration | Average visit duration in seconds, per period, for each configured domain | Incremental, Full refresh | date | — |
bounce_rate | Share of visits that ended without further interaction, per period, for each configured domain | Incremental, Full refresh | date | — |
global_rank | Monthly worldwide traffic rank for each configured domain | Incremental, Full refresh | date | — |
traffic_sources | Visits split by marketing channel and organic/paid, per period, for each configured domain | Incremental, Full refresh | date | — |
traffic_by_country | Traffic share and engagement per visitor country, aggregated over the synced window | Full refresh | — | — |
Troubleshooting
- If the connection fails with an authorization error, the API key is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
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.