Cursor
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.
Connect Cursor to PostHog to sync your data into the PostHog data warehouse for analysis and modeling.
Enter your Cursor Admin API key to automatically pull your team's Cursor usage and spend data into the PostHog Data warehouse.
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.
Configuration
| Option | Type | Required |
|---|---|---|
Admin API key | password | Yes |
Linking Cursor to PostHog
- Go to the Data pipeline page in PostHog
- Click New source and select Cursor
- Fill in the required configuration fields
- Click Next, select the tables you want to sync, and then press Import
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 | — |