Shopify turns Analytics into an app platform for merchant data

Shopify developer changelog preview image for the Analytics platform update.Shopify Developers
Shopify developer changelog preview image for the Analytics platform update.Shopify Developers
Business & Career

Shopify has expanded Analytics into a developer platform for apps, adding queryable app data, ShopifyQL documentation, embeddable analytics components, annotations, and metric targets.

Shopify is turning Analytics into a platform surface that app developers can build on directly. The July 21 developer changelog says apps can now model, query, embed, and enrich analytics inside Shopify instead of running a separate warehouse, charting layer, locale handling, and admin-style UI.

For merchants, the practical change is that app data can sit closer to the reports they already use. For app teams, it creates a more native route for merchant-facing dashboards, attribution views, campaign markers, subscription metrics, and target tracking.

Shopify Analytics now accepts app-shaped data

The update starts with custom data. Shopify says metafield definitions can be marked as analytics-queryable, which lets those values appear as ShopifyQL dimensions alongside store data. An app could expose an order-level campaign source, a customer subscription status, or another merchant-specific attribute without forcing the merchant to sync that data into a separate BI system.

Shopify is also opening early access to App Events in Analytics. Apps can declare events in shopify.app.toml, emit them through the App Events API, and let merchants query FROM app_events in ShopifyQL. That matters for products where the event stream is the value: loyalty launches, email campaigns, subscription changes, review requests, operational alerts, or any app workflow that needs to be analyzed next to sales and customer data.

ShopifyQL becomes a documented app surface

The ShopifyQL API is now described as a first-class analytics query layer with schema-level reference documentation on shopify.dev. That gives developers a versioned surface for metrics and dimensions, with types, descriptions, and examples.

This is useful beyond hand-written dashboards. Public schema docs make it easier for code generators, internal tools, and AI-assisted development environments to produce valid ShopifyQL instead of guessing field names from examples. The tradeoff is clear: teams still need to design data definitions carefully, because a queryable metafield becomes part of the merchant's reporting vocabulary.

Apps can embed native analytics cards

Shopify is also exposing Analytics Web Components from the admin experience to third-party apps. The changelog names the metric card, metrics bar, and metrics bar date picker components. Developers load the analytics UI script after Polaris, enable Direct API access, and render charts from ShopifyQL queries inside their own app UI.

That reduces the amount of repeated work in commerce apps. A developer can embed a chart with one element instead of maintaining a charting library, formatting currencies and locales, and rebuilding visual patterns Shopify already uses in the admin. It also gives merchants a more consistent analytics experience across the admin and installed apps.

Annotations and metric targets add context to reports

Two API additions make the platform more than a chart renderer. Partner apps can create annotations on merchant charts through the GraphQL Admin API, with app attribution shown in the chart panel. Shopify lists required scopes for this path as read_analytics_annotations and write_analytics_annotations.

Metric targets are now a core GraphQL Admin API primitive as well. Apps can create, read, and overlay targets on charts, while merchants can track progress against goals such as total sales, ad-attributed revenue, or another metric that fits their store.

Shopify's merchant-facing Analytics update from June shows the same direction from the store owner's side: insights, annotations, metafield and metaobject filtering, metric targets, and a Flow action that can run ShopifyQL queries on a schedule. The developer update moves that pattern outward so app data and app UI can participate.

What app teams should check first

This is a platform opportunity, not a universal migration order. App teams should start by mapping which data belongs inside Shopify Analytics and which data still needs an external warehouse or customer-owned BI stack. High-value candidates are metrics merchants already review in Shopify: attribution, subscriptions, loyalty events, inventory-facing actions, campaign markers, and operational targets.

The early-access label on App Events in Analytics also matters. Teams should verify preview access, API version targets, Direct API access requirements, scopes, and merchant permissions before committing roadmap work. Existing dashboards do not need to disappear overnight, but new merchant-facing analytics should now be compared against Shopify's native path before another custom reporting stack is built.

Evidence

Shopify's July 21 developer changelog is the primary source for the platform update. Daily.dev's changelog mirror independently lists the same entry and timing. Shopify's June merchant-facing Analytics post supplies context for the store-level features that the new developer surface now extends to apps.