Shopify Store Leads

Shopify Store Leads finds public Shopify storefronts and returns one consolidated lead record per store. It uses direct HTTP requests by default, detects Shopify from public HTML and storefront endpoints, samples products, and enriches contact and social signals from a small set of same-site pages.

What it does

• Accepts store domains, URLs, or Apify startUrls.
• Confirms Shopify with multiple independent public signals.
• Extracts store title, description, country, currency, theme hints, technologies, emails, phones, social profiles, contact/about URLs, and product samples.
• Uses /products.json and /shop.json when those public endpoints are available.
• Enforces SSRF checks before every initial request and redirect, including DNS resolution against private and reserved addresses.
• Keeps concurrency, response size, redirects, pages, and product samples bounded.
• Supports an optional Apify or custom proxy for stores that block direct cloud traffic.

Input

Provide stores as domains or URLs, or startUrls as request-list objects. maxPagesPerStore defaults to 4, maxProducts to 20, and maxConcurrency to 5. defaultCountry is used only for local phone normalization. Proxy use is opt-in.

Output

One row is emitted per requested store. Successful rows have ok: true and isShopify: true. A failed, blocked, invalid, unreachable, or non-Shopify input becomes an ok: false diagnostic row. Diagnostics include an errorCode and are never charged.

Empty input emits a clearly labeled _sample: true row for the Apify input preview. Sample rows are never charged.

Billing and economics

The actor emits the pay-per-event event store only after a confirmed Shopify result has been written to the dataset. Non-Shopify sites and all diagnostic or sample rows do not call Actor.charge.

The planned price is $0.0045 per confirmed Shopify store, below the observed $0.00599 per-store competitor benchmark. Direct HTTP is the default because residential proxy bandwidth can erase the margin on small lead records. At the planned price, validate a representative cloud batch before publishing or enabling residential proxy by default.

Proxy and limitations

Some Shopify stores use bot protection, geoblocking, consent interstitials, or client-rendered content. A proxy can help with IP blocking but adds bandwidth cost and may still be blocked. This actor does not bypass authentication, CAPTCHAs, paywalls, checkout flows, or private APIs. It does not submit forms or contact stores.

The product endpoint is a public sample, not a guaranteed complete inventory. productCountType tells you whether the count is a storefront endpoint sample or unavailable.

Local development

npm install
npm test
npm run check
npm run smoke

The live smoke test uses SHOPIFY_SMOKE_URL when supplied and defaults to https://www.allbirds.com. It is intentionally local-only and does not deploy or publish the actor.