Quick answer: Google Analytics annotations are short, dated notes you attach to the timeline graph in a Universal Analytics view. Use them to record anything that could change your numbers: site launches, redesigns, tracking changes, campaigns, outages and algorithm updates. To add one, open any report with an over-time graph, click the small tab under the graph, choose “Create new annotation,” pick the date, write a short note and save it as shared or private. Make it a team habit and future you will know why traffic jumped or dropped instead of guessing.
Why annotations matter
Every analytics account eventually shows a spike or dip that nobody can explain. Was it the new homepage? The email campaign? The week the contact form broke? A tracking code that went missing during a plugin update?
Six months later, nobody remembers. People dig through old emails or chat threads, or give up and guess. Annotations fix that by putting the context exactly where you look at the data: on the graph itself.
They take seconds to add and cost nothing. The value comes from doing it consistently.
How annotations work in Universal Analytics
A few basics before you start:
- Annotations live in a view. They are attached to the reporting view where you create them. If you use several views (for example, a raw view and a filtered main view), add important notes to each one you report from. Our guide to Google Analytics views and filters explains how views fit together.
- They are dated, not timed. An annotation marks a day, not a specific hour.
- They can be shared or private. Shared annotations are visible to everyone with access to the view. Private ones are visible only to you. Creating shared annotations requires sufficient permissions on the view (Collaborate or Edit).
- The text is short. The note field only takes a brief line, so write clearly and save the details elsewhere.
- You can star them. Starring an annotation highlights it in the list, which helps when a busy month has many notes.
How to add an annotation, step by step
- Sign in to Google Analytics and open the view you report from.
- Go to a report with an over-time line graph, such as Audience Overview or Acquisition Overview.
- Click the small tab or arrow just below the graph to open the annotations panel.
- Click Create new annotation.
- Choose the date the change happened.
- Write a short, specific note.
- Choose Shared if the whole team should see it, or Private if it is a personal reminder.
- Click Save.
A small marker appears under the graph on that date. Hover over or click it to read the note. You can edit or delete annotations you created from the same panel.
Adding notes for past events
You can pick any past date, so it is worth spending half an hour back-filling the big events from the last year or two: launches, redesigns, migrations, major campaigns and known outages. Old reports instantly become easier to read.
What to annotate
Anything that might move your numbers, or make someone misread them, belongs on the timeline. A practical list:
Site changes
- New site launch or redesign
- Domain change or HTTPS move
- New or removed pages, sections or navigation
- Changes to forms, checkout or pricing pages
- Big content updates on high-traffic pages
Tracking changes
- Tracking code added, moved or replaced (for example, a switch to Google Tag Manager)
- New filters applied to the view
- Goals created or edited
- Event tracking added or changed
- Consent banner added or updated, since it can change how many visits are recorded
Tracking changes are the ones teams forget most, and they cause the most confusion. A sudden drop in bounce rate is often a tracking change, not a real improvement.
Marketing activity
- Email campaigns and newsletters
- Paid campaigns starting, stopping or changing budget
- Press coverage, podcast mentions or social posts that drove a spike
- Promotions, sales and seasonal offers
Outside events
- Confirmed Google updates that may affect organic traffic (see our notes on Google core updates)
- Holidays, local events or anything that changes demand
- Store or office closures and reopenings
- Hosting problems or downtime
Writing annotations people can use
Since the text is short, structure helps. A simple pattern:
[Type] What changed (where)
Examples:
- “SITE: New homepage layout live”
- “TRACKING: GTM replaced hard-coded GA tag”
- “CAMPAIGN: Autumn newsletter sent to full list”
- “OUTAGE: Site down approx. 3 hours, host issue”
- “SEO: Title tags rewritten on service pages”
Starting with a type label makes the list easy to scan. Keep the wording plain enough that someone new to the team will understand it a year later.
If a change needs more explanation, keep a fuller change log in a shared spreadsheet or project tool, and use the annotation as a pointer to it.
Making annotations a team habit
Annotations only help if people actually add them. A few ways to make that happen:
- Make one person responsible. Often the person who looks after analytics or the website. Others tell them when something changes.
- Add it to launch checklists. “Add GA annotation” should be a line on every deployment, campaign launch and tracking change.
- Review monthly. When you prepare a monthly report, scan for spikes and dips without a note and find out what happened while memories are fresh.
- Agree on a format. A shared naming pattern keeps the list readable.
Developers and marketers both make changes that affect the data, so both should know about the habit.
Using annotations when reading reports
Annotations earn their keep when you are trying to explain a change. When you see a sudden shift:
- Open the annotations panel for that date range.
- Check for site, tracking or campaign notes on or just before the change.
- Compare segments (organic, paid, direct, device) to see where the shift happened.
- If there is no note, investigate and add one once you know the cause.
They are especially useful for diagnosing a traffic drop and for year-over-year comparisons when this year’s pattern looks nothing like last year’s. Notes on closures, reopenings and campaign pauses make those comparisons far easier to explain.
Limits to keep in mind
Annotations are simple, and they have some gaps:
- No bulk import or export. Each note is added by hand in the interface.
- No access through the reporting API, so they do not flow into other tools.
- They do not appear in Google Data Studio. If you build reports there, keep a change log sheet and show key events in a table or text box alongside your charts. Our guide to Google Data Studio dashboards covers report layout.
- They are per view, so important notes may need adding in more than one place.
These limits are why a separate change log is worth keeping for bigger teams. The annotation tells you something happened; the log tells you the full story.
Checking annotations during an audit
If you inherit an analytics account, the annotations list is one of the first places to look. A healthy account has regular notes on launches, tracking changes and campaigns. An empty list usually means the history lives in people’s heads. Our Google Analytics audit checklist includes annotations alongside goals, filters and tracking checks.
FAQ
Who can see my Google Analytics annotations?
Shared annotations are visible to anyone with access to the view. Private annotations are only visible to the person who created them.
Can I add an annotation for a date in the past?
Yes. You can choose any date, which makes it easy to back-fill launches, migrations and campaigns that happened before you started the habit.
Do annotations copy across views?
No. Each annotation belongs to the view it was created in. Add important notes to every view you use for reporting.
Should I annotate small content updates?
Only if the page matters to your traffic or conversions. Annotating every small edit creates noise. Focus on changes that could plausibly move your numbers.
Context turns numbers into answers
Google Analytics annotations are one of the simplest habits in analytics. A few seconds per change saves hours of guessing later and makes every report easier to explain to clients, managers and your own team. If you want help setting up clean tracking and reports that show what is working, take a look at our Know what’s working service.
