Home › Guides › E-commerce & app intelligence

Digital footprint as qualification data: Shopify stores and App Store publishers

Firmographics tell you how big a company is. Digital footprint tells you what it actually does — whether it sells online, on which platform, how deep its catalogue runs, whether it ships a mobile app and how often it updates. This guide covers two of the cleanest public signals: Shopify detection with catalogue extraction, and App Store publisher profiles.

Shopify: a definitive yes or no

Most technology detection is probabilistic — a script tag here, a header there, a confidence score. Shopify is different: storefronts expose their catalogue through a predictable public endpoint, so a domain either answers in the Shopify shape or it does not.

That makes it a useful qualification filter for anyone selling into DTC commerce. Run a prospect list through detection and you have split it into "runs Shopify" and "does not" with certainty rather than inference.

One design point matters more than it sounds: a detector should return an explicit negative for non-Shopify domains. In our own dataset the default input deliberately includes apple.com — which is not a Shopify store — so that the output shows what a negative looks like: a row with isShopify: false and a note explaining it, rather than silence. A silent empty result is indistinguishable from a broken request, and that ambiguity causes more bad analysis than any missing field.

What the catalogue gives you

For stores that do run Shopify, the public catalogue is rich:

{
  "companyName": "kith.com",
  "isShopify": true,
  "productTitle": "VANS GS Old Skool 36 Pearlized - Multi",
  "vendor": "VANS",
  "productType": "Low Top Sneakers",
  "minPrice": 75.00,
  "variantCount": 8,
  "available": true
}

Note vendor: for multi-brand retailers this reveals the brand mix a store carries — which brands a retailer stocks is competitive intelligence for anyone else selling those categories. Price range across variants, variant and image counts, and the created/published/updated dates together describe catalogue depth and how actively the store is maintained.

Shopify detection & catalogue data →

App Store: engineering investment made visible

A company's mobile app is evidence firmographics cannot provide. Employee count does not tell you whether a business is technically active; a mobile app updated last week does.

App Store listings publish the publishing entity (the legal name, not just the brand), the app's category, price, rating, rating count, current version, release and update dates, supported languages, file size and minimum OS. In our measured run every one of those fields populated on every row.

{
  "companyName": "Monzo Bank Limited",
  "appName": "Monzo Bank - Mobile Banking",
  "bundleId": "io.b2a.BankProd",
  "industry": "Finance",
  "website": "https://monzo.com"
}

Three derived signals are worth building:

• Release cadence — the gap between release date and last update, plus the version string, separates an actively developed app from an abandoned one.
• Rating volume — review count indicates real user scale far better than headcount does.
• Language list — which markets a company has actually localised for, as opposed to which it claims to serve.

Set the storefront deliberately. The App Store is per-country: ratings, review counts, price and availability all differ. Querying the US storefront for a UK-focused fintech produces a misleading profile.

App Store publisher data →

Combining footprint with firmographics

The combination is what makes this useful. A company with a deep Shopify catalogue, a well-rated app updated monthly and three open engineering roles is a materially different prospect from one with the same headcount and none of those things — and no firmographic database will tell you the difference.

Practical cautions

1. Catalogue size is not revenue. A store with 5,000 SKUs may be a dropshipper. Use catalogue depth alongside other signals, not as a proxy for scale.
2. App publisher names differ from trading names. Monzo Bank Limited publishes the app; the brand is Monzo. Match on the publisher's legal name when joining to registry data.
3. Product text is copyrighted. Using catalogue data for analysis is one thing; republishing descriptions and images is another.

The date fields are the activity signal

Catalogue records carry three timestamps that most people ignore: when a product was created, when it was published, and when it was last updated. Individually they are metadata. Aggregated across a store they are the best available proxy for how actively a business is being run.

• Recent creations — the store is adding range. A business expanding its catalogue is a business investing.
• Recent updates across many products — prices, descriptions or variants are being maintained. Someone is working on this store daily.
• Nothing touched in a year — the store is running, technically, but nobody is minding it. For a vendor selling operational tooling that is either a poor prospect or a very specific one.
• A large gap between created and published — organised merchandising, with products staged before release. That is an operator with process, which usually means an operator who buys software.

The same reasoning applies to the App Store side. The gap between original release date and last update is a maintenance signal, and a version string that has not moved in eighteen months says something a rating never will.

This is the general principle behind digital-footprint qualification: a static fact tells you what a company is, a timestamp tells you whether it is awake. Catalogue size, app rating and headcount are all static facts. Update cadence is the field that separates a business from an artefact of one.

Frequently asked questions

How do you detect Shopify?

Storefronts answer on a predictable public catalogue endpoint, so detection is definitive rather than a fingerprint guess — and a good detector reports the negative explicitly.

What's in a Shopify catalogue?

Product title, vendor, type, price range, variant and image counts, availability, tags and lifecycle dates. Not inventory levels or customer data.

Why does app data matter for B2B?

Release cadence and rating volume show engineering investment and real user scale — things firmographics cannot see.

Does app data differ by country?

Yes. Ratings, price and availability are per-storefront; set the country to the market you care about.

Detect Shopify stores → See all 87 datasets