Skip to content
Telemetry
For Cursor users adding event logging to their apps

Cursor Telemetry setup

Paste this prompt into Cursor to add event tables, track signup steps, and build dashboards.

This guide helps Cursor add analytics to your own application. For the editor's data-sharing controls, see Cursor's privacy settings.

Reviewed by the Telemetry product team on . We checked the event fields, suggested queries, and data to exclude. Who reviews this page

Instrument Cursor workflowsCopy the prompt

Reuse the same reviewed instructions across repositories with the agent telemetry skill.md guide.

Why this works
  • Works with React, API routes, workers, and server actions.
  • The prompt asks Cursor to keep event names, table names, and fields consistent across the repo.
  • Asks Cursor to build an activation and retention dashboard from the events it adds.
How to test this use case

Measure Cursor Telemetry setup and check the results

To measure cursor telemetry setup, choose one workflow and its owner. Define the events, test them with known inputs, and write a query that answers a specific question.

  1. 1

    Choose when to log

    Paste the setup prompt into Cursor with your Telemetry API key.

  2. 2

    Capture the outcome

    Begin with marketing_cta_clicked, register_success, onboarding_step_completed and document the grain of each event.

  3. 3

    Check the stored rows

    Use Telemetry to check funnel dropoff and return behavior.

  4. 4

    Make the decision

    Which CTA source sends users who activate?

Agent prompt

Paste this into your coding agent

Replace YOUR_API_KEY after signup, then ask the agent to run the product flow and verify the first events.

agent prompt

Cursor Telemetry setup setup prompt

text
Instrument the acquisition and revenue funnel with Telemetry.

Use /skill.md and this Telemetry API key: YOUR_API_KEY

Please add structured events for:
1. Marketing page views, CTA clicks, pricing plan selection, docs CTA clicks, and prompt copies.
2. Registration attempts, successful registrations, onboarding steps, team creation, first API key creation, and first telemetry event received.
3. Checkout start, checkout success, plan changes, billing portal opens, and payment failures.
4. Activation milestones: first table created, first query run, first dashboard created, first alert created, and second active day.

Create a dashboard for visitor to signup, signup to activated team, activated team to paid, and weekly retention by activation milestone.

Create the API key for this prompt, preview a working agent event, and replace the sample when your application is ready.

Open this setup free

Setup steps

  1. 1Paste the setup prompt into Cursor with your Telemetry API key.
  2. 2Tell Cursor which user workflow you want to measure.
  3. 3Have Cursor add events and run the flow locally.
  4. 4Use Telemetry to check funnel dropoff and return behavior.

Events to capture

marketing_cta_clickedregister_successonboarding_step_completedfirst_event_receivedquery_rundashboard_created

Questions you can answer

  • Which CTA source sends users who activate?
  • Where do new users leave onboarding?
  • Which features correlate with week-two retention?

Example event schemas

Event schemas for this workflow

Check what each event records, when to send it, and which field types it needs. Review the example payload and privacy checklist before using it in production.

Product lifecycle7 fields

user_signed_up

One accepted signup per user and account.

View schema
Product analytics8 fields

product_milestone_completed

One completed milestone per actor, account, and occurrence.

View schema

Use these queries in Telemetry

Learn about Dashboards

Save a product or revenue query to a dashboard your team can check.

Explore DashboardsRead customer stories

Related SQL recipes

More SQL recipes

Run the query using this workflow's event fields and check the example result. Save the result to a dashboard or set up an alert.

Browse all recipes
Product analyticsIntermediate

Build a signup-to-activation funnel in SQL

Where do new users leave before reaching first value?

Open recipe
Product analyticsAdvanced

Calculate weekly cohort retention

What percentage of each signup cohort returns in weeks one through twelve?

Open recipe
Product analyticsAdvanced

Find features used before upgrade

Which features are most commonly adopted before an account upgrades?

Open recipe
Recipe collectionsProduct analytics SQL

Next step

Create the API key your agent will use

The free plan is enough to run the prompt, send test events, and review the first dashboard.

Prompt packInstrument Cursor workflows

Related pages

AI agent telemetry and observability

Record agent runs and tool calls in Telemetry tables. Query retries, latency, cost, failures, and whether users accepted the results.

Open page

Claude Code observability

Ask Claude Code to add event logging while it implements a feature, then verify the events in Telemetry.

Open page

Codex instrumentation prompt

Ask Codex to add product events, verify that they arrive, and report which workflows still need logging.

Open page