Product Analytics Engineer

What it does

Product Analytics Engineer is a Cursor agent playbook named analytics-engineer. AgenticKit installs it so a session can adopt this role instead of acting as a generic coding assistant.

The analytics-engineer agent equips your product with actionable telemetry. It implements standardized event taxonomies, server-side tracking, conversion funnels, and retention cohort tracking using PostHog, Mixpanel, or custom SQL views.

Sets up event tracking, funnel telemetry, PostHog, Segment, and Mixpanel. Analytics engineer for Cursor that implements privacy-friendly product telemetry, conversion funnels, event tracking, and dashboard schemas.

Why it exists

A pile of agent files is not a team. analytics-engineer exists so one job, product analytics engineer, has a written brief, required skills, and a stop condition.

It ships in the Engineering Kit. Skills it must read: Product Analytics & Funnel Tracking; Next.js App Router & Server Components; SaaS Architecture Patterns & Multi-Tenancy. Commands that adopt this role: /feature-spec: PRD & Product Feature Requirement Spec; /landing-fix: Landing Page CRO Audit & Copy Optimizer; /ship: End-to-End Feature Pipeline Shipper.

When to use it

• Tracking user onboarding funnels and conversion drop-offs
• Setting up product analytics without compromising privacy
• Building custom SQL retention and activation dashboards

When not to use it

• Do not ask analytics-engineer to do a different role's job. If you need a launch post, switch agents.
• Do not keep the same chat after this agent has finished its artifact. Start a reviewer in a new thread.
• Do not invoke every agent in the kit for a small change.

Example workflow

1. Install the Engineering Kit so .cursor/agents/analytics-engineer is on disk.
2. Run /feature-spec: PRD & Product Feature Requirement Spec, or start a chat and tell Cursor to adopt the analytics-engineer role.
3. The agent should read: Product Analytics & Funnel Tracking; Next.js App Router & Server Components; SaaS Architecture Patterns & Multi-Tenancy.
4. It produces the artifact for this role only, then stops.
5. A different agent or you review. Same-chat self-review is not a review.

Example usage

Example: "You are analytics-engineer. Tracking user onboarding funnels and conversion drop-offs. Read product-analytics before you edit."

Or let the pipeline invoke it: /feature-spec: PRD & Product Feature Requirement Spec.

Capabilities you should actually see: Standardized event tracking taxonomy design (Object-Action syntax)

Example output

• analytics-engineer should leave files or a written verdict, not a vibe check. Standardized event tracking taxonomy design (Object-Action syntax) PostHog, Mixpanel, and Google Analytics 4 integration
• Engineering agents should touch the slice they were given (schema, route, test, or review note) and nothing else.

Best practices

• Standardized event tracking taxonomy design (Object-Action syntax)
• PostHog, Mixpanel, and Google Analytics 4 integration
• Server-side event dispatch and client session attribution
• Funnel drop-off and user retention cohort analysis queries
• One role per chat unless a command is explicitly orchestrating a sequence.

Common mistakes

• Using analytics-engineer as a synonym for 'the Cursor agent'. It is a brief, not the product.
• Skipping the required skills and hoping the role name is enough.
• Letting the writer approve its own PR.
• Invoking this agent and three unrelated ones in the same prompt.