Why a sudden change in a metric needs a fast, careful answer
A number that moves sharply is either a problem to fix or a win to repeat, and you usually need to know which before the next meeting. Unsubscribes triple after one newsletter. Signups fall by a third in a single week. Traffic jumps on a Tuesday for no obvious reason. Someone will ask what happened, and "we're looking into it" only works once.
The work behind a good answer follows the same order every time. You check that the change is real and not a tracking problem. You break the number down until you find the slice where the change actually happened. You line that slice up against what happened at the same moment, such as a send, a launch, a site update, or a campaign that ended. Then you say what you think caused it and how sure you are.
None of this is hard, but it's slow. It means pulling reports from several tools, comparing the right date ranges, and remembering what shipped last Thursday. An AI agent is well suited to it, because it can read every source in one pass and keep a record of what changed and when.
Kite is an AI marketer. It researches your business, builds a growth strategy, and ships the work that brings you new customers. Here's how it investigates a number that moved.
How Kite investigates a sudden spike or drop
Kite starts with the number you're worried about and the dates you noticed it. It reads that metric from wherever it's measured: Kite's built-in analytics for a website Kite hosts, or your connected Google Analytics, PostHog, Mixpanel, Amplitude, or Mailchimp account. It compares the period with the one before it so the size of the change is a number rather than a feeling.
From there, Kite works the problem the way an experienced analyst would. It checks whether the data can be trusted, breaks the metric down to find where the change is concentrated, and lines that up against the work that shipped and anything else that happened that week. Kite has an advantage here, because when it published the page, sent the email, or launched the campaign itself, it already knows what changed and when.
Kite then tells you the likely cause, the evidence behind it, and what it would do next. Once you agree on a fix, it makes the change it can make, then reads the same number again to see whether it recovered.
- Check that the change is real before explaining it
- Find where the change is concentrated
- Match the change to what happened at that moment
- Explain the likely cause and how sure Kite is
- Fix the cause and watch the number recover
Check that the change is real before explaining it
The first question in any investigation is whether the number moved or the measurement did. A signup event that stopped firing after a site update looks exactly like a collapse in signups. A provider outage can make a day look empty. A renamed event can make a funnel step look like it lost everyone.
Kite separates these cases before it explains anything. Its built-in analytics distinguish between a number that was measured as zero, data that hasn't arrived yet, and data that couldn't be read at all, and Kite never reports an outage as zero activity. It reads the site's list of tracked events to confirm that the conversion event still exists and was recorded recently. In Amplitude, it reads each event's volume for the week, so an event that stopped arriving after a release stands out. In PostHog, it reads error tracking, so a broken signup button shows up as a named error rather than an unexplained dip.
Kite also makes sure the comparison is fair. It compares the same length of time, the same filters, and similar days, so a quiet holiday week isn't mistaken for a decline.
Find where the change is concentrated
A sudden change in a total almost always comes from one part of it. Kite breaks the metric down by the dimensions that could hide the cause and looks for the slice that moved while the rest stayed flat.
For website traffic and signups, Kite splits the number by:
- traffic source and campaign
- landing page
- device and browser
- country
It also builds the signup funnel step by step to find the exact step that lost people. A drop that sits entirely in mobile visitors at the form step points somewhere very different from a drop spread evenly across every source.
For email, Kite reads the Mailchimp report for each campaign, including deliveries, bounces, opens, clicks, unsubscribes, and abuse complaints. It lists who unsubscribed after a particular send and reads your audience's daily subscribe and unsubscribe activity, so it can tell whether the spike came from one campaign or built up over several. It also compares the campaign with the sends before it to see which segment it went to and how often those people had heard from you recently.
Here's how that plays out. Say unsubscribes from Tuesday's newsletter were five times your usual rate. Kite reads the campaign report and the list of people who unsubscribed, then finds that most of them were contacts added from a webinar list last month who had never received the newsletter before. The newsletter itself performed normally with your regular subscribers. The cause is who received the email, not what it said.
Match the change to what happened at that moment
Once Kite knows where the change happened, it looks for what changed at the same time and in the same place. The timing and the location together usually narrow the cause to one or two candidates.
Kite starts with the work it knows about. It keeps a record of the pages it published, the emails it sent, and the campaigns it ran, along with the initiatives they belonged to. On a Kite-hosted site, every published change is recorded, so Kite can see that the signup page was updated on the day signups fell. In PostHog and Amplitude, Kite can read and add notes on your charts, so a launch or pricing change appears right on the trend line.
It then asks about what it can't see. You know that a partner mentioned you in their newsletter or that the sales team ran a promotion, and a single sentence from you can save an hour of searching. Kite can also research outside causes, such as a competitor launch or a public discussion that sent people to your site.
Explain the likely cause and how sure Kite is
Kite reports a cause as a finding with evidence, not as a verdict. Each finding names the source of the numbers, the dates it compared, any filters it applied, and what the data can't show.
Kite is careful about the difference between timing and cause. "Signups dropped the week the homepage headline changed" is a reason to test the headline, not proof that the headline did it. When the evidence is strong, such as a JavaScript error on the signup form that started with a site update and affects only the visitors who stopped converting, Kite says so plainly. When two explanations fit equally well, it says that too, and proposes the check or test that would separate them.
Short findings arrive as a message in your conversation with Kite. When the explanation needs charts and tables, Kite can publish a findings page with them.
Fix the cause and watch the number recover
An investigation is only useful when it leads to a change. Kite proposes the fix that matches the cause, and it carries out the work it's able to do.
For example, if a site update broke the signup form on a Kite-hosted site, Kite can fix the error or undo that single change without losing the work published after it. If unsubscribes came from sending to the wrong segment, Kite can tag those contacts in Mailchimp and build a segment so future newsletters reach only the people who asked for them. If a page change looks responsible but the evidence isn't conclusive, Kite can set up an experiment to test it. Kite asks for your approval before it publishes, sends, or launches anything.
After the fix, Kite reads the same metric over a comparable period to confirm it recovered. If you want to hear sooner next time, Kite can keep a standing watch on your website traffic or put a regular check on a schedule, so a change reaches you in days rather than at the end of the month. The custom alerts and traffic drop alerts pages describe those options in more detail.
What you get
A confirmed change
Kite tells you how much the metric moved, over which dates, and whether the change is real or caused by a tracking or data problem.
The slice where it happened
You see the source, campaign, page, device, funnel step, or email segment that accounts for the change.
A likely cause with evidence
Kite names what it believes caused the change, the evidence behind it, and how confident it is.
A proposed fix
You get the specific change Kite recommends, and Kite carries out the work it can do once you approve it.
A follow-up reading
Kite measures the same number again after the fix, so you know whether it recovered.
How to get started
Tell Kite which number moved and roughly when. You might say, "Unsubscribes spiked after Tuesday's newsletter. What happened?" or "Signups dropped this week. Find out why before Monday's meeting." You can work with Kite in the Kite web app or in Slack.
Kite proposes what it will check first, such as the campaign report, the signup funnel, and the pages that changed recently, and then runs the investigation. It reports back with its findings and the fix it recommends, and you approve any change before it goes live.
If Kite hosts your website, its built-in analytics already measure your traffic and conversions, so you don't need to connect anything. If your site, product, or email is measured elsewhere, connect the account that holds the number, such as Google Analytics, PostHog, Mixpanel, Amplitude, or Mailchimp.
Integrations used to investigate a sudden spike or drop
Kite reads the metric from the tool where it's recorded. For websites Kite hosts, that's Kite's built-in analytics, which need no extra account. For everything else, connect the analytics or email tool your team already uses.
Read website and product numbers
Kite compares traffic and conversions across periods, breaks them down by channel, source, campaign, landing page, and device, and builds funnel reports to find the step that lost people.
Kite reads web analytics, funnels, paths, and error tracking to find where a change happened, opens the session recordings behind a drop-off, and adds notes to charts so launches and fixes appear on the trend line.
Kite reads your saved reports and the event definitions your team wrote, then splits funnels and retention by campaign, device, plan, or country to find the group behind the change.
Kite reads active users, funnels, and retention broken down by platform, country, or source, and checks each event's weekly volume to catch an event that stopped arriving.
Common questions
Why did my email unsubscribes suddenly spike?
A sudden spike in unsubscribes usually comes from who received the email rather than what it said. The most common causes are sending to a segment that doesn't normally hear from you, such as a recently imported list, sending noticeably more often than usual, or sending content that doesn't match what people signed up for. Kite checks each of these by comparing the campaign's audience, timing, and results with your previous sends and reading the list of people who unsubscribed.
How do I tell whether a change is real or just normal variation?
Compare the change with how much the number usually moves, not just with last week. A metric with small numbers, such as 40 signups a week, can swing by a quarter without anything changing, while the same swing in a metric with thousands of events is much more likely to mean something. Kite compares the period with similar periods before it and tells you when the change is too small to explain with confidence.
What should I check when signups suddenly jump?
Check where the new signups came from and whether they behave like your usual signups. A jump from one source, such as a mention in a newsletter or a post that spread, is good news worth repeating. A jump from an unfamiliar source with signups that never come back can be spam or low-quality traffic. With a connected product analytics tool such as PostHog, Mixpanel, or Amplitude, Kite can see whether the new signups went on to use the product.
Could a traffic spike be coming from ChatGPT or other AI assistants?
Yes, and it's worth checking, because AI assistants now send visitors to many websites. Kite's built-in analytics show AI assistants as a source of visitors on sites Kite hosts, and with Google Analytics connected Kite can filter visits by sources such as chatgpt.com and perplexity.ai. The AI assistant referral traffic page covers how to track this over time.
Is a website traffic drop handled differently?
A traffic drop follows the same steps, with extra checks for search rankings, campaigns that ended, and pages that broke. The traffic drop diagnosis page covers that case in detail.