Why this matters
Locked-feature views are demand signals. If many starter accounts repeatedly hit the same feature gate, that is either a pricing opportunity or a product packaging problem.
What you get
- Locked features ranked by demand
- Prompt click-through and conversion
- Accounts showing repeated expansion intent
- Packaging recommendations by plan
Walk through it
You
Which locked features are creating upgrade demand?
Agent
I’ll compare gate impressions to prompt clicks and later plan changes.
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.feature AS feature, properties.plan AS plan, countIf(event = 'feature_locked_viewed') AS locked_views, countIf(event = 'upgrade_prompt_clicked') AS prompt_clicks, count(DISTINCT properties.account_id) AS accounts FROM events WHERE event IN ('feature_locked_viewed','upgrade_prompt_clicked') AND timestamp > now() - INTERVAL 30 DAY GROUP BY feature, plan ORDER BY locked_views DESC LIMIT 30"The output
The agent returns feature gates with demand and likely action: improve copy, adjust entitlement, or route accounts to sales.
Setting it up
Emit events wherever the product blocks or upsells a feature. Include account and plan.
Variations
- “Show only accounts above 80% quota.”
- “Find features that get viewed but never upgraded.”
- “Draft pricing-page copy for the top gated feature.”