livepeer / livepeer/livepeer-data-mcp
[Feedback] :thumbsup: positive — cohort member retention vs non-cohort users
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
## Feedback (positive)
**Question:** cohort member retention vs non-cohort users
**Tool:** `query`
**Dataset:** `dbt.cohorts, dbt.cohort_members`
### Notes
Cohort membership data lives in dbt.cohorts and dbt.cohort_members (not in semantic schema, not discoverable via list_datasets). dbt.cohorts has cohort_id, cohort_name, track, start_date, end_date. dbt.cohort_members has cohort_id, track, user_email. Join to scope_cloud_events on user_email and to posthog_events on daydream_user_email.
---
_Feedback ID: `7305b429-8945-4934-90e6-2c77e28952d5` | Recorded at 2026-03-09T20:54:50.738Z_
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the `query` tool and inspect how `dbt.cohorts` and `dbt.cohort_members` are exposed, since the feedback says they are not discoverable through `list_datasets`. Trace the joins to `scope_cloud_events` and `posthog_events`; done means the requested cohort-member versus non-cohort retention analysis is supported or the limitation is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100