Amplitude + Kite

Kite builds funnels from the events your product already sends to Amplitude to find the exact step where people give up. A self-serve signup funnel might run from "Pricing Page Viewed," to "Signup Started," to "Account Created," to "Project Created." Kite reads how many people complete each step within the time window you'd expect, such as seven days for a trial, and how long the ones who convert take to get there.

The overall rate rarely tells the whole story, so Kite splits each funnel by one property at a time, such as platform, country, plan, or first UTM source. That's how a vague "activation is down" becomes something specific, like "new mobile users from one paid campaign stop at account creation." Kite can also limit a funnel to new users only, which keeps returning customers from hiding a problem with first-time visitors.

Before Kite trusts a sudden drop, it checks the events themselves. It reads the event types in your project with this week's volume for each, so it can spot an event that stopped arriving or was renamed in a recent release. A step that broke because of tracking gets a tracking fix, not a page rewrite.

A campaign that fills your signup chart with people who never come back costs more than it looks. Kite reads Amplitude's retention data to see what share of new users return in the days and weeks after they sign up, and it can split that by a property such as acquisition source or plan.

Here's how that plays out. Say a LinkedIn campaign and a Google search campaign each brought in 300 signups last month. If 35 percent of the search signups are still active four weeks later and only 8 percent of the LinkedIn signups are, Kite flags the gap and recommends where to shift effort. It can then act on that recommendation, for example by rewriting the LinkedIn landing page so it sets clearer expectations, or by drafting an onboarding email for the users who signed up and went quiet.

When your product sends revenue events to Amplitude, Kite also reads revenue per user, revenue per paying user, and total revenue over time. That lets it judge channels by what their users pay, not just by how many sign up.

Sometimes the useful question is about specific people. Kite can look up a user by the ID your product gives them and read their event stream from the first event forward, including the UTM parameters and referrer recorded when they arrived.

That's useful when a handful of accounts matter a lot. If five teams upgraded to your top plan this month, Kite can read how each one first arrived, which pages they saw before signing up, and what they did in their first week. Patterns across those five timelines often point to the campaign or page worth more budget.

Kite reads the headline numbers your team checks every week. These include daily, weekly, and monthly active users, new users, and how those numbers break down by platform, country, or app version. It also reads session counts per user, average session length, and today's live activity in five-minute intervals.

Kite uses these numbers to notice when something changes and to explain it. If new users jump 40 percent on a Tuesday, Kite checks which country, platform, or source the jump came from before it tells your team what happened. It can deliver that readout once or put it on a schedule, such as every Monday morning.

When Kite ships something, it can add a note to your Amplitude charts on that date. A note might read "Pricing page rewrite" or "Spring webinar email sent," filed under a category such as Marketing, and it can cover a single day or a date range. Kite can attach the note to one chart or show it across every chart in the project.

Those notes make before-and-after comparisons readable for everyone. Anyone who opens your signup chart a month later can see why the line moved, without asking Kite or digging through old conversations. Kite also reads the notes your team has already added, so it knows about a release or outage before it explains a change.

A cohort in Amplitude is a saved group of users, such as everyone who started a trial in September but never created a project. Kite reads the cohorts your team has already saved, and it can pull the members of one, along with the user properties you choose, to use in its own work. For example, it can use that list to plan an email to the trial users who stalled.

Kite can also create a cohort from a list of users it identified, or add and remove members from an existing one. If Kite's research marks 40 free accounts as ready for a sales conversation, it can save them as a cohort so your team can open the same group in Amplitude, chart it, and send it to the tools your Amplitude account already syncs with.

Kite can update user properties in Amplitude without sending a new event. For example, after an email campaign it can mark each recipient with the campaign's name, so later funnels and retention charts can be split by who got the email. It can also send events into your project, which is useful when a step in the journey happens somewhere Amplitude doesn't see.

A funnel built on the wrong event gives the wrong answer, and tracking plans get messy as teams grow. Kite reads your project's event types, event properties, and user properties, along with their categories and descriptions, so it uses the exact names your product sends.

Kite can also tidy that plan. It writes descriptions for events that have none, groups events into categories your team will recognize, and updates or removes event types that are no longer used. It can restore an event type that was deleted by mistake. When a funnel needs a step your product doesn't track yet, Kite can add the event to your tracking plan with a clear description, so your developers know exactly what to build.