Linking Google PageSpeed Insights 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 Google PageSpeed Insights connector syncs pagespeed desktop, pagespeed mobile, 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.
Enter your Google Cloud API key and the URLs you want to analyze to pull PageSpeed Insights (Lighthouse) scores.
Create an API key in the Google Cloud console and enable the PageSpeed Insights API for your project. A key raises your quota to 25,000 queries/day (400 per 100 seconds); without one, requests are heavily throttled.
There is no list endpoint - every request runs a fresh, on-demand analysis of a single URL - so enter one URL per line (starting with http:// or https://). For example:
Each analysis is a full Lighthouse run and can take several seconds. Each URL is analyzed once per selected table (desktop / mobile) per sync. To accumulate a history of scores over time, pick the append sync method on the table.
You'll be asked for:
- API key: for example
Your Google Cloud API key. - URLs: for example
https://posthog.com https://posthog.com/docs.
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 Google PageSpeed Insights tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
URLs | textarea | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
pagespeed_desktop | PageSpeed Insights / Lighthouse analysis under the desktop profile for each configured URL. One row per URL per sync; use append sync to accumulate a time series of scores. | Append only, Full refresh | analysis_timestamp | — |
pagespeed_mobile | PageSpeed Insights / Lighthouse analysis under the mobile profile for each configured URL. One row per URL per sync; use append sync to accumulate a time series of scores. | Append only, Full refresh | analysis_timestamp | — |
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.