Analytics apps and tools for a Shopify store

Entry price is the lowest monthly price the vendor lists; “Free” means a free plan or free self-hosting. “At 100k” is the monthly price for 100,000 units, as the vendor bills them. Dates under statuses, prices and script sizes show when we checked them. See how we check every value.

What puts a tool on this page

A tool is counted here when the vendor publishes its own way into a Shopify store: an app in the Shopify App Store, or an installation guide written for Shopify. Instructions that say the snippet works on any website do not count, and neither does an app written by somebody else. Those cases read “Partly” in the Shopify row of a card, and two tools sit there: OpenPanel, whose Shopify page describes the standard script tag plus purchase events you write yourself, and Pretty Insights, which advertises a Shopify integration on its homepage that its documentation does not cover.

The line is drawn at the vendor because of maintenance. Shopify keeps changing what an outside script may do inside a store: its documentation records that additional scripts and script tags were sunset on the thank-you and order-status pages, for Plus stores in August 2025 and for other stores in August 2026. A route the vendor owns is the one rewritten on dates like those.

Services closed to new customers stay out of collections, so the count here is smaller than the number of tools that document Shopify. Hotjar is the one missing on that ground; its row stays in the full table, and the change sits in the market log.

What the store already counts

Shopify reports sessions, visitors, orders, revenue and a conversion breakdown on every plan, with acquisition reports for referrers and locations. Two properties decide when that is enough. The reports are assembled from what the platform already records, so an event of your own has nowhere to live in them. And sessions-based metrics reach back only to 1 October 2022, with sessions closing at midnight UTC rather than in the store’s time zone.

The Shopify analytics guide goes through those reports, their limits and the two-part installation: the theme for the storefront, a customer-events pixel for checkout. What sends store owners to the table above is usually one of four things: events they define themselves, one report that also covers a blog on another domain, campaign information carried through to orders, and a say in where data is kept and for how long.

An app, a guide, or the Shopify API

The routes behind a single “Yes” are not the same piece of work. An app installs from the store admin, survives a theme change and can register a web pixel extension that Shopify runs in a sandbox: “Microsoft Clarity: AI Insights” comes from Microsoft Clarity, “Piwik PRO Analytics” from Piwik PRO SA with Checkout named on the listing, “Amplitude: Customer Analytics” from Amplitude.

A guide route puts the snippet into theme.liquid and adds a custom pixel for the checkout events, which is what Plausible, Fathom, Mixpanel and several lighter tools document; Pirsch states plainly that a plugin may exist in the App Store but the vendor provides none itself. Heap takes a third road: its Shopify source works server-side, pulling order events and customer properties through the Shopify API.

Two checks take a minute: the developer name on a listing, which tells you whether the app comes from the analytics vendor, and the date on a guide, because what it replaced had expiry dates.

How to choose

  1. Decide what has to reach the checkout. If purchases and revenue belong in the tool, the route needs a pixel or a server-side connection, since a theme snippet never loads there.
  2. Settle storage and cookies before features. The Data in EU and Cookieless columns narrow the table, and both are hard to change later.
  3. Read the unit on the bill. Sessions, pageviews, events and users all appear here, and none matches Shopify’s own session, which ends after 30 minutes of inactivity and again at midnight UTC.
  4. Check the publisher and the age of the route: the developer on a listing, the last update of a guide, and whether it still describes checkout the way Shopify documents it now.
  5. Compare retention and price at your traffic last, in each vendor’s unit; the methodology covers those columns.

Questions and answers

Does an app from the App Store see the checkout?

That depends on the app and on your Shopify plan. Shopify runs app pixels in a sandbox and hands them standard customer events, so what a tool reports from checkout comes from that payload, not from reading the page. Vendors record their own limits: Clarity states that checkout and post-checkout pages are covered through Shopify’s pixel on Shopify Plus, and Hotjar said third-party scripts do not run in the built-in checkout.

How is this page different from the Shopify guide?

This page is the list and the rule behind it: which vendors publish a Shopify route of their own, with the measured and documented values beside each. The guide is the instruction: what the built-in reports show, where they stop, how the snippet and the pixel are added, and which events a store is worth counting.

A tool I use is missing. Why?

Three reasons cover most absences. The vendor documents no Shopify route, so the row reads “Partly” or stays empty and the tool sits in the full table. The service takes no new customers. Or the integration comes from another developer, which is recorded on the card rather than counted here.

Guides on this topic

Other collections