Telemetry
For teams that need activation, feature adoption, and retained-account data

Product Analytics for Retention

Use agent-installed structured events to learn which early actions create returning users and revenue-ready teams.

Get an API keyCopy the prompt
Why this works
  • Activation events tied to the actual first useful action in your app.
  • Feature adoption data that can be queried by team, plan, source, and cohort.
  • Retention milestones that make it easier to see which onboarding paths work.

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

Product Analytics for Retention setup prompt

text
Instrument product usage and retention with Telemetry.

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

Please add structured events for:
1. Signup, onboarding step completion, team creation, first successful integration, and first meaningful product action.
2. Core feature usage with feature_name, action, surface, team_id, user_id, status, latency_ms, and error_type when relevant.
3. Retention milestones: second active day, first saved dashboard, first shared artifact, first alert created, and first return after seven days.
4. Expansion signals: invited teammate, upgraded plan intent, billing page viewed, usage limit reached, and support requested.

Create a dashboard for activation rate, weekly active teams, feature adoption, retained teams by first action, and upgrade-intent events.

Setup steps

  1. 1Define the activation moment for the product.
  2. 2Ask an agent to instrument onboarding, core feature usage, and return events.
  3. 3Send test events for a new account and a returning account.
  4. 4Build dashboards for activation, weekly active teams, adoption, and upgrade intent.

Events to capture

onboarding_step_completedfirst_meaningful_action_completedfeature_useddashboard_savedteammate_invitedretention_milestone_reached

Questions unlocked

  • Which first action best predicts retained teams?
  • Which features are adopted by accounts that later upgrade?
  • Where does onboarding lose otherwise qualified users?

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 packStart free

Related pages

Claude Code Observability

Give Claude Code a prompt that makes telemetry part of the implementation pass instead of a separate cleanup project.

Open page

Cursor Telemetry Setup

A copyable setup prompt for adding event tables, funnel tracking, and dashboards from inside Cursor.

Open page

Codex Instrumentation Prompt

A focused prompt that asks Codex to instrument the rest of the product, verify events, and summarize coverage gaps.

Open page