Chart Annotations: How to Add Context to Your Traffic Data

You open your analytics dashboard three months after a major campaign and see a sharp spike on April 14th. Traffic doubled for four days, then returned to normal. No one on the team can remember what happened that week. Was it a newsletter? A press mention? A Product Hunt launch? The data is there — the context is gone.

Chart annotations solve this problem by letting you embed explanatory labels directly onto your traffic chart at the date they occurred. They require no code changes — just a date, a label, and a click to save. And they stay in the chart permanently, giving you and your whole team a shared record of what drove every significant traffic movement.

What Are Chart Annotations?

Chart annotations are labeled markers on your analytics traffic chart tied to specific dates. In statpx, annotations appear as amber dashed vertical lines on your site's main pageview chart. When you hover over a line, the label you wrote appears — "Product Hunt launch", "Newsletter #12 sent", "New pricing page went live", "Server outage 14:00–17:00 UTC".

The annotation sits exactly at the date it describes. When you view your 30-day or 90-day chart, every annotated event is visible in its correct position relative to the traffic data. Instead of asking "what happened here?", you already know.

How It Works in statpx

Annotations are managed from the Annotations page in your site dashboard. The workflow is straightforward:

1. Navigate to your site and open the Annotations page
2. Click Add annotation
3. Select the date the event occurred
4. Type a short label (e.g. "Email campaign — May batch")
5. Save

That's it. The annotation immediately appears as an amber dashed line on your site's traffic chart. No code, no deploys, no configuration. You can edit or delete annotations at any time from the same page.

What to Annotate

Any event that could plausibly affect your traffic is worth annotating. In practice, the most useful categories are:

• Product launches and releases — major feature releases, new pricing tiers, public betas
• Marketing campaigns — newsletter sends, paid ad campaign starts and ends, affiliate partnership activations
• Content milestones — major blog posts published, landing pages launched, viral social posts
• Technical events — server outages, CDN changes, major site redesigns, tracking snippet updates
• A/B test lifecycle — test started, test ended, winner deployed
• External factors — search algorithm updates (Google core update dates), platform policy changes that affect referral traffic
• Seasonal events — holiday sales, industry conferences, year-end traffic drops

The more consistently you annotate, the more useful your historical charts become. A chart you've been annotating for a year is a business timeline, not just a graph.

Annotations vs. Notes Apps: Why In-Chart Context Wins

Teams often keep notes about significant events in Notion, Confluence, Slack, or spreadsheets. The problem isn't that those tools are bad — it's that they're disconnected from the data. When you look at a traffic chart, you don't think to open Notion and search for what happened on a specific date. You make assumptions, misremember, or simply lose the context.

In-chart annotations remove that gap entirely. The context is attached to the data. When you pull up your 90-day chart to report on quarterly traffic, the annotations for every campaign, launch, and outage are already visible — no cross-referencing required. This is especially valuable during team reviews, investor updates, or post-mortems where you need to explain traffic patterns quickly and accurately.

Team annotations

When you share your statpx dashboard with team members, they see the same annotations you do. Annotations are stored at the site level, not the user level — so everyone looking at the same site's chart sees the same set of markers. This creates a shared understanding of your site's history without requiring any communication overhead. A new team member joining three months after a major launch can open the chart and immediately understand the context of every traffic movement since you started annotating.

How many annotations is too many?

Annotations are most useful when they mark genuinely significant events. If you annotate every minor blog post, every social post, or every small config change, the chart becomes cluttered with markers that dilute the signal from the events that actually mattered. A good rule of thumb: annotate anything that would warrant a sentence in a quarterly traffic review. For events that happened more than 90 days ago and are no longer relevant to ongoing analysis, consider deleting them to keep your chart readable.

If you want to be alerted when traffic moves significantly without you noticing — rather than explaining it after the fact — see our guide on traffic spike alerts. Annotations and alerts work well together: alerts catch the movement as it happens, annotations provide the explanation for why it happened.

The Bottom Line

A traffic chart without context is just a line. You know where the peaks are, but not why they happened, whether they're repeatable, or what caused the valleys in between. Chart annotations transform your analytics history into a timeline you can actually reason about. The investment is minimal — a few seconds per notable event — and the payoff compounds every time you open your dashboard weeks or months later and can immediately explain what you're seeing. If you share your analytics with a team or use them to make product decisions, annotations should be part of your standard workflow. For sharing analytics more broadly, take a look at our guide on team analytics sharing.