Linking SpeedCurve 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 SpeedCurve connector syncs your synthetic monitoring data into the PostHog data warehouse: sites, monitored URLs, test results, deployments, notes, and performance budgets. This lets you correlate web performance with product usage and ship speed.
Prerequisites
- A SpeedCurve account with at least one site configured for synthetic monitoring.
- A SpeedCurve API key. Find it in SpeedCurve under Admin > Teams. An organization admin can access this page.
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.
You need one value to connect:
- API key - found under Admin > Teams in your SpeedCurve dashboard.
The connector uses SpeedCurve API v1. SpeedCurve's v2 API is still in beta and is not supported.
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.
The tests and deploys tables support incremental sync using the timestamp field (a Unix timestamp in seconds). All other tables are full refresh only.
Incremental sync defaults to a 24-hour lookback window. Changes older than 24 hours require a longer lookback or a full refresh to pick up.
The tests table covers up to the last 364 days of data. This stays within SpeedCurve's rolling twelve-month API retention limit.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
sites | Sites configured for synthetic monitoring in the SpeedCurve team. | Full refresh | — | site_id |
urls | Monitored URLs across the team's sites, with metadata for their latest tests. | Full refresh | — | site_id, url_id |
tests | Synthetic tests, including queued, failed, and successful tests, with available performance metrics. | Incremental, Full refresh | timestamp | test_id |
deploys | Deployments recorded in SpeedCurve, with their sites, timestamps, and notes. | Incremental, Full refresh | timestamp | deploy_id |
notes | Notes attached to the team's sites to explain changes in performance. | Full refresh | — | note_id |
budgets | Synthetic performance budgets from dashboards visible to the entire team, with their evaluation data. | Full refresh | — | budget_id |
Notes on specific tables
- tests - includes queued (status
-2), failed (status-1), and successful (status0) results. - budgets - only includes budgets from dashboards visible to the entire team. Private dashboard budgets are excluded.
- urls - each row includes the
site_idof the parent site so you can join URLs back to sites.
Note: RUM (Real User Monitoring) data is not included in this source. This connector covers synthetic monitoring only.
Troubleshooting
- "SpeedCurve rejected the API key" - the API key is wrong, expired, or the SpeedCurve account is inactive. Generate a new key under Admin > Teams and reconnect.
- "SpeedCurve denied access" - the API key doesn't have the right permissions for your team. Check the key's team permissions in SpeedCurve.
- Missing recent test data - incremental sync uses a 24-hour lookback by default. If you need older data, increase the lookback window or run a full refresh.
- No test data beyond 364 days - SpeedCurve's API only retains roughly twelve months of test data. Older results are not available through the API.
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.