Looker Studio annotations: how to mark changes on your charts

Does Looker Studio have annotations?

No. Looker Studio has no built-in way to pin a note to a date on a chart, and the April 2026 rename did not add one. Google's release notes for 16 April 2026 say: "We've rebranded Looker Studio as Data Studio." Your reports keep working; only the name changed, and the help pages now say Data Studio.

That matters if you came from Universal Analytics or use GA4, where annotations are native. Google's GA4 annotations help page says notes show on report cards with line graphs, with titles up to 60 characters and descriptions up to 150. The same page does not mention Data Studio, so don't expect GA4 notes to show up in your dashboards. Our guide to GA4 annotations covers the GA4 side.

In Data Studio you have four workable options:

• Reference line or band on the chart's X axis, set to a date.
• Blended event sheet: a Google Sheet of changes joined to your data by date and drawn as bars.
• Calculated field: a CASE formula that flags specific dates inside the data source.
• Change table or text box next to the chart, listing what changed and when.

How do I add a date marker with a reference line?

A reference line is the fastest way to mark one or two dates on a single chart. Google's reference lines documentation lists time series, line, combo, column, bar, area and scatter charts as supported.

1. Edit the report and select the chart.
2. In the properties panel, open the Style tab.
3. Click Add a reference line (or Add a reference band for a date range, such as a sale week).
4. Set the type to Constant value or Parameter, then in the axis settings choose the X axis. With a date dimension, a date selector appears.
5. Type a label, such as "Bidding: tCPA 40 → 32", and tick Show label.

Limits to know before you rely on it:

• Up to 10 reference lines per chart.
• Each line lives on one chart. Copy the chart and you copy the lines, but nothing updates across the report.
• Changing the chart type removes unsupported lines. 100% stacked column and bar charts don't support them at all.
• The same Google page also says "Reference lines on date axes aren't supported" in its limits section. The documentation contradicts itself, so test a date line on your chart before you build a client report around it.

Use reference lines for the two or three changes a stakeholder must see. They are not a change log.

How do I show events from a Google Sheet on a time series chart?

Keep your changes in a Google Sheet, blend it with your metrics on the date field, and draw the event count as bars on a second axis. This is the only method where one list of events feeds every chart.

A method described by Lazarina Stoy works like this:

1. Create a sheet with the columns Date (YYYY-MM-DD), Category, Event and Description. Use one date format everywhere, or the join fails silently.
2. Add the GA4 or Search Console source and the sheet to the report.
3. Blend them: the metrics source on the left, the sheet on the right, join condition on Date, join type Left outer join.
4. Build a time series with Date as the dimension, your metric (sessions, conversions) as a line, and the count of events as a second metric.
5. In the Style tab, show the event series as bars on the right Y axis and fix that axis at 0 to 1, so every event day reaches the top.
6. Add a table below the chart with Date, Category and Event, plus a filter by category.

Two details from Google's blend documentation save debugging time. A blend takes up to five data sources. And rows are pre-grouped before the join, so "identical rows are collapsed": if two changes on the same day look identical, add an ID column to the sheet so both survive.

The bar shows that something happened that day; the description stays in the table, not on the chart. That split is fine: the chart tells you where to look, the table tells you what to check.

Which annotation workaround should you use?

Pick by how many changes you have and how many charts need them. For a few fixed dates, a reference line is enough. For an ongoing account, use the blended sheet plus a table.

Most teams end up combining two: bars from the sheet on the trend chart, and a short table of changes for the period under it. If you send these reports to clients, our post on agency client reporting shows how to write the "what changed" part.

What should you log in the annotation sheet?

Log every change that could move a metric, not only the big launches. An annotation sheet with five entries a year tells you nothing when conversions drop on a Tuesday.

• Ads: budget and bid strategy changes, new or paused campaigns, audience and creative swaps, auto-applied recommendations.
• Tracking: GTM publishes, consent banner changes, conversion action edits, new GA4 events.
• Site: releases, template or checkout changes, price changes, downtime.
• CRM and sales: lead routing, form fields, lead scoring rules.
• External: competitor promotions, holidays, platform outages, algorithm updates.

Give each row a date, an owner, a category and a one-line reason. Write the before and after values where they exist ("Daily budget 150 € → 220 €"). Agree on one time zone, the same one your reports use, or a late-night change lands on the wrong day. Our marketing change log template has a ready column set you can paste into the sheet.

The hard part is not the sheet, it is the habit. Name one owner per client who checks the sheet weekly against the ad platforms' change history.

How do annotations help you find what caused a change?

Annotations narrow the search: they show which changes sit right before the shift, so you test those first instead of guessing. The method is the same whatever the metric.

1. Put every change on one timeline. Take the 7–14 days before the shift and list your team's edits, platform automations, site and tracking releases, CRM changes and outside events.
2. Rule out tracking first. Check GTM versions, consent changes and conversion settings for that window. A broken tag looks exactly like a drop in demand.
3. Test one hypothesis at a time. Compare the segment the change touched with one it didn't: the campaign, device, country or landing page.
4. Write the conclusion back on the event row, so the next person doesn't redo the work.

Example: sessions on a Data Studio chart fall 18% from 3 March. The event bars show a site release on 2 March and a GTM publish on 3 March. Organic and paid fall by the same share while server orders stay flat, which points at tracking, not traffic. The GTM version on 3 March removed the GA4 config trigger from two templates.

A spreadsheet works until it drifts out of date. Changeline keeps this list as a marketing change log on a shared timeline per client: Google Ads edits are imported automatically, and the team logs the rest with date, owner and reason. You can start a change log for free and keep the sheet for the chart. For the full diagnosis method, see marketing root cause analysis.