Executive summary
What: Analytics charts in Shopify admin now show which app added an annotation, identifying the source by app name or logo.
Why: An annotation timeline is only useful if you can trust where each marker came from. Attribution makes the timeline evidence rather than noise.
Who: Teams running frequent campaigns, launches or supplier changes who currently reconcile events against metrics in a separate spreadsheet.
What changed
Annotations are markers placed on a report's timeline for a specific date or date range: a product launch, a marketing campaign, a sale event, a supplier change, a landing page launch, a popup store, a business milestone. Shopify already generated some of these automatically from store activity such as a theme publish or an app install. What is new is attribution. When an app writes an annotation, the admin now shows which app it was. You can view the timeline against sales, sessions, conversion rate, average order value, units sold, returns and fulfillment performance, so the context sits directly under the metric it explains.
Why it matters
Most enterprise stores run somewhere between fifteen and forty apps, several of which touch merchandising, inventory or pricing. When three apps and two humans can all write to the same timeline, an unlabelled marker raises a question instead of answering one. Attribution changes the economics of investigation: you can look at a dip and immediately know whether the marker beside it came from your inventory system, your PIM, or a theme publish. That matters because the expensive part of analytics work is rarely reading the chart. It is the cross-team messaging that follows. The same reasoning applies to any structured conversion rate optimization program, where the value of a test depends on knowing what else changed in the same window. Annotations do not alter the underlying data, so there is no reporting risk in switching them on.
Role-specific impact
Marketers: campaign start and end dates now land on the same chart as conversion rate and average order value, which shortens the argument about whether a dip was seasonal or self inflicted.
Developers: if you maintain a private or custom app that touches launches, deployments or catalog changes, consider writing annotations from it. Your app's identity now appears on the marker, so the signal is attributable.
Store admins: audit which apps write annotations. A chatty integration can crowd the timeline and make the useful markers harder to find, so treat annotation volume as something to govern.
Use-case example
Real-world scenario
A specialty retailer watches conversion rate fall from 2.6 percent to 2.1 percent across a four day window. The first instinct is a checkout regression, and a developer starts bisecting recent theme deploys. Opening the annotations panel on the sessions and conversion report shows two markers in that window: a theme publish on day one, and a supplier change annotation written by the inventory app on day two. The theme publish is the obvious suspect, but the inventory marker lines up more closely with the drop, and a stock check confirms three top sellers went out of stock on that date. Time to root cause falls from roughly half a day of cross-team messages to about ten minutes inside a single report, and the theme deploy is cleared without a rollback.
Implementation checklist
Open a report you review weekly and turn on the annotations timeline.
List which apps currently write annotations and confirm each one earns its place on the chart.
Agree a house convention for what deserves an annotation: campaign launches, price changes, supplier switches, theme publishes.
Backfill the last quarter's significant events where your tooling supports it, so historical comparisons carry context.
Add an annotations review to the weekly trading meeting agenda.
If you maintain a custom app, add annotation writes to deployment and catalog change routines.
Retire the parallel events spreadsheet once the timeline is trusted and complete.
FAQ
Q: Do annotations change the underlying report data?
A: No. They are a context layer drawn on the visualization. Metrics, totals and exports are unaffected, which means there is no measurement risk in enabling them on reports your finance team relies on.
Q: Can we tell an app-written annotation from an automatic one?
A: Yes, and that is the substance of this update. Annotations added by an app now carry that app's name or logo, so you can separate integration-generated context from Shopify's own activity markers.
Resources
Annotations in your Shopify reports
Need guidance? Talk to Makro.