Cursor Integration Guide

Span's AI Tool Adoption Report provides visibility into how your engineering organization uses AI coding assistants like Cursor. This API integration automatically tracks Cursor usage metrics, helping you understand adoption patterns, measure AI impact on productivity, and identify opportunities for improvement.

How is Cursor activity attributed to users? 

To count towards AI usage for Cursor, one of these actions must be taken: 

• Interacting with Agent / Ask functionality.

• Accepting tab suggestions.

What Data is Collected

Span collects the following daily usage metrics from Cursor:

• Accepted Lines of Code: Total lines of code accepted from Cursor suggestions

• Tab Completions: Number of accepted tab completions (converted to line equivalents)

• Active Usage Days: Days when each developer actively used Cursor

• User Activity: Which team members are using Cursor and how frequently

All metrics are tied to individual developer email addresses and automatically mapped to your Span organization members.

Setup Instructions

Prerequisites

• Organization admin access in Span

• Admin access to your Cursor team account

• A valid Cursor API key

Step 1: Generate Cursor API Key

1. Navigate to API Settings or Integration Settings

2. Generate a new API key for Span integration, make sure it has an "admin" scope.

3. Copy the API key (you'll need it in the next step)

See here for more info from Cursor.

Step 2: Configure Integration in Span

1. Navigate to Organization Settings → Integrations 

2. Find and select Cursor from the list of AI tools

3. Click Connect or Set Up Integration

4. In the authentication dialog, paste your Cursor API key

5. Click Verify & Connect

Span will validate your credentials by connecting to the Cursor API. Once validated, the integration is automatically configured.

Step 3: Initial Data Sync

After successful connection:

• The first data sync begins immediately, pulling the last 90 days of Cursor usage data (configurable)

• Subsequent syncs run automatically every night at 2:30 AM UTC

• Initial sync may take a few minutes depending on your team size and usage history

Step 4: Email Mapping

For accurate metrics, Cursor user emails must match emails in your Span organization:

• Span automatically maps Cursor users to organization members by email

• Email mappings sync nightly to ensure accuracy

Available Metrics

Once connected, the following metrics become available in the AI Tool Adoption Report:

Adoption Metrics

Impact Metrics

Viewing Your AI Tool Adoption Report

Accessing the Report

Navigate to Insights → AI Transformation → Adoption

1. Select your desired date range

2. Filter by Developer Tool to view Cursor-specific metrics

3. Additional filters available: Team, Person, IC Level

Report Sections

AI Tools Impact Summary

• High-level overview of Cursor adoption across your organization

• Shows total active users, code generated, and adoption trends

Active Users Charts

• Time-series visualization of weekly and monthly active users

• Trend lines help identify adoption growth or decline

Code Ratio Chart

• Percentage of code from Cursor over time

• Compare AI-generated code vs. manually written code

Active Users Breakdown Grid

• Detailed breakdown by individual developer or team

• Drill-down capability to explore specific adoption patterns

• Sort and filter to identify power users or low adopters

Understanding the Data

How Metrics are Calculated

• Line Counting: Cursor tab completions are converted to line equivalents using a 2:1 ratio (each tab ≈ 2 lines)

• Active Day Definition: Any day where a developer accepted at least one Cursor suggestion

• Code Percentage: Calculated as (Accepted AI Lines / Total Merged Lines) × 100

• Weekly/Monthly Windows: Rolling windows based on your selected date range

Data Freshness

• Cursor usage data syncs nightly at 2:30 AM UTC

• Metrics typically reflect activity up to the previous day

• Initial historical sync pulls up to 90 days of past data

Best Practices

Maximizing Adoption Insights

1. Regular Monitoring: Check the report weekly to track adoption trends

2. Team Comparisons: Compare Cursor usage across teams to identify best practices

3. Identify Champions: Find power users who can mentor others

4. Track Onboarding: Monitor new team members' adoption patterns

5. Measure ROI: Correlate AI code percentage with cycle time improvements

Troubleshooting Common Issues

Problem: No data appearing after setup

• Solution: Verify your Cursor API key is still valid

• Solution: Check that Cursor user emails match Span organization member emails

• Solution: Wait for the first nightly sync to complete (up to 24 hours)

Problem: Some team members not showing in the report

• Solution: Ensure their Cursor email matches their email in Span

• Solution: Configure multi-domain email mapping if your org uses multiple domains

• Solution: Verify they've actually used Cursor during the selected date range

Problem: Metrics seem lower than expected

• Solution: Check the date range bounds indicator at the top of the report

• Solution: Verify VCS integration (GitHub/GitLab) is properly configured for code ratio calculations

• Solution: Confirm developers are accepting Cursor suggestions (not just viewing them)

Privacy & Security

• Cursor API credentials are securely stored and encrypted

• Only aggregate usage metrics are collected (no code content)

• Data is partitioned by organization with strict access controls

• Email mappings respect your organization's privacy settings

• All data transmission uses secure HTTPS connections

Support

For additional assistance with Cursor integration:

• Contact your Span customer success manager

• Visit the Span Help Center for detailed guides

• Submit a support ticket through the in-app help menu