Feature Request: Dynamic Recap Generator ("Spotify Wrapped" as a Service)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 39.9k
- Forks
- 3.4k
- Avg merge
- 7h 27m
- Merged PRs (30d)
- 222
Description
Feature request
Is your feature request related to a problem? Please describe.
Currently, creating narrative-driven analytics (like a Quarterly Business Review for stakeholders or a "Year-in-Review" for end-users) requires exporting data out of PostHog and manually building slides or using external automation tools.
While Dashboards are great for monitoring, they lack the narrative structure required for storytelling, and they cannot easily be personalized dynamically for thousands of individual users at once.
Describe the solution you'd like
I propose a Dynamic Presentation Builder (or an evolution of Notebooks) that allows users to create slide-based reports populated by live PostHog insights.
Crucially, this feature should support Dynamic Variables (e.g., {person.id}) to allow for mass personalization.
Core Functionality:
- The "Slide" Builder (UI)
A drag-and-drop interface similar to Notebooks, but paginated into "slides."
Users can pull in saved Insights/SQL queries.
Support for "Themes" (CSS styling) to match branding.
- Dynamic Data Injection (The "Wrapped" Logic)
The ability to set a query variable (e.g., WHERE distinct_id = {target_user}) within the deck.
When generating the deck, PostHog iterates through a cohort of Identified Persons, populating the charts specific to that user.
- Distribution/Workflow Integration
Export: PDF or Public Link generation.
Webhooks/Email: The ability to trigger an email workflow where the payload includes a link to the user's specific "Year-in-Review" or a snapshot of their specific stats.
Use Cases
A. Internal: Automated Business Reviews (Owner Specific)
Goal: Automated QBRs/MBRs for internal stakeholders.
Content: High-level aggregate metrics.
Top Performing Customers (by revenue/events).
Most viewed vs. most converted products.
"Most active user who didn't convert" (Churn risk).
Frequency: Automated email to the Admin/Product team every Monday or Quarter.
B. External: User-Facing "Year-in-Review" (User Specific)
Goal: Viral marketing and retention (similar to Spotify Wrapped or Grammarly Insights).
Content: Personalized metrics injected via person.id.
"You spent X hours in the app this year."
"Your most used feature was Y."
"You ordered Z products."
Frequency: Annual or Quarterly emails sent to the customer base.
Why this is valuable?
Retention: "Gamified" usage stats are proven to increase user engagement.
stickiness: Moves PostHog from just an analytics tool to a communication/marketing enablement tool.
Time Savings: Eliminates manual reporting for product managers.
Additional context
From: https://posthoghelp.zendesk.com/agent/tickets/44394 (moved to PostHog: https://us.posthog.com/project/2/support/tickets/46711)
Debug info
Kind: feedback
Target area: analytics
Report event: http://go/ticketByUUID/b1786092-2f0c-4e66-b822-c84311b60c9b
Session: https://us.posthog.com/project/sTMFPsFhdP1Ssg/replay/019aed33-5e1a-7b1c-8abf-26e9606e3e2c?t=816
Exceptions: https://us.posthog.com/project/2/error_tracking?filterGroup=%7B%22type%22%3A%22AND%22%2C%22values%22%3A%5B%7B%22type%22%3A%22AND%22%2C%22values%22%3A%5B%7B%22key%22%3A%22%24session_id%22%2C%22value%22%3A%5B%22019aed33-5e1a-7b1c-8abf-26e9606e3e2c%22%5D%2C%22operator%22%3A%22exact%22%2C%22type%22%3A%22event%22%7D%5D%7D%5D%7D
Location: https://eu.posthog.com/project/64467/insights
Persons-on-events mode for project: person_id_override_properties_on_events
Contributor guide
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
The issue does not identify repository files, tests, or entry points to inspect. Start by locating the existing Notebooks, Insights, export, and workflow-integration implementations, then define a narrower milestone with explicit completion criteria before attempting the full feature.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, sql
- Domain
- analytics, api, backend, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100