NewAnalytics

Annotations
Annotation markers that overlay "changes in your metrics" and "events that happened in your store"
on the same chart

On a day your conversion rate dropped, just hover over a marker to learn that "a theme was published that same day." Product publications, store changes, and system events appear right on your data as color-coded markers. No setup required—they're generated automatically from your store activity.

What's on this page
  1. What's actually changing (a 30-second overview)
  2. How it works: from event to chart
  3. The 3 categories annotations cover
  4. How to use it (3 steps) and controls
  5. Spec summary: what it can do / not documented
  6. 5 points developers should know
  7. 3 use cases you can put to work
  8. A one-line summary for your pitch

1What's actually changing

Until now, when "conversion rate dropped on Tuesday → what happened?", you had no choice but to dig through other tools or your own memory to find out.
Annotations is a feature thatoverlays events that happened in your store, as color-coded markers, on the same chart as your data.
?

Before: you see the numbers but not the cause

You could only guess why the graph moved, relying on other tools or a teammate's memory.

Now: events overlay your data

Hover over a marker to see "a theme was published that day," and click to list every event from that day.

A concrete example from the post : conversion rate drops on Tuesday → hover over the marker → you discover "a new theme was published that same day" → click to open the annotations panel, and every event that could be the cause—every product published and every app installed that day—is laid out day by day.

2How it works: from event to chart

Store activity Product published / Theme published App installed / System No setup · collected automatically Annotations are auto-generated nothing to configure Visualization panel Show Toggle ON Hover for details Markers appear instantly
Annotations areauto-generated from store activity. No setup or configuration needed—just turn on "Show annotations" in a report and the markers appear right away.

3The 3 categories annotations cover

As of today, annotations cover the following 3 categories. The color coding is illustrative, used only for explanation on this page.

Product events

Product events

Published / unpublished.
Ranked by revenue, so high-impact events always appear at the top.

Store changes

Store changes

Theme published / app installed / uninstalled.

System events

System events

Data delays / metric definition changes.You can tell whether a movement in the numbers reflects a real change or is caused by data..

Product events Store changes System events

4How to use it (3 steps) and controls

1

Open any report

open any report: works in any report.

2

Turn on "Show annotations"

Turn on the toggle in the Visualization panel.

3

Markers appear instantly

Markers show up on the chart right away.

What you can do in the annotations panel

Hover / click

Hover over a marker to see its details. Click to open the annotations panel and view that day'sdaily breakdown(such as every product published and every app installed).

Filter by event type

You can narrow down to a specific event type, such as "product publishes only" or "system events only."

Move between days with the arrows

Use the arrow buttons to move back and forth between dates and spot patterns across time.

5Spec summary: what's supported / not stated

ItemDetails
Applicable reportsAny Available in any report (open any report)
How to enableTurn on the "Show annotations" toggle in the Visualization panel
DisplayOn the day an event occursColor-coded markersare displayed. Hover for details, click for a daily breakdown
FilteringFilter by event type from the annotations panel (e.g., product launches only / system events only)
NavigationMove between dates with the arrow buttons to spot patterns
CoverageThree categories: product events / store changes / system events (as of today)
Product orderingBy revenue High-impact events surface at the top
SetupNot required Auto-generated from store activity (no setup & nothing to configure)
Supported plans / countriesNot stated
API / Webhook / ExportNot stated
Manual annotations / custom annotationsNot stated(only auto-generated events are mentioned)

6Five points engineers should know

1. Zero configuration, auto-generated

Annotations are auto-generated from store activity, with no settings to configure. No implementation or integration work is needed—merchants and operators just turn it on.

2. Three data source categories

Product events / store changes / system events. Actions that can move the numbers—installing an app, publishing a theme, launching a product, and so on—serve as event sources.

3. Type filter + daily navigation

Filter by event type in the annotations panel and move between days with the arrows. Root-cause isolation runs on two actions: "filter → step through days."

4. Use System events to isolate "data-driven" causes

Because data delays and metric-definition changes appear as annotations,whether a shift in the numbers reflects a real-world change or a data-side eventcan be distinguished. A key signal for preventing misreads of your analytics.

API ?

5. API / Webhook / Export and supported plans are not stated

The article describes only the behavior in the admin (reports + annotations panel). Whether data can be retrieved via the Admin API or webhooks, exported to CSV/BI, and which plans and countries are supported arenot stated. If you're considering automation or external BI integration, separate verification is needed.

7Three use cases you can apply to your work

CVR and events
USE CASE 1

Cut root-cause investigation of KPI anomalies down to "a single hover"

Challenge
When conversion rate or sales drop on a given day, the cause isn't obvious, so you spend time investigating by jumping between other tools or relying on a colleague's memory.
What to do
Turn on "Show annotations" in the relevant report. Hover over the marker on the day that dipped, then click to open the annotations panel and review every event from that day, broken down by day.
Result
You can instantly pinpoint a likely cause—for example, "we published a theme on Tuesday"—cutting the effort and lead time of root-cause investigation.
Technical notes
No setup required, generated automatically. The annotations panel's daily breakdown lists every product published and every app installed.
¥¥¥ ¥¥ ¥
USE CASE 2

Instantly see which product launches drove sales, ranked by revenue

Challenge
On days when you publish a large number of products for a sale or new arrivals, it's hard to tell which launch actually drove the sales impact.
What to do
Use product event annotations. Product annotations are ranked by revenue, so the highest-impact publishing events appear at the top.
Result
You can identify winning tactics and products faster, and reuse that as supporting data for your next launch plan or assortment decisions.
Technical notes
Applies to Product events (published / unpublished). Ordering is based on revenue. There's no mention of whether aggregation can be automated or exported.
A drop after a change
USE CASE 3

Regression monitoring for app/theme changes

Challenge
When metrics shift after installing or uninstalling an app or publishing a theme, judging whether the change caused it depends on individual know-how.
What to do
In the annotations panel, filter by the "Store changes" type and use the arrow navigation to compare the days before and after a change marker. Also check system events (data delays, metric definition changes) to rule out misreadings.
Result
You can catch KPI degradation caused by a change early, speeding up decisions on rollback or isolating the cause.
Technical notes
Combine Store changes (theme published / app installed / uninstalled) with System events. You can tell whether a shift in the numbers is real or caused by the data.

8A one-line summary you can use in a pitch

"An annotation feature that automatically overlays product launches, store changes, and system events onto your analytics charts ascolor-coded markers.
Zero setup—just turn it on in any report—and product events are sorted by revenue.
Pinpoint "the reason the numbers moved" with a single hover, cutting the effort of root-cause investigation."