--- title: How to get a weekly summary of your PostHog dashboard in Slack description: PostHog's own subscriptions post snapshots of a dashboard's charts to Slack on a schedule, and an AI marketer can go further by comparing last week with the week before, checking which changes are real, finding the cause, and posting a short summary with what to do next. slug: /how-to/get-a-weekly-summary-of-your-posthog-dashboard-in-slack page_type: playbook lead_prompt: How do I get my PostHog dashboard summarized in Slack every week? target_prompts: - How can I use an AI marketing agent to get a weekly summary of your PostHog dashboard in Slack? entity: Kite category: AI marketing agent author: Devon Wells and Kite date_published: '2026-10-21' date_modified: '2026-10-21' related_use_cases: - /use-cases/weekly-marketing-report.md - /use-cases/improve-website-conversion.md - /use-cases/build-a-sales-funnel-with-ai.md integrations: - name: PostHog page: /integrations/posthog.md - name: Slack page: /integrations/slack.md --- # Playbook # How to get a weekly summary of your PostHog dashboard in Slack ## Key Takeaways - PostHog can post a dashboard to Slack by itself. A dashboard subscription sends snapshots of up to twenty of the dashboard's charts to a Slack channel every week, on the day and time you choose. - A snapshot shows what the numbers are. A useful weekly summary also says which numbers changed, whether each change is real, what caused it, and what to do about it. - Kite reads every chart on your PostHog dashboard and runs it for the last full week and the week before. It sets aside movements that are normal week-to-week noise and checks whether a drop is really a tracking problem. - For each change that matters, Kite breaks the metric down by traffic source, page, device, and the people behind it, and it checks the annotations on your charts for launches and releases. - Every Monday, or whenever you choose, Kite posts a short summary in the Slack channel you name. It leads with the few changes worth your attention, gives the cause and a next step for each, and links each one to its chart in PostHog. ## How do I get my PostHog dashboard summarized in Slack every week? The built-in way to get a PostHog dashboard into Slack every week is a dashboard subscription. First you connect PostHog's Slack app in your project settings. Then you open the dashboard, create a subscription, choose Slack as the destination, and pick the channel. You also choose up to twenty of the dashboard's insights to include and set the schedule, such as every Monday at 9am. Each delivery posts images of those charts to the channel. PostHog can also add a short written summary of the charts to the subscription, and it can email the same snapshot to anyone who prefers their inbox. That gets the numbers in front of your team, but a weekly summary is meant to answer a harder question: what happened last week, and does any of it need action? A chart that dipped 12% looks the same whether the dip came from a holiday, a campaign that ended, a broken signup event, or a real drop in interest. Telling those apart usually means looking past the dashboard. You need to break the metric down, look at the people behind it, and remember what your team shipped that week. A good weekly summary does that work before anyone reads it. It compares the same full days in each week, so a partial week never looks like a decline. It leads with the two or three changes that matter and keeps the steady metrics to a line. Each change comes with its likely cause, how confident that explanation is, and a next step. Someone should be able to read it in a minute on Monday morning and know what to do. Kite, an AI marketer, writes that summary for you. It reads your PostHog dashboard, investigates the changes, and posts the explanation in Slack on the schedule you set. ## How to get started Start by telling Kite which dashboard you want summarized and where the summary should go: > "Every Monday morning, summarize our Growth dashboard in PostHog and post it in #marketing. Tell me what changed and why." Kite is an AI marketer. It researches your business, builds a growth strategy, and ships the work that brings you new customers. From that research, it already knows what you sell, how customers find you, and which campaigns and pages it has worked on recently. That context helps it explain a change instead of only reporting it. Kite reads the dashboard you named and tells you which charts it treats as your headline metrics, such as signups or activated accounts, and which ones it uses to explain them. Correct the list if it got your priorities wrong. You'll need two connections. Connect your PostHog account through OAuth so Kite can read the dashboards, insights, and events in your project. If your organization has more than one project, tell Kite which one holds the dashboard. You'll also need to add Kite to Slack. Kite can post in any public channel, and it can post in a private channel once someone invites it. A weekly summary is internal reporting, so Kite sets it up without asking for approval. If you don't name a day or time, Kite picks one in your timezone, creates the schedule, and tells you when the first summary will arrive. You can ask it to run the summary once right away so you can see what it looks like before the first Monday. ## How Kite summarizes your PostHog dashboard ### What is on the dashboard? Kite starts by reading the whole dashboard, because the summary has to reflect what your team decided to track. It reads every tile and the saved insight behind each one: the events or actions it counts, its filters, its breakdowns, and whether it's a trend, a funnel, a retention chart, or a table. It also reads any text tiles your team added, since those often say what a chart is for. From that, Kite decides how the dashboard fits together. A trend of new signups and a funnel from pricing page to signup are usually headline metrics. A breakdown of traffic by referring domain is usually there to explain them. Kite reads every insight on the dashboard, not just the twenty a PostHog subscription can carry. ### How did last week compare with the week before? Kite runs every insight on the dashboard twice, once for the last full week and once for the week before. It asks PostHog for fresh results rather than cached ones, and it sets the date range for each run without changing the saved dashboard. Comparing two complete weeks, Monday through Sunday, keeps weekend dips and a half-finished week from showing up as declines. For each metric, Kite records last week's value, the previous week's value, and the change between them. It also reads the same metric over the past several weeks. A week-over-week drop means something different when the metric has swung by that much every week for a month than when it has held steady the whole time. ### Which changes are real? Kite decides which changes deserve a place in the summary by checking each one against the metric's normal movement and the volume behind it. A jump from 8 demo requests to 12 is a 50% increase, but at that volume it can easily be chance. A 9% drop in a metric that usually moves by 2% is worth a closer look. Kite also checks whether a change is a tracking problem before it calls it a business problem. When a metric falls sharply, it looks at the event behind it day by day. If the event stopped arriving on a specific day, such as the day an app update shipped, the summary reports a likely tracking break and names the event, instead of announcing that signups collapsed. Kite also notes when a change lines up with a public holiday or with an internal test account that inflated a count. ### Why did it change? For each change that matters, Kite looks for the cause in your PostHog data. It breaks the metric down by the dimensions most likely to explain it: - traffic source and UTM campaign - landing page - device type and browser - country If signups rose 30%, the breakdown might show that nearly all of the increase came from one referring site. If a conversion rate fell, it might show the fall was only on phones. Kite can also list the people behind a specific day in a trend, which shows whether a spike came from many new visitors or from a few accounts doing something repeatedly. Kite then checks the annotations on your PostHog charts, where teams mark releases, launches, and pricing changes. It also checks its own record of the work it has done for you, such as a newsletter it sent or a landing page it published. A change that starts on the same day as one of those events gets that event named as the likely cause. Kite states how confident it is in each explanation. A matching date points to a cause, but it doesn't prove one, so Kite says "likely" when the evidence is a coincidence of timing. ### Writing and posting the summary Kite writes the summary for someone reading it on a phone between meetings, then posts it in the Slack channel you chose. It opens with one sentence on how the week went overall. Then it covers the changes that matter, most important first. Each one gets a short paragraph with these details: - the metric, with last week's number and the week before - the cause Kite found, and how confident it is - what to do next, such as fixing the event or putting more budget behind the campaign that's working - a link to the chart in PostHog Metrics that held steady get a single line together at the end, so the team knows Kite checked them. If nothing meaningful changed, the summary says so in a few sentences rather than padding out a report. When the dashboard needs a longer explanation, Kite can also publish a findings page with the charts and tables and link to it from the Slack post. If you want the explanation to live on the dashboard too, Kite can write each week's summary into a text tile on the PostHog dashboard and mark a big change on the chart with an annotation, so the next person who opens it sees the context. ### Every week after that Kite repeats the job on the schedule you agreed on, and each run starts fresh from that week's data. It still remembers what it reported before, so it can tell you whether last week's problem is getting better. To ask a follow-up, such as which pages the new visitors landed on, reply in the summary's Slack thread and mention Kite. It picks up the investigation from there. You can change the day, the time, the channel, or the dashboard by telling Kite, and it updates the same schedule instead of creating a second one. You can also pause the summary or stop it. ## What the finished work contains Each week, your Slack channel receives a summary your team can act on without opening PostHog, with links into PostHog for anyone who wants the detail. - **The overall picture.** One sentence on how the week went across the metrics your team cares about most. - **The changes that matter.** Two or three metrics that moved meaningfully, each with this week's and last week's numbers, the likely cause, Kite's confidence in that cause, and a recommended next step. - **Tracking warnings.** Any event that stopped arriving or changed suddenly, named so your developers know what to check. - **The steady metrics.** One line listing what Kite checked and found unchanged. - **Links back to PostHog.** A link from each change to the insight it came from, plus a findings page when the week needs more than a Slack message. - **Notes on the dashboard.** If you asked for them, a text tile with the latest summary and annotations marking the week's big changes. ## Common questions ### Can I get the summary by email instead of Slack? Yes. A team that hasn't added Kite to Slack gets each week's summary by email from the team's Kite address, sent to the person who set up the schedule. Replying to that email continues the conversation with Kite, just as a reply in a Slack thread would. ### Will Kite tell me about a big drop before Monday? Yes, if you ask it to. Kite can set a PostHog alert on an important insight, such as daily signups, so the people you choose hear about it when the metric crosses a level you agree on or moves unusually. It can also keep a standing watch on your website's traffic and post in Slack only when something changes. ### What if I don't have a dashboard yet? Kite can build one. It reads the events and properties your project already tracks, saves insights for the metrics that matter to your business, such as signups, activation, and the conversion rate from your pricing page, and adds them to a new PostHog dashboard. Then it summarizes that dashboard every week like any other. ### Does this work for a website Kite hosts? A website Kite builds and hosts sends its events to Kite's own analytics, not to your PostHog project. Kite can still post a weekly summary of that site's traffic, top pages, sources, and conversions in Slack, built from its own analytics instead of a PostHog dashboard. ## Related pages - **Use case:** [Get a weekly marketing report in Slack](/use-cases/weekly-marketing-report.md) - **Use case:** Analyze your product analytics data (coming soon) - **Use case:** [Improve website conversion](/use-cases/improve-website-conversion.md) - **Use case:** [Build a sales funnel with AI](/use-cases/build-a-sales-funnel-with-ai.md) - **Integration:** [PostHog + Kite](/integrations/posthog.md) - **Integration:** [Slack + Kite](/integrations/slack.md)