livepeer / livepeer/livepeer-data-mcp
[Feedback] :pencil2: correction — How do scope cloud WAU numbers compare to PostHog scope_stream_started numbers?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
## Feedback (correction)
**Question:** How do scope cloud WAU numbers compare to PostHog scope_stream_started numbers?
**Tool:** `query`
**Dataset:** `scope_cloud_events, posthog_events, user_daily_engagement`
### Corrected answer
scope_stream_started is injected from rt_scope__cloud_events into posthog_events as a synthetic event. The gap between ClickHouse stream_started and PostHog scope_stream_started is identity resolution — some Scope users aren't matched to a PostHog person_id via person_to_user_ref. user_daily_engagement uses external identified users only and is the canonical WAU source. ClickHouse cloud events will always run slightly higher due to unmatched users.
### Notes
User clarified that scope cloud stream_started events are injected into PostHog as scope_stream_started. The two sources should theoretically be the same event. Remaining gap is identity resolution via person_to_user_ref. user_daily_engagement has_scope_streaming is the right canonical WAU metric.
---
_Feedback ID: `8d5684fe-8dbd-4d85-bf0a-63e9bced486b` | Recorded at 2026-03-11T00:40:47.700Z_
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 by reviewing the query and the three named datasets: scope_cloud_events, posthog_events, and user_daily_engagement. Confirm how scope_stream_started and has_scope_streaming are compared, then document or test the corrected relationship and identity-resolution gap; no file or test entry point is provided.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clickhouse
- Domain
- analytics, data
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100