GA4 annotations alternative: when notes on a chart are not enough

What are GA4 annotations and what are their limits?

GA4 annotations are short notes you attach to a date or a date range in a Google Analytics 4 property, so anyone reading a line chart sees that something happened. They are built in and free, but small by design.

• 1,000 annotations per property.
• 60 characters for the title and 150 for the description.
• Analyst role or above at the property level to create, edit or delete them; Viewer or above to see them.
• Line charts only. You create one from a report with a line graph or through the Admin API, and it then shows on every report and report card with a line graph in that property.
• One list per property, under Admin, Data display, Annotations.
• System annotations. Google may add one when an issue affects your data; you can't edit or delete those.

For a full walkthrough of creating and using them, see our guide to GA4 annotations.

Why are GA4 annotations not enough for marketing teams?

GA4 annotations explain a chart inside one property. Most marketing changes happen somewhere else, and most teams work across many properties and many people.

• One property at a time. An annotation lives in the property where you made it. An agency with 20 clients keeps 20 separate sets of notes, and they sit in GA4 reports, not in Google Ads or Meta Ads Manager.
• 150 characters. Enough for "New landing page live", not for the old and new value, the owner and the reason.
• Writing needs the Analyst role. Media buyers or developers with Viewer access can read notes but not add them, so changes go unrecorded or wait for someone else.
• Readers need GA4 access. A client or manager needs at least the Viewer role on that property to see a note.
• Nothing comes in on its own. Apart from Google's system annotations, every note is typed by a person or sent through the Admin API. Your Google Ads edits, site releases and CRM changes don't appear by themselves.

None of this makes annotations bad. It makes them a sticky note on a chart, not a record of everything your team changed.

What do teams use instead of GA4 annotations?

Teams usually pick one of five options, from free and manual to paid and automatic.

• A shared spreadsheet or Notion page. Free and flexible, with as many columns as you like. It works until people stop updating it, and nobody sees it next to the chart. Our marketing change log template gives you the columns to start with.
• Looker Studio with a notes sheet. MeasureSchool describes a workaround for the time series annotations Looker Studio lacks: blend a Google Sheet of dates and notes with your GA4 data, joined on the date, and show the notes in a combo chart.
• A browser extension. Crystal Ball, also known as GAannotations, adds manual and automated annotations to GA4, Google Ads, YouTube and Wix charts, from sources such as Google Ads, GitHub, Shopify, WordPress and Google algorithm updates. It has a 7-day free trial.
• CoNote. A company logbook with 33 listed integrations that can also write its notes into GA4 as native annotations, within Google's limits.
• Changeline. A marketing change log: a to-scale timeline per client project, where Google Ads changes are imported and every other change is logged with date, owner, tags and reason.

How does Changeline compare with GA4 annotations and a spreadsheet?

GA4 annotations are best for a few dates on a chart, a spreadsheet for small disciplined teams, and Changeline for teams logging many changes across several clients.

The Free plan has no card and no time limit. Compare Changeline plans.

When are GA4 annotations the better choice?

Stay with GA4 annotations when you have one property, a handful of notable dates a month and an analyst who owns the notes. They cost nothing, they sit right on the chart, and everyone with GA4 access sees them.

They also work well next to a change log. Add a short annotation for big events, such as a site migration or a tracking fix, so anyone opening GA4 gets the hint, and keep the full detail in your change log. If you want notes to appear inside GA4 charts automatically, CoNote and Crystal Ball do that; Changeline does not write to GA4.

Move to a dedicated change log when you manage several clients or properties, when the people making changes don't have the Analyst role, or when you need the old and new values to explain a result.

How do you find which change caused a drop in GA4?

Put every change from the days before the drop on one timeline, rule out tracking first, then test one hypothesis at a time. GA4 shows you when the line moved; your change log tells you what moved it.

1. Confirm the drop is real: check tags, consent and the Google Tag Manager versions published that week.
2. List every change from the 7 days before: ad edits, budgets, landing pages, forms, CRM rules.
3. Line them up against the day the metric moved and pick the closest likely cause.
4. Test that one hypothesis, for example by checking the affected campaign, page or event on its own.

Example: a client asks why leads in GA4 fell on Tuesday. The GA4 chart has one annotation from last month, "New homepage". The agency's change log for that week shows a Target CPA cut from $40 to $32 on Friday, a new landing page on Saturday and GTM version 42 published on Monday. The form event stopped firing after Monday's publish, so the answer was the tracking change.

With every change on one timeline, the GTM publish sits right before the drop instead of hiding in another tool. Start a free change log in Changeline and connect Google Ads to bring in the last 30 days of edits automatically.