--- title: PostHog + Kite description: Kite reads your PostHog funnels, web analytics, heatmaps, and session recordings to find where people stop converting, then sets up the experiments, surveys, cohorts, and email workflows that address it and measures the result in the same project. slug: /integrations/posthog page_type: integration primary_question: What can Kite do with PostHog? entity: Kite category: AI marketing agent author: Devon Wells and Kite date_published: '2026-10-05' date_modified: '2026-10-06' integration: name: PostHog categories: - analytics connection_types: - OAuth customer_account_requirement: required capabilities_verified: '2026-08-26' vendor_url: https://posthog.com related_use_cases: - /use-cases/improve-website-conversion.md --- # PostHog + Kite ## Key Takeaways - Kite reads your PostHog project to find where visitors and users stop converting. It works from your web analytics, funnels, paths, heatmaps, session recordings, and the people behind each drop-off. - Kite also acts in PostHog. It sets up experiments, creates surveys, builds cohorts, and writes the email workflows PostHog sends, and it asks for your approval before any of them reach real people. - Kite checks your campaign tracking too. It audits UTM tags and conversion goals so PostHog credits each signup to the campaign that brought it. - You connect your own PostHog account through OAuth and choose the project Kite works in. Websites that Kite builds and hosts come with their own analytics, so they don't need PostHog. Capabilities verified August 26, 2026. ## What PostHog is and how Kite uses it PostHog is a product analytics platform that records what people do on your website and in your product. It stores each pageview, click, and signup as an event, and it adds session recordings, heatmaps, experiments, surveys, and feature flags on top of that data. An AI marketing agent uses PostHog the way a growth marketer would. It reads the events to find where people stop converting, looks at what they did at that moment, and then tests a change and measures it in the same project. Kite runs that whole loop. It finds the step that loses people, works out why, and sets up the experiment, survey, or email that addresses it. Then it reads the same numbers again to see whether more people got through. You connect your own PostHog account through OAuth. ## Marketing jobs Kite can do with PostHog PostHog holds both halves of conversion work: the record of what people did, and the tools that change what they see next. The jobs below follow that order. They start with reading your traffic, move through finding and explaining a leak, and end with fixing it and keeping your team informed. ### See where your traffic comes from and where it lands Kite reads PostHog's web analytics to give you a current picture of your site's traffic. It pulls visitors, pageviews, sessions, average session duration, and bounce rate for any period, compared with the period before. It breaks those numbers down by page, UTM source and campaign, device, browser, and country. It also reads Core Web Vitals page by page, so it can spot the pages that load slowly. Here's how that plays out. Say sessions from a LinkedIn campaign doubled last week, but signups didn't move. Kite sees both numbers and finds the landing page the campaign sends people to. Before it suggests rewriting anything, it checks whether that page is slow on phones. ### Find the step where people drop out of your funnel Kite builds funnels in PostHog from the events you already track to find the exact step where people give up. A typical funnel might run from a pricing page view, to a click on "Start free trial," to a completed signup, to a first project created. Kite reads the conversion rate at each step and finds the one that loses the most people. It can then list the actual people who dropped off at that step, along with their session recordings when PostHog captured them. Paths fill in the rest of the story. Kite reads the most common sequences of pages and events, so it can tell you what people do right before they buy, or where they go instead of finishing signup. If visitors who abandon the signup form keep heading to your security page, that's a strong hint about what the form is missing. When a step has no event to measure it, Kite can create one. It defines a PostHog action, such as a "Sign up click" that matches clicks on your signup button. That way, the funnel ends on the conversion you actually care about. ### Watch what visitors did on the page that lost them Funnels show where people leave, and PostHog's heatmaps and recordings show what happened just before they did. Kite reads click, rage-click, and scroll-depth heatmaps for a page, and it can filter them by screen width to compare phones with desktops. That's how it learns that most mobile visitors never scroll far enough to reach your pricing table. It can also open the sessions behind a hotspot. PostHog keeps heatmap data for 90 days, so Kite reads it within that window. Kite searches your session recordings by page, date, person, or console errors. It can also ask PostHog to review a specific set of recordings against a question, such as why these visitors abandoned checkout. It saves the recordings worth watching into a playlist your team can open. Errors belong in this picture too. Kite reads PostHog error tracking, so a signup button that breaks in one browser shows up as a named error with the pages and users it affected, rather than as an unexplained dip in signups. ### Make sure your campaigns get credit for the signups they bring Kite checks the tracking behind your campaign reports, because attribution only works when UTM tags match up. It runs PostHog's marketing analytics checks on your project. It audits recent UTM tags, finds campaigns with mistyped or unmatched sources, and lists the conversion goals you've set up with their last 30 days of results. It can break down the signups that count toward a goal by UTM source and campaign. It also suggests custom events that would make good conversion goals. This is the work that keeps a report honest. Imagine half your paid signups are sitting under "non-integrated" because someone tagged a campaign "Linkedin" instead of "linkedin." Kite finds the mismatch, shows you which campaigns are affected, and suggests the mapping that puts those signups back under the right channel. ### Test a fix with a PostHog experiment Once Kite knows which step to fix, it can test the fix as a PostHog experiment. First, it estimates how long the test needs to run to detect a meaningful lift with your current traffic. Then it creates the experiment with its feature flag and variants and adds the conversion it will measure. After you approve, Kite launches the experiment, reads the results as they come in, and recommends a winner. When you agree, it ships the winning variant to everyone, or it ends the test without shipping if neither version won. A PostHog experiment decides who sees which version. Your site or app then shows that version by checking the experiment's feature flag. When Kite works on your website code through an imported GitHub repository, it can build the new version too. Otherwise, your developers connect the variant to the flag and Kite handles the test from there. ### Ask visitors and users why they stall Sometimes the fastest way to learn why people stall is to ask them, and Kite does that with PostHog surveys. It can create a survey that pops up inside your site or product, or a hosted form with its own link. Kite writes the questions and targets the people you want to hear from, such as visitors who reached the pricing page but didn't start a trial. It launches the survey once you approve it. Then it reads response rates, individual answers, and a summary of the themes, and it stops the survey when it has heard enough. A survey answer becomes evidence for the next change. If a third of pricing-page respondents say they couldn't tell which plan includes single sign-on, Kite has a specific rewrite to propose. ### Group users and follow them over time Kite builds PostHog cohorts, which are saved groups of people defined by their properties or behavior. One example is everyone who signed up in September and hasn't come back since. A dynamic cohort updates its membership on its own, while a static cohort holds a fixed list. Kite uses cohorts to break down funnels, to target surveys, and to keep certain users out of an experiment. Kite also reads how people behave over time: - Retention shows how many new signups come back in the weeks after they join. - Lifecycle splits your active users into new, returning, resurrecting, and dormant. - Stickiness shows how many days in a period people use a feature. Together, these tell Kite whether a campaign brought in people who stay or people who leave after a day. ### Send lifecycle email through PostHog workflows If your team sends messages through PostHog workflows, Kite can build those emails and the workflows that send them. It writes the email template in your brand voice. Then it creates the workflow with its trigger, such as a signup event or a scheduled batch, and runs a test before anything goes live. For a batch send, Kite counts exactly how many people the audience matches and tells you that number before you approve. Once the workflow is live, Kite reads its delivery stats. That means a dormant-user cohort can turn straight into a win-back email without leaving PostHog. Kite picks the audience, writes the message, and then checks the lifecycle numbers to see how many of those people came back. ### Keep your team's PostHog dashboards current Kite keeps the analysis it does visible in PostHog, where your team already looks. It saves the insights it builds, such as a funnel or a retention chart, and adds them to new or existing dashboards. It marks important moments on your charts with annotations, so the day a new pricing page went live appears right on the trend line. It can also set up subscriptions that deliver a chart or dashboard snapshot on a schedule. And it reads PostHog's weekly web analytics digest, which compares visitors, top pages, top sources, and goal conversions with the week before. ## What Kite reads and changes in PostHog ### Information Kite can read - **Web analytics.** Visitors, pageviews, sessions, bounce rate, session duration, top pages, UTM sources and campaigns, devices, countries, Core Web Vitals, and the weekly digest. Kite uses these to spot traffic changes and the pages behind them. - **Funnels, paths, and trends.** Step-by-step conversion rates, the people who converted or dropped off at each step, common navigation paths, and event counts over time. These tell Kite which step to fix first. - **Heatmaps.** Clicks, rage clicks, mouse movement, and scroll depth on a page, plus the sessions behind a hotspot. These show Kite how people actually use a page. - **Session recordings.** Each recording's duration, starting page, activity, and console errors, plus PostHog's review of selected recordings. Kite uses these to explain a drop-off. - **Errors.** Error tracking issues with the pages, users, and sessions they affected. Kite checks these when a conversion falls for no visible reason. - **Marketing analytics.** Conversion goals, UTM tagging quality, and unmatched sources. Kite uses these to keep campaign credit accurate. - **Experiments.** Each experiment's status, exposures, and results for every variant and metric. Kite reads these to recommend a winner. - **Surveys.** Questions, targeting, response counts, individual answers, and theme summaries. Kite turns these into the next change to test. - **People and cohorts.** Person profiles and properties, cohort membership, retention, lifecycle, and stickiness. Kite uses these to judge whether new users stay. - **Your existing setup.** Saved insights, dashboards, and the events and properties your project tracks. Kite reads these first so it builds on what your team already measures. ### Information Kite can create or change - **Actions and event descriptions.** Kite creates actions that turn clicks or pageviews into named conversion events, and it adds descriptions to your events and properties. - **Insights, dashboards, annotations, and subscriptions.** Kite saves charts, builds and updates dashboards, marks launches on charts, and schedules snapshots for your team. - **Experiments and feature flags.** Kite creates draft experiments and their flags, adds metrics, launches and pauses tests, refreshes results, and ships the winning variant. - **Surveys.** Kite creates pop-up surveys and hosted forms, then launches and stops them. - **Cohorts.** Kite creates dynamic and static cohorts and changes who belongs to them. - **Recording playlists.** Kite collects the session recordings your team should watch. - **Workflows and email templates.** Kite writes email templates, builds workflows, runs tests, and turns a workflow on after you approve it. - **Person properties.** Kite sets properties on a person's profile, such as a lifecycle stage, so later cohorts and funnels can use them. ## How Kite connects to PostHog Kite is your AI marketer in Slack. It researches your business, builds a growth strategy, and ships the work that brings you new customers. Connect your PostHog account through OAuth. Kite then works with the records and permissions available to that connected account. If your organization has more than one project, such as one for your marketing site and one for your product, you choose the project Kite works in, and it can switch projects when a question spans both. You can start with a goal, like "find out why trial signups dropped last week." Kite proposes the funnel, the date range, and the recordings it will look at before it runs anything. This connection is separate from the analytics built into Kite. A website Kite builds and hosts comes with its own traffic and conversion reporting. Connect PostHog when your site or product already sends its events there. ## Playbooks using PostHog - How to find where users drop out of your funnel with PostHog (coming soon) Kite builds the funnel from your PostHog events, finds the step that loses the most people, explains why from the recordings and paths behind it, and proposes the change to make first. - How to find broken or leaky funnels with Segment, PostHog (coming soon) Segment sends your events into PostHog. Kite checks whether a weak step is a real drop-off or an event that stopped arriving, so you fix the tracking or the page, whichever is actually broken. - How to see which product behaviors lead to paid customers with PostHog, Stripe (coming soon) PostHog supplies what people did in your product, and Stripe supplies who went on to pay. Kite lines the two up on a shared customer identifier to find the actions that paying customers have in common. - How to see which Typeform submissions become conversions in PostHog (coming soon) Typeform supplies the form responses, and PostHog supplies what those people did next. Kite follows each submission into PostHog to see which forms produce people who go on to sign up or buy. ## Where PostHog fits in Kite's marketing work ### [Improve website conversion](/use-cases/improve-website-conversion.md) PostHog can carry the whole conversion loop for a site or product that Kite doesn't host. Kite reads the funnel to find the weak step, uses recordings, heatmaps, and surveys to explain it, and tests the fix as a PostHog experiment. Then it measures the result with the same events it used to find the problem. Because every stage happens in one project, the number Kite set out to move is the same number it reports back to you. ## Review and approval Kite proposes work by default. A team approves it with a reply in the Slack thread or the Approve button on a proposed plan. Teams that want Kite to act first can turn that on. In PostHog, approval comes before the steps that change what real people see or receive: launching an experiment, shipping a winning variant, launching a survey, and turning on an email workflow. Reading data, building funnels, and saving charts happen as part of the analysis. ## Common questions ### Can Kite connect PostHog behavior to revenue in Stripe or my CRM? Yes, when your tracking gives both tools a shared identifier, such as the user's email address or account ID. With that in place, Kite matches each person in PostHog to their Stripe customer or CRM contact and compares what paying customers did with what everyone else did. Without a shared identifier, Kite compares the two sides as trends over the same period instead of person by person. ### Does Kite check the ad platform data that PostHog pulls in? Yes. If you've connected ad platforms to PostHog's marketing analytics, Kite checks each one's sync status, when it last synced, and any errors it hit. It then confirms that the campaign names coming from the ad platform match the UTM tags on your events, which is what lets PostHog put ad spend and signups in the same report.