Shopify app detector: the apps a store loads, and the ones that stay invisible
Enter a store address and we read the homepage source its server sends back, then name the apps behind the scripts it loads. Anything we cannot identify is listed as unknown instead of guessed.
Why anyone looks up another store's apps
Every app on a storefront was a decision somebody pays for. Someone looked at a problem, whether abandoned carts, missing reviews or support questions piling up, and picked a tool to deal with it. The list of a running store shows you which of those problems were considered serious enough to spend money on.
Often the missing entries tell you more than the present ones. A store in your niche, at your price point, with no review widget, no chat and no popup is telling you those three things are not the reason it works. That lesson is cheaper than installing all three and finding out yourself.
So read the result as a list of questions, not a shopping list. For every name you recognise, ask what job it is doing on that page and whether you have that job at all. The honest answer is usually that your problem is a different one, and the app would just cost you money.
What a page source can show, and what it cannot
This tool reads exactly one thing: the HTML that the store's homepage delivers to a browser once. From that it collects the addresses of the scripts the page loads and matches them against a list of known providers. That is the whole method, and therefore also the whole limit.
Anything that does not load a script of its own in that source stays invisible. We run no JavaScript, so a file that another script fetches after the page has loaded never reaches us. Apps that work on the shop's server, functions built into the theme, tools that only appear in the cart or the checkout, and everything Shopify itself provides leave no readable trace either. An empty category is never proof that a store has nothing there.
The other direction matters just as much. A script domain we cannot place is reported as unknown rather than given a plausible name, because a wrong answer here is worse than no answer. Shopify's own files and the large advertising networks are left out on purpose, so a missing Meta or TikTok pixel in this list says nothing either way. And a loaded script only proves the file is loading, not that the feature behind it is configured, switched on or actually in use.
The stack is the cheapest part to copy
The most common mistake is to read an app list as a recipe: the store is doing well and runs these eight tools, so it must be the eight tools. Almost never. The offer, the product cost, the buying of traffic and the person deciding what happens next week do the work; the apps are the part a stranger can see.
Copying also has a direct price. Every tool on that list would be another recurring line in your cost sheet, and every script another file each visitor's browser has to fetch. Moving a large store's stack into a small store usually brings the costs along without the volume that justified them.
Comparison is what makes the result useful. Check three or four stores in the same niche and the same price range and look at what turns up everywhere. One store's choice is taste; the same tool at every serious seller in a niche suggests the job it does is unavoidable there. That pattern survives the limits of this method far better than any single result.
Frequently asked questions
Why does this store show almost no apps?
Three entirely ordinary explanations. The store may have solved much of it inside the theme, in which case the code is part of the page instead of arriving as a provider's script. It may use apps that work on Shopify's side or only appear in the cart and the checkout, and neither touches the homepage. And some stores genuinely run on very little. A short list is a real result, but a result about the homepage, not about the business.
What are the unidentified script domains?
They are addresses the page loads that we could not match to any provider we know. Some belong to apps missing from our list, some to an agency or a developer who built something custom, others to marketing or measurement services. We show up to twelve of them with their domain so you can look them up yourself. A guess that sounds convincing would be worse than an honest gap.
Does the store owner notice, and is any private data involved?
The tool requests the same homepage anyone can open in a browser, once, and reads what the server sends back. No login, no account, nothing that is not already delivered to every visitor. Because no JavaScript runs on our side, the request lands in the shop's server log rather than in its visitor statistics. Check the same address again shortly afterwards and you get the stored result, without the shop being contacted twice.
Should I install the same apps?
Start from your problem, not from their list. If you have no reviews, a review widget solves nothing; if no support questions are reaching you, a chat window mostly adds a button. Use the result to see what is common in your niche, then test one thing at a time so you can tell what actually changed. A stack assembled by copying is the hardest one to take apart later.