Activation and Retention Event Template

Template evidence path

Activation And Retention Template: implementation to decision

Treat the prompt as an implementation brief. The useful artifact is not copied code alone, but a reviewed event contract that produces a trustworthy answer.

1
Select the boundary
Instrument the point where signup_completed becomes final.
2
Create the contract
Start with signup_completed, onboarding_step_completed, first_meaningful_action_completed and keep every field typed, bounded, and privacy-reviewed.
3
Run a fixture
Exercise known success, failure, retry, and empty-result cases before relying on aggregate results.
4
Answer the question
Which first action predicts week-two retention?

Template versus use case

This page is the implementation brief

Copy this template when the measurement goal is already clear. Use the matching use-case guide to review event boundaries, success definitions, and the decisions the resulting SQL should support.

Read Product Analytics for Retention

Template

Paste this into your coding agent

Replace YOUR_API_KEY, run the flow locally, then verify the generated events and dashboards.

activation-retention

Activation And Retention Template

text

Instrument product activation and retention with Telemetry.

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

Log signup, onboarding, first successful integration, first meaningful action, core feature usage, invited teammate, dashboard/shared artifact creation, billing page viewed, upgrade intent, and seven-day return.

Create dashboards for visitor to signup, signup to activated account, activation to retained account, feature adoption, and upgrade-intent events by cohort.

Keep event names and properties consistent across client, server, and worker surfaces.

Events to capture

signup_completedonboarding_step_completedfirst_meaningful_action_completedfeature_usedretention_milestone_reached

Verification checklist

What a complete instrumentation pass leaves behind

Events

Synthetic events reach the intended table with stable names and field types.

Queries

The first SQL queries return plausible rows with an explicit time window.

Views

A dashboard uses the real fields and includes enough context to explain a change.

Safety

Prompts, bodies, credentials, signatures, and private content were checked for redaction.

Event schema starting points

Review the row grain, emit boundary, required types, privacy classes, example payload, and validation checklist before adapting a query or snippet to production.

Product lifecycle7 fields