Linking Cursor 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 Cursor connector syncs members, daily usage, usage events, 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 Cursor Admin API key to automatically pull your team's Cursor usage and spend data.
You need a Cursor team plan (Business or Enterprise). A team admin can create an API key in the Cursor dashboard under Settings → Cursor Admin API Keys.
You'll be asked for:
- Admin API key: for example
key_....
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 Cursor tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
Admin API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
members | Current team members with their roles. Full refresh only | Full refresh | — | — |
daily_usage | Per-user daily usage metrics (lines accepted, tabs, agent requests). Only syncs the last 365 days on initial sync | Incremental, Full refresh | date | — |
usage_events | Per-request usage events with model, token usage, and cost. Only syncs the last 365 days on initial sync | Incremental, Full refresh | timestamp | — |
spend | Per-member spend for the current billing cycle. Full refresh only | Full refresh | — | — |
agent_edits | Daily team totals for agent-suggested edits: diffs suggested, accepted, and rejected, with line counts. Needs a Cursor Enterprise plan. Only syncs the last 365 days on initial sync | Incremental, Full refresh | event_date | — |
tabs | Daily team totals for Tab autocomplete: suggestions, accepts, rejects, and line counts. Needs a Cursor Enterprise plan. Only syncs the last 365 days on initial sync | Incremental, Full refresh | event_date | — |
dau | Daily count of team members who used an AI feature, with the CLI, cloud agent, and Bugbot counts alongside. Needs a Cursor Enterprise plan. Only syncs the last 365 days on initial sync | Incremental, Full refresh | date | — |
models | Daily team model usage, with a message count and a user count for each model. Needs a Cursor Enterprise plan. Only syncs the last 365 days on initial sync | Incremental, Full refresh | date | — |
top_file_extensions | Daily team file extension breakdown of AI-assisted edits, top five extensions per day. Needs a Cursor Enterprise plan. Only syncs the last 365 days on initial sync | Incremental, Full refresh | event_date | — |
by_user_agent_edits | Per-user daily agent edit metrics, keyed by email so they join to members. Needs a Cursor Enterprise plan. Only syncs the last 365 days on initial sync | Incremental, Full refresh | event_date | — |
by_user_tabs | Per-user daily Tab autocomplete metrics, keyed by email so they join to members. Needs a Cursor Enterprise plan. Only syncs the last 365 days on initial sync | Incremental, Full refresh | event_date | — |
by_user_models | Per-user daily model usage, with a message count for each model. Needs a Cursor Enterprise plan. Only syncs the last 365 days on initial sync | Incremental, Full refresh | date | — |
by_user_top_file_extensions | Per-user daily file extension breakdown of AI-assisted edits. Needs a Cursor Enterprise plan. Only syncs the last 365 days on initial sync | Incremental, Full refresh | event_date | — |
ai_code_commits | Per-commit attribution of lines added and deleted to Tab, Composer, and non-AI authoring. Needs a Cursor Enterprise plan with AI code tracking enabled. Only syncs the last 365 days on initial sync | Incremental, Full refresh | commitTs | — |
ai_code_changes | Individual accepted AI changes with the lines added and deleted, the model, and the files each change touched. Needs a Cursor Enterprise plan with AI code tracking enabled. Only syncs the last 365 days on initial sync | Incremental, Full refresh | createdAt | — |
Troubleshooting
- If the connection fails with an authorization error, the admin 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.