Shopify App Detector: Find Every App a Store Uses

Every public-facing Shopify store leaks its app stack into the page source. The chat widget, the upsell drawer, the review block, the analytics pixels - each one drops a script tag, a class name, or a CDN domain that maps back to a specific app. A Shopify app detector reads those signals and gives you the list in a few seconds.

I built our detector at ShopThemeDetector.com for exactly this. Paste a Shopify store URL, hit detect, and you get the theme plus a list of detected apps with links to their App Store pages. Below I’ll walk through how the detection actually works, what it catches and what it misses, and the four ways store owners get the most value from this kind of tool.

What Is a Shopify App Detector?

A Shopify app detector is a tool that takes a store’s URL, fetches the public storefront, and returns the list of third-party apps it has installed. You don’t need to log in to the store, install anything, or know the merchant. The data is already public - the detector just reads it for you.

The detector at shopthemedetector.com works in the browser. Paste the URL into the input box, click detect, and within a few seconds you get two outputs: the active theme (with its variant and Theme Store link) and the apps detected on the page you scanned. Each app entry links to its Shopify App Store listing so you can read pricing, reviews, and install it yourself.

How Does the Detection Actually Work?

Shopify apps don’t hide. When you install one, it adds code to your theme - either via the Online Store 2.0 app block system, a script tag injected at runtime, or a snippet the merchant pasted manually. That code carries fingerprints the detector can match.

The four main signals our detector looks for:

• Script source domains. Most apps load JavaScript from a known CDN, like cdn.judge.me for Judge.me reviews or loox.io for Loox. Match the domain, identify the app.
• CSS class prefixes and IDs. Apps drop their own DOM nodes with predictable class names. .spurit-easy-tabs means Easy Tabs by Spur-IT, #klaviyo-form means a Klaviyo embed.
• Meta tags and config blocks. Some apps register a window-level config object or a custom meta tag for their analytics, easy to grep for.
• Shopify app block markers. Apps using OS 2.0 blocks leave structured comments in the rendered HTML that name the app and block type.

Our detector keeps a signature database of around 1,000 apps and updates it as new apps ship. When a store has an app we haven’t fingerprinted yet, it shows up as “unknown integration” with the raw domain or class name, which is usually enough to identify it manually.

What the Detector Catches and What It Misses

An app has to leave a trace on the storefront to be detectable. That sounds obvious, but it shapes everything about how to read the results.

Reliably detected (storefront apps)

• Review apps (Judge.me, Loox, Yotpo, Stamped, Okendo)
• Upsell and cross-sell apps (Rebuy, Bold Upsell, In Cart Upsell)
• Chat widgets (Tidio, Gorgias, Shopify Inbox, Zendesk)
• Popups and email capture (Privy, Klaviyo, Justuno)
• Page builders (PageFly, Shogun, GemPages, EComposer)
• Analytics and pixels (GA4, Meta Pixel, TikTok, Triple Whale)
• Cart drawers and bundlers (Rebuy Smart Cart, Kaching Bundles, Slide Cart)
• Currency converters and translators (Shopify Geolocation, Langify, Weglot)
• Loyalty and rewards (Smile.io, Yotpo Loyalty, LoyaltyLion)

Usually missed (server-side and private apps)

• Inventory management (Stocky, Skubana, Cin7) - runs in the Shopify admin only
• Fulfillment apps (ShipStation, ShipBob, Easyship) - back-end integrations
• Accounting (QuickBooks, Xero) - never touches the storefront
• Print on demand (Printful, Printify) - shows up only if their cart logic injects scripts
• Private custom apps built for one merchant
• Shopify Plus admin tools (Launchpad, Shopify Flow) - admin-only

If you’re auditing a store and need a complete picture, the detector is the start, not the end. For server-side tools you have to look at job postings, public case studies, or merchant interviews.

Four Ways Store Owners Use App Detection

Competitor research

The most common use. You find three or four stores you compete with, run them through the detector, and see which review app, which upsell tool, which chat widget they’re all running. That tells you what the niche has settled on, where the spend goes, and which integrations are table stakes vs. nice-to-have. Pair this with a structured competitor analysis to get the rest of the picture.

Theme migration audits

Before you switch themes, run the detector on your own store. It lists every app currently loading scripts on your storefront. After you migrate, run it again. If an app dropped off the list, it means the new theme isn’t loading its assets - either you forgot to enable an app block, the app isn’t OS 2.0 compatible, or you need to paste a snippet that was wired into the old theme manually.

App stack cleanup

The detector also shows you the apps you forgot you had. The free trial you never canceled, the review app you replaced six months ago whose script is still injected, the old translator app that’s slowing down your home page. Run your own store through the detector and cross-reference with your billing - anything detected that you don’t pay for is a stale script you should remove. Anything you pay for that doesn’t show up is back-end and not pulling weight on the storefront.

Pre-acquisition due diligence

If you’re buying a store from a marketplace like Shopify’s Acquire or a flippa-style listing, the seller’s app stack is one of the things you want to verify before money changes hands. A high-converting store running ten paid storefront apps has a very different cost structure than one with the same revenue and three apps. Detection is the cheapest way to verify the seller’s tech-stack claims before you sign.

How to Get the Most Out of Each Scan

One scan of the home page catches the apps that load globally. A few practical tips for getting a complete picture:

1. Scan more than one URL. The home page catches site-wide tools (analytics, chat, currency). The product page reveals upsells, reviews, cart drawers, and stock widgets. The collection page surfaces filters and sorting apps. The checkout page (where accessible) shows the post-purchase upsells and tipping apps.
2. Run a known-good store first. If you’ve never used a detector, scan a store whose apps you already know (your own, or a friend’s). That calibrates what “complete coverage” looks like for the kind of niche you’re scanning.
3. Cross-check with the store’s source. If something feels off, view source on the page (right-click, “View Page Source”) and search for the app name. If it’s installed correctly the name or its CDN domain will appear somewhere in the HTML.
4. Note the absences. A store doing million-dollar revenue with no detected email capture, no detected review app, and no detected upsell tool is either (a) running everything server-side via Shopify Functions, or (b) lying about revenue. Both worth knowing.

Detector Tools Compared

Several tools sit in this category. Quick rundown of how they differ:

• Web-based detectors (like ours at shopthemedetector.com) - paste a URL, get results. No install. Best for one-off lookups or when you don’t want a browser extension.
• Chrome extensions - install once, click the icon while browsing any Shopify store. Faster for back-to-back research but only works in Chrome.
• API-based services - paid, give you the same data programmatically. Useful if you’re building a competitor monitoring dashboard or scraping at scale.

For most use cases - competitor scouting, an occasional audit, due diligence on a store you might buy - a free web detector is enough. The Chrome extension makes sense if you’re running ten scans a day. The API tier only pays off if you’re building tooling on top of detection.

Common Mistakes Reading Detector Output

Two false conclusions to avoid:

First, “no app detected” doesn’t mean “no app installed.” It means no public storefront fingerprint matched. The store might run the same job server-side, use a custom theme implementation that mimics an app, or have a private app built specifically for them. Detection is a floor, not a ceiling.

Second, “app detected” doesn’t always mean “the merchant is paying for it.” Some apps leave residual scripts after uninstall, especially older apps that injected snippets directly into theme.liquid instead of using OS 2.0 blocks. If something looks weirdly out of place in a store’s stack, treat it as a possible leftover, not an active integration.