livepeer / livepeer/livepeer-data-mcp
[Feedback] :thumbsup: positive — Daydream user retention using meaningful core actions
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
## Feedback (positive)
**Question:** Daydream user retention using meaningful core actions
**Tool:** `query`
**Dataset:** `semantic.posthog_events`
### Notes
posthog_events.is_core_action (Bool) and core_action_name (String) are pre-computed and reliable for retention analysis. Core action names: api_stream_created, community_engagement, dashboard visit, logged in creator page visit, playground stream, project_published, scope_stream_started, sign up. Always exclude 'sign up' from return-event retention checks (it's the entry event). Join key to cohort_members: daydream_user_email = cohort_members.user_email. user_type='external' filter correctly excludes internal/anonymous users for cohort analysis.
---
_Feedback ID: `1dd7e9c3-aad6-4412-bc39-1e209337dc7b` | Recorded at 2026-03-09T21:54:13.255Z_
Contributor guide
No contributing guide indexed for this repository
Research direction
Review the `query` tool and the `semantic.posthog_events` dataset details recorded here, including the `is_core_action`, `core_action_name`, and cohort join requirements. The issue does not define a specific code change or completion condition, so the desired retention-analysis outcome needs clarification before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- analytics, data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100