Annotation

Analytics

Also: Chart Annotation · Data Annotation

What it isA note pinned to a date in your analytics
When it mattersWhenever traffic or conversions spike or drop
Watch forNot annotating at the time
Lives inGA4, Search Console, ad platforms

Quick definition

An annotation is a note added to a specific date or date range in an analytics platform to explain why data changed. When traffic spikes, a campaign launches, tracking breaks, or the site is updated, an annotation records what happened so future analysis has context.

How it varies across Australia

Most Australian businesses we review have no annotation history at all. The businesses that do annotate consistently are a minority, and they make substantially better decisions when investigating historical data. The gap between annotators and non-annotators shows up most sharply when teams try to explain year-on-year changes in organic traffic or conversion rate.

See data and tracking maturity across Australian industries

What it actually means

An annotation is a note you leave on a date in your analytics tool. It says: something happened here, and here is what it was.

When a campaign launched, annotate it. When the site went down for two hours, annotate it. When you changed the tracking setup, changed a UTM Parameter convention, migrated to GA4, or pushed a major SEO update, annotate it. Every anomaly in your data has a cause. Annotations are how you record the cause at the time, rather than trying to reconstruct it six months later.

The value is almost invisible when things are running smoothly. It becomes critical during year-on-year comparisons, attribution reviews, or any time someone asks 'why did this change?' A well-annotated analytics account lets you answer that question in thirty seconds. An unannotated one requires archaeology.

Google Analytics 4 (GA4) supports annotations natively, as do most ad platforms and Search Console. The annotation doesn't change the data. It sits beside it as context.

Annotations also protect the team when tracking breaks. If a developer accidentally removes a tag and nobody notices for a week, the data gap looks like a traffic collapse. An annotation, even added retroactively, stops future analysts from drawing wrong conclusions from the hole in the chart.

Annotations are institutional memory for your analytics. Without them, every traffic spike becomes a mystery.

How it shows up

Annotations appear as markers or flags on timeline charts inside analytics platforms. In GA4, annotations are visible as small icons on the chart that expand to show the note text when clicked. In Google Search Console, they appear along the bottom of the performance chart. In most ad platforms, campaign launches and pauses often auto-annotate, but site-level changes, tracking issues and external events require manual notes.

The absence of annotations also shows up, indirectly, every time a team spends an hour in a meeting debating why traffic moved instead of knowing immediately.

The Australian context

Australian public holidays, retail events like EOFY, Click Frenzy and the AFL Grand Final all create predictable traffic and conversion anomalies. Businesses that annotate these events year-on-year build a running comparison layer that makes seasonality planning far more reliable. Without annotations, EOFY traffic spikes and conversion drops get re-investigated from scratch every year.

Where people get this wrong

Adding annotations retroactively from memory weeks after the event.Memory is unreliable and teams rarely agree on exact dates. Retroactive annotations are better than nothing, but they lose precision and often miss secondary events that happened around the same time.
Only annotating major campaigns and ignoring tracking changes.Tracking changes, tag removals and GA4 configuration updates are the most dangerous unannotated events because they create data gaps that look like real traffic or conversion changes.
Treating annotations as optional documentation rather than standard operating procedure.When annotations are optional, they happen inconsistently, which means the account has context for some periods and not others, which is almost as confusing as having none at all.

Related terms

Common questions

Where do I add annotations in GA4?

In GA4, annotations are added directly on the Explorations or Reports charts. Click the annotation icon on the timeline, select a date, and type the note. Annotations are visible to anyone with access to the property, so the whole team benefits from a single entry.

What should I annotate?

Campaign launches and pauses, major site updates, tracking changes, GA4 configuration changes, outages or downtime, UTM convention changes, algorithm updates you suspect hit you, and any external event like a media mention or PR spike. When in doubt, annotate. The cost is thirty seconds.

Do annotations affect my data?

No. Annotations sit alongside the data as notes. They don't change what is recorded, how sessions are counted, or how conversions are attributed. They are purely contextual.

What happened to annotations in GA4 compared to Universal Analytics?

Google removed annotations when GA4 launched, then re-introduced the feature after significant user demand. If your GA4 property was set up before annotations returned, you will not have retroactive notes for that period. Add them manually from what you can reconstruct, and build the habit going forward.

Keep exploring

About New Rebellion

New Rebellion is a marketing intelligence consultancy. We build tools, score Australian businesses on how their marketing actually performs, and publish Debrief every day. This dictionary is part of how we work in the open.

How we think →