Executive summary
- What changed: Supported time-series reports in Shopify Analytics now accept annotations: a title, description, date or date range, and a type.
- Why it matters: The explanation for a spike or a dip lives next to the data instead of in someone's memory, a spreadsheet or a Slack thread.
- Who should care: Anyone who reads reports for a living. Annotations are visible to staff with the Reports permission, which makes this a team practice rather than a personal one.
What changed
Shopify Analytics has added an annotations panel to supported time-series reports. From it you can record the moments that shape a trend line: a campaign launch, a creator mention, a supplier change, a promotion, an operational fix. Each annotation takes a title, a description, a single date or a date range, and an annotation type. Shopify offers auto-detected categories, and you can also set your own.
Annotations are editable and deletable, and each one records who created it. You can search and filter them, and the panel surfaces context from three sources together: notes your team wrote, context from installed apps, and context from Shopify itself. Visibility follows the Reports permission, so everyone who can read the report can read the annotations on it.
Why it matters
Attribution decay is a familiar problem at enterprise scale. A report shows that conversion rate moved four percent in week 32. Someone knew why at the time. Twelve weeks later, during planning, nobody does, and the team either re-derives it from campaign calendars and purchase orders or quietly ignores the anomaly. Both outcomes are expensive, and the second one is worse because it trains people to distrust the reports.
Keeping that context in the reporting tool rather than beside it changes the economics of the question. The cost of writing an annotation is about thirty seconds at the moment you already know the answer. The cost of reconstructing it later is an hour of someone senior's time, and the reconstruction is often wrong.
Two secondary benefits are worth noting. Because annotations carry an author, they create accountability for interpretation, not just for numbers. And because app-sourced and Shopify-sourced context appears in the same panel, a platform change or an app event that moved a metric is visible to the person reading the report rather than discoverable only by someone who knows to go looking. This is the same discipline that makes experimentation programs work, which is why it pairs naturally with structured conversion rate optimization.
Role-specific impact
- Marketers: Annotate campaign start and end dates, creator mentions and promotion windows as they happen. A date range rather than a single date is usually the honest representation for a campaign.
- Developers: Annotate deploys that touch the storefront, checkout or tracking. A theme release or an analytics change that shifts a metric should be findable from the report, not only from the commit log.
- Store admins: Annotate operational events: a stockout, a supplier delay, a shipping carrier change, a tax or pricing update. Agree on a naming convention before the panel fills with inconsistent entries.
Use-case example
Real-world scenario
A specialty food brand saw sessions rise 38 percent across four days in September with conversion rate falling by nearly half over the same window. The pattern looked alarming in isolation. An annotation recorded at the time, noting a creator mention on a video platform, would have explained it in one line: high-volume, low-intent traffic, performing exactly as that traffic always does. Instead the team spent most of a planning session relitigating it. The fix costs thirty seconds of typing per event, and it compounds: a year in, your reports carry their own explanation.
Implementation checklist
- Confirm which staff hold the Reports permission, since that is who can see and create annotations.
- Agree on a short annotation taxonomy covering campaigns, deploys, supply events and pricing changes.
- Decide whether to use the auto-detected categories or your own, and document the choice.
- Set a naming convention for titles so search stays useful at a few hundred entries.
- Backfill the last quarter's significant events while anyone still remembers them.
- Add annotating to the definition of done for campaign launches and storefront deploys.
- Review the panel in your monthly reporting meeting and correct or remove entries that proved wrong.
FAQ
Q: Who can see annotations our team writes?
A: Staff with the Reports permission. Treat them as internal documentation visible across the team, not private notes, and write them accordingly.
Q: Do annotations replace our existing reporting documentation?
A: Not entirely. They are strongest for point-in-time events attached to a specific metric and date. Methodology, definitions and anything that needs version history still belong in a document.
Resources
Shopify reports overview in the Help Center
Need guidance? Talk to Makro.