See all services → Shopify Plus Partner
Analytics Global

Report on App Events Directly Inside Your Shopify Analytics

Supported apps can now send events into Shopify Analytics, queryable through ShopifyQL with an app_events dataset. Useful for comparing app activity, but the join limits keep it short of attribution.

Executive summary

What changed

Reports now offer an App Events category in the configuration panel, so you can pull app metrics and dimensions into reports you already use. The same data is queryable in ShopifyQL by selecting from app_events, grouped by app or time period.

Every app event carries four common fields: app_name identifies the sending app and makes cross-app comparison possible, event_handle names the event, event_count counts occurrences, and latest_event_timestamp gives the most recent one. Standard events follow a pattern such as shopify.marketing.email_sent, each with its own metrics and dimensions, so email sending exposes an emails_sent metric alongside campaign and message type dimensions.

Apps can also define custom events, referenced with dot notation of the form event, app handle, event name, then field, with hyphenated handles quoted. Two limits are worth memorising. Custom event dimensions cover only the last 30 days, so queries grouping on one need a recent date range. And app_events cannot be queried alongside another dataset, so selecting from sales and app_events together is unsupported.

Why it matters

The honest framing is that this is an activity view, not an attribution tool. Because app_events will not join to sales in a single query, you cannot ask Shopify what revenue followed a loyalty redemption or an email send. What you can do is compare volume and consistency across apps on one surface: how many emails each platform actually sent, whether a loyalty integration stopped firing last Tuesday.

That matters more than it sounds, because silent integration failure is common and expensive in enterprise stacks, and an app that quietly stops sending is usually found through a revenue dip weeks later. A reportable latest_event_timestamp turns that into a monitorable signal. The same logic applies to the workflow layer: if you orchestrate messaging through Flow and Klaviyo triggers, event volume becomes an independent check that automation is firing as designed.

Coverage is the practical constraint. Available data depends on which installed apps support the feature and what each developer sends, so the dataset will be patchy at first. Audit before building reporting on it, and expect to re-audit as vendors adopt it.

Role-specific impact

Use-case example

Real-world scenario

A specialty retailer runs two email platforms during a migration, plus loyalty and reviews apps. Finance asks why email costs rose while campaign output looked flat. That answer previously required exports from both vendors and most of a day reconciling spreadsheets. With app events the team groups emails_sent by app_name over 60 days in one ShopifyQL query and finds the old platform still sending roughly 40 percent of total volume, four months after the migration was declared complete, because three automations were never ported or switched off. The query takes minutes and retires a duplicate subscription nobody had reason to question.

Implementation checklist

  1. Open a report, find the App Events category, and see which installed apps actually appear.
  2. List the event handles each app sends, then build one cross-app comparison report for a metric you already argue about internally.
  3. Add a latest_event_timestamp check for every business-critical app and define what a stale value means.
  4. Keep date ranges inside 30 days for queries grouping on a custom event dimension.
  5. Avoid reports that require joining app events to sales, and ask your vendors whether they plan to send standard events.

FAQ

Q: Can we attribute revenue to app activity with this?

A: No. The app_events dataset cannot be queried together with another dataset such as sales, so revenue attribution still requires your own warehouse or the app vendor's own reporting.

Q: Why do we see nothing from some of our apps?

A: Availability depends on whether each app's developer sends events to Shopify. An absent app is not a misconfiguration on your side, it has simply not adopted the feature.

Resources

Querying app events with ShopifyQL

Need guidance? Talk to Makro.