feat(engagement): surface the engaged state on the dashboard (#172)#236
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ADR-001 defines
engagedas "interacted with the post but did not click the external link", yet the state was never materialized: the Edge Function does not write it (by design) and the dashboard did not aggregate it. Add engaged_users to post_engagement_daily, aggregate it over the 30-day window and show it on each post's secondary line.Each engaged user is attributed to the day of their first interaction with the post, so summing the daily rows counts distinct users instead of doubling someone who interacted on several days. The materialized view is recreated (they cannot ALTER ... ADD COLUMN); the unique index, the hourly pg_cron job and the concurrent refresh all keep working.
Closes #172