Track waitlist to activation

See which waitlist cohorts convert after invite, where they stall, and whether invite timing changes activation quality.

Published

difficulty beginner · time to value 4 minutes

Start from this

Analyze waitlist conversion: joined waitlist, invited, accepted invite, signed up, activated, and retained by cohort and acquisition source.

Why this matters

Waitlists create demand, but delayed access can cool intent. This playbook shows whether your invite cadence turns demand into activation.

What you get

  • Waitlist cohort conversion
  • Invite acceptance and signup rate
  • Activation after invite
  • Source quality and timing effects

Walk through it

You

How well does our waitlist convert after invites?

Agent

I’ll build a waitlist-to-activation funnel by cohort and source.

Endpoint: POST /v1/projects/:project_id/analytics/query
Exact shape: /v1/openapi.json?path=%2Fv1%2Fprojects%2F%7Bproject_id%7D%2Fanalytics%2Fquery&method=post
Custom HogQL goes in the OpenAPI-defined `query` field.
Concept fields:
  query: "SELECT properties.cohort AS cohort, properties.source AS source, countIf(event = 'waitlist_joined') AS joined, countIf(event = 'invite_accepted') AS accepted, countIf(event = 'activated') AS activated FROM events WHERE event IN ('waitlist_joined','invite_accepted','activated') GROUP BY cohort, source ORDER BY joined DESC"

The output

The agent returns cohort conversion and recommends whether to invite faster, change messaging, or segment by source.

Setting it up

Emit waitlist and invite lifecycle events. Preserve source and cohort through signup and activation.

Variations

  • “Compare invites sent within 7 days vs after 30 days.”
  • “Find sources with high waitlist joins but low activation.”
  • “Publish this for launch planning.”

Adapt this playbook in your own agent.

Ask your agent to map the starter prompt to your saved signal map, live events, and the current HTTP API before answering.

Set up Agentry in this repo by following https://agentry.sh/install.md. I authorize you to: run its device-code login and save the key to ~/.agentry/credentials.json, read this repo, propose an instrumentation plan for my approval, and edit code after I approve it.

+ Full access
5.5 Extra High
  1. 1. Open your repo in Codex, Claude Code, Cursor etc.
  2. 2. Paste the install prompt.
  3. 3. Your agent reads the install doc and shows you an implementation plan for approval.