What apps does a Shopify store use?

To detect Shopify apps, you need evidence, not guesses. Many Shopify apps leave a public trace: a script loaded from the vendor's own servers, a stylesheet, a theme app extension, or markup with the vendor's own class names. The App Detector reads those traces on the page you enter and, when it can, on one product page, then matches them against a registry of known signatures.

Each detection shows the technology's name and category, the type of evidence that was seen (a script address, a stylesheet, an inline loader, an element id or a class name), a confidence level and a link to the vendor. Public identifiers that every visitor's browser receives, such as a Google Tag Manager container id, are shown when they are part of the evidence.

Categories

  • Reviews and Social Proof: review widgets and rating badges.
  • Marketing and Analytics: analytics and advertising tags, email and SMS marketing.
  • Customer Support: chat and help-desk widgets.
  • Loyalty and Rewards: points and rewards programs.
  • Upselling and Conversion: upsell and recommendation tools, search and filters, and pay-later messaging.
  • Subscriptions: subscription and recurring-order apps.
  • Other: page builders, translation, consent banners, accessibility widgets and shipment tracking.

How confidence is decided

High means the page loads a script, stylesheet or app extension from the vendor's own address. Medium means a marker only that vendor uses, such as its own class prefix or configuration object, was found. Two different kinds of medium evidence agreeing make a high. Weak signals on their own are not shown at all, so the list contains no guesses.

A link to a vendor's website is never treated as evidence. Mentioning an app is not the same as installing it, and generic words such as "reviews" or "chat" never count.

Why this is not the full list of installed apps

Only publicly detectable technologies are shown. This is not a complete list of installed Shopify apps. Many apps work only in the Shopify admin, at checkout or in the back office, and leave nothing on the storefront. Others load only after a visitor scrolls, accepts cookies or adds something to the cart. ORVX cannot see a store's private list of installed apps, and the detector never claims to.

When a theme app extension is loaded that matches no known signature, it is listed separately as an unidentified app embed, with its folder name as the only claim made.

Questions

Can it detect apps on stores built with a headless front end?

Fewer of them. A headless storefront often loads its scripts after the first page load, so less is visible in its HTML. The report says when a page appears to be drawn mostly by JavaScript.

How are new apps added?

Each technology is one entry in a signature registry, with the specific public signals that identify it. The detection engine does not change when the registry grows.

Worked examples

Illustrative figures, not benchmarks.

A review app

Illustrative: the page loads a script from a review vendor's own address. That is high confidence, and the address is shown.

A marker only

Illustrative: only a vendor's class name is found. That is medium confidence, and the report says so.

An unknown embed

Illustrative: a theme app extension matches no known signature. It is listed as unidentified, with its folder name as the only claim.

Common mistakes

  • Assuming the list is complete: back-office apps leave no trace.
  • Copying an app because a big store loads it.
  • Reading a link to a vendor as proof of an install.
  • Checking only the home page: many apps load on product pages.

Questions

Why is an app I know about missing?

It may run only in the admin or at checkout, or load after a visitor acts.

Do I need a Chrome extension?

No. It runs from this page.