How to Find Out Which Tools a Shopify Store Uses

To find out which tools a Shopify store uses, you just need to observe what's visible from the outside: the page source code, the tracking scripts loaded on load, and the logos displayed at checkout. No access to the store's admin is needed for this.

You'll see how to inspect a product page to spot traces of an app, how to distinguish an installed advertising pixel from an actually active campaign, and which elements of the purchase funnel reveal the payment or shipping services used by the seller. You'll also see the most common mistakes in this type of analysis, and how to bring all these signals together in a single view, without opening ten different tabs.

Which tools can be spotted on a Shopify store

A Shopify store leaves visible traces without you needing admin access. By looking at the theme, the page code and the checkout funnel, you can already spot most of the tools used by the seller.

These traces fall into a few main categories:

• The theme and its structure: certain CSS file names or folder names reveal a paid theme, such as Debutify or a modified Dawn.
• The installed apps: a customer review widget displayed under the product page, for example Loox or Judge.me, leaves an identifiable script in the code.
• Advertising tracking and analytics scripts: a Meta pixel or a Google Ads tag loaded when clicking "Add to cart".
• Payment tools: the logos displayed at the checkout step, Shop Pay, PayPal or Klarna for example.
• Carriers and shipping solutions: a "Delivered by" mention or specific tracking in the confirmation email.
• Additional marketing tools: sign up pop up, live chat, upsell in the checkout funnel.

Each visible element corresponds to a specific tool, but none of them tells you whether that tool is actually active or just installed. That is the nuance you will learn to spot in the following sections.

How to inspect a product page's source code

To see the code of a product page, two methods are enough: view the page source or open the browser inspector. Both give access to the HTML loaded by the store, along with the scripts it has added.

View the page source

1. Open the product page you're interested in.
2. Right click then "View Page Source" (or Ctrl+U on Windows, Cmd+Option+U on Mac).
3. Use the browser's search (Ctrl+F) to look for the words script src, cdn.shopify.com/extensions or apps.shopify.com.

These paths often point to the name of the installed app. For example, a file named with "klaviyo" or "judgeme" in its URL gives away the tool used, even without knowing the store's interface.

Use the inspector

1. Right click on the page then "Inspect".
2. Go to the "Network" tab and reload the page.
3. Sort requests by domain to spot the ones coming from a third party service rather than the Shopify theme itself.

This method also shows requests loaded with a delay, which the plain page source doesn't always reveal. It takes a bit more effort, but gives a more complete view of the tools actually running on the page.

How to spot installed tracking pixels and scripts

Where to look for pixels

In the "Network" tab you already opened, filter by keyword: "facebook", "google", "tiktok", "pixel", "gtag" or "analytics". You'll see requests appear to domains like connect.facebook.net or googletagmanager.com. In the source code, also look for <script> tags placed just before the closing </head> tag: this is often where stores paste these scripts.

A few concrete examples:

• A call to connect.facebook.net signals an installed Meta Pixel.
• A gtag.js or analytics.js script indicates Google Analytics or Google Ads.
• An analytics.tiktok.com domain reveals the TikTok pixel.

What this really tells you

Finding a pixel only proves that a tracking tool is in place on the store. It's not proof that an advertising campaign is currently running. A store may install a Meta pixel in anticipation of a future campaign, then never launch it, or may have stopped it months ago. To know whether an ad is actually being served, you need to check each platform's official ad libraries, not just spot the script in the code.

How to identify the payment and shipping tools displayed

The purchase funnel shows clues that the source code alone doesn't always show clearly. These elements appear at checkout or delivery, not necessarily on the product page.

To spot them, move forward in the customer journey as if you were about to buy, without validating the final order:

• Cart page: the payment method logos at the bottom of the page often indicate the provider used (for example Shop Pay, PayPal or a local banking processor).
• Checkout page: the name displayed in the URL or in the footer of this step sometimes reveals the integrated payment platform.
• Delivery fields: some themes display the name of the carrier or aggregator as soon as you enter an address, even before paying.
• Delivery time mentions: a precise mention such as "shipped from" or "delivered by" points to a third party logistics service rather than a standard carrier.

One detail to keep in mind: a displayed logo does not guarantee that this payment method actually works for all customers. Some stores display several logos for illustrative purposes, without each one being active. Always check by pushing the journey through to the confirmation step, without validating the purchase.

Common mistakes when analyzing a store's tools

When analyzing a store from the outside, certain conclusions seem logical but are false. Here are the most common ones.

• Confusing a detected pixel with an active campaign: a Meta pixel present in the code means the tracking tool is installed, not that an ad is currently running. A store can keep its pixel after having stopped its campaigns for several months.
• Believing you see everything without accessing the admin: the source code shows the scripts loaded client side, not the internal settings. An inventory management dashboard, a billing tool or an internally connected CRM remain invisible from a public page.
• Taking a logo as proof that something works: as seen above for payments, a displayed logo does not confirm that the tool is active for every visitor.
• Ignoring changes over time: a store changes apps regularly. A script spotted today can disappear the following week if the merchant is testing another tool.
• Relying on a single type of signal: spotting a customer reviews script says nothing about the actual sales volume. Cross-referencing several clues gives a more reliable picture than a single isolated detail.

How Evidio brings these signals together in one analysis

All the methods seen above (source code, pixels, payment logos) require manual searching, page by page. Evidio automates this reading.

The tool reads the public store the same way a visitor would, then gathers what it finds into a single profile: detected apps, tracking pixels, catalog, estimated traffic and contacts. You avoid opening the inspector on every product page to find a script or a carrier logo.

Specifically, a store's profile displays:

• The complete list of detected applications and technologies, among more than 370 recognized.
• The advertising pixels installed, with the reminder that a detected pixel does not prove a campaign is active today.
• An opportunity score out of 100, which combines up to 15 measurable factors such as traffic, advertising pixels or catalog size.

As with manual inspection, Evidio only sees what leaves a visible trace on the store side: an application that runs entirely server side remains invisible, regardless of the method used. The difference mainly comes down to time saved: instead of cross referencing several tabs and several pages, you find apps, pixels and other technical signals gathered on a single profile, viewable directly from your browser.

What is the next step

Spotting the tools used by a Shopify store comes down to two steps: opening the source code to list scripts and tags, then cross-referencing these clues with what shows up at checkout, payment logos and carrier mentions. This method works on any public store, with no account or admin access needed.

To test it in practice, pick a specific store, ideally a competitor you already follow. Open its best-selling product page, inspect the code, note the external domain names in the network requests, then spot the advertising pixels in the page's head. Do the same on its checkout page if it's accessible.

If you want to save the time spent opening multiple tabs, run an Evidio analysis on that same URL: you'll find apps, pixels and other technical signals gathered on a single report, without changing the underlying method, just without the manual work.

Next step

Take the URL of a store you're already watching and compare what you find by hand with what an Evidio report shows for the same address. You'll quickly see where manual inspection hits its limits. Feature details are listed on the features page.