> For the complete documentation index, see [llms.txt](https://help.rankability.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rankability.com/track/using-ga4-annotations.md).

# Using GA4 annotations

Mark important events on the GA4 trend chart timeline to correlate site changes, campaigns, or algorithm updates with traffic patterns.

GA4 annotations let you mark specific dates on the GA4 Performance chart with notes about events that may have influenced your traffic and engagement metrics. This creates a timeline of actions alongside your data, making it easy to spot cause-and-effect relationships.

## Adding an annotation

1. Click the **Annotate** button in the GA4 Performance card header.
2. Enter a **title** (required) – a short label for the event.
3. Add a **description** (optional) – more detail about what happened.
4. Select the **date** when the event occurred.
5. Choose a **category**:
   * **Content change** – Major content updates or new page launches.
   * **Algorithm update** – Google or platform algorithm changes.
   * **Link building** – Backlink campaigns or notable link acquisitions.
   * **Technical fix** – Site migrations, speed improvements, or infrastructure changes.
   * **Client event** – Business events like product launches, sales, or PR.
   * **Other** – Anything else worth noting.
6. Click **Save**.

## How annotations appear

Each annotation appears as a vertical dashed reference line on the chart at the corresponding date. The line color matches the category, making it easy to distinguish between different types of events. Hover over the colored dot at the top of the line to see the annotation title and description.

## Editing and deleting

Click on an annotation label below the chart to open it. From there you can edit the title, description, date, or category. To delete, use the delete button in the edit dialog.

## Tips for effective use

* Add annotations whenever you publish major content updates or make technical changes to the site.
* Use them to mark the start of link building campaigns so you can measure impact over time.
* When you see a traffic spike or drop, check if any annotations align with the date – this is often the fastest way to find the cause.
* GA4 annotations are separate from GSC annotations, so you can maintain independent timelines for each data source.

## Related articles

* [Connecting and using Google Analytics 4](/track/connecting-google-analytics.md) — Overview of the GA4 Performance card.
* [Using GSC annotations](/track/using-gsc-annotations.md) — The equivalent feature for the GSC chart.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.rankability.com/track/using-ga4-annotations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.