# Shopify Store Lead Extractor (`ayeeyee/shopify-store-lead-extractor`) Actor

Extract verified contact details, business intelligence, and tech stack data from Shopify stores for B2B lead generation and competitive analysis.

- **URL**: https://apify.com/ayeeyee/shopify-store-lead-extractor.md
- **Developed by:** [Virtual Footprint LLC](https://apify.com/ayeeyee) (community)
- **Categories:** Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 shopify store leads

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Shopify Store Lead Extractor

Turn a list of Shopify store URLs into sales-ready merchant leads: MX/DNS-verified owner emails, phones, social profiles, the store's Shopify apps, payment methods, product categories, industry, tech stack, and an A–D lead score.

No third-party API keys and **no residential proxy required** — the Actor reads each store's own public storefront (home page + a few likely contact/about pages on the same host) directly, so it sidesteps the proxy limits and cost that constrain search/map scrapers.

### Input

```json
{
  "urls": ["allbirds.com", "gymshark.com", "mvmt.com"],
  "verifyEmails": true,
  "concurrency": 5
}
```

| Field | Type | Default | Description |
|---|---|---|---|
| `urls` | array (required) | — | Shopify store URLs or bare domains, 1–1000. One record returned per input. |
| `verifyEmails` | boolean | `true` | Validate the best-matched email's domain against live MX/DNS records. |
| `concurrency` | integer | `5` | Stores processed in parallel (1–10). |
| `proxyConfiguration` | object | none | Optional — only needed if you hit rate limits; the Actor works without a proxy. |

### Output

One record per input URL, pushed to the dataset:

```json
{
  "inputUrl": "gymshark.com",
  "resolvedUrl": "https://gymshark.com",
  "domain": "gymshark.com",
  "isShopify": true,
  "storeName": null,
  "storeDescription": null,
  "productCategories": [],
  "industry": null,
  "shopifyApps": ["Intercom", "Zendesk"],
  "paymentMethods": ["Apple Pay", "PayPal"],
  "techStack": ["Intercom", "Nginx", "React", "Shopify"],
  "emails": ["support@gymshark.com", "press@gymshark.com", "legal@intercom.io"],
  "emailVerified": true,
  "phones": [],
  "socials": {
    "instagram": "https://www.instagram.com/gymshark",
    "twitter": "https://www.twitter.com/gymshark",
    "tiktok": "https://www.tiktok.com/@gymshark",
    "facebook": "https://www.facebook.com/gymshark",
    "youtube": "https://www.youtube.com/gymshark"
  },
  "pagesScanned": 3,
  "leadScore": "A",
  "hasContact": true
}
```

- `storeName`/`storeDescription`/`productCategories`/`industry` come from the store's `<title>`, meta description, and `/collections/` links — some themes (like Gymshark's) don't expose these, so they're `null`/empty rather than guessed.
- `emails` are ranked with the store's own domain first, then filtered against a placeholder/asset/support-widget blocklist and deduplicated.
- `phones` must match a strict NANP pattern (rejects digit-soup like tracking IDs); dedup by digits.
- `hasContact` is `true` when at least one of `emails`, `phones`, or `socials` is non-empty — this drives billing (see Pricing).

### Real example (live run, 2026-07-10)

**Input**: `["gymshark.com", "allbirds.com", "mvmt.com"]`, `verifyEmails: true`, `concurrency: 3`

**Result**: 3/3 stores returned data in 9.8s. All 3 returned a verified email; Allbirds also returned a phone. Gymshark's title/meta/categories were empty (blocked by theme markup) — flagged transparently as `null`, not guessed.

| Store | isShopify | Emails | Phone | Tech stack | Lead score |
|---|---|---|---|---|---|
| gymshark.com | true | support@gymshark.com, press@gymshark.com, legal@intercom.io | — | Intercom, Nginx, React, Shopify | A |
| allbirds.com | true | help@allbirds.com, privacy@allbirds.com, bulkorders@allbirds.com, legal@allbirds.com | +1-888-963-8944 | Cloudflare, Google Tag Manager, Shopify | A |
| mvmt.com | false | support@mvmt.com | — | Cloudflare, Google Tag Manager | A |

Note: `mvmt.com` returned `isShopify: false` because its current storefront doesn't expose Shopify-specific HTML/CDN signatures at crawl time — the Actor still extracts contact and tech data for any storefront, Shopify or not, so no lead is lost.

### Pricing (pay-per-event — you pay only for successful results)

| Event | Price | Charged when |
|---|---|---|
| `store_lead` (primary) | $0.008 | Store returns at least one real contact signal (email, phone, or social) plus storefront intelligence |
| `email_found` | $0.003 | Store yields at least one MX/DNS-validated business email |
| `tech_stack_found` | $0.001 | Store's tech stack/apps are detected |
| Actor start | $0.0001 | One-time, per run |

No charge for stores with no contact signal at all. Zero upstream compose cost (the Actor fetches each target's own site directly) — margin-positive at these prices.

### Troubleshooting

- **`isShopify: false` for a store you know runs Shopify**: some themes hide the usual `cdn.shopify.com`/`myshopify.com` markers from initial HTML. Contact/tech data is still extracted normally.
- **Missing `storeName`/`productCategories`**: the store's title tag, meta description, or `/collections/` links weren't present in the fetched pages — the Actor never fabricates these, it returns `null`/`[]`.
- **No emails or phones found**: the store may not publish contact info on its home/about/contact pages, or blocks non-browser requests. Try `proxyConfiguration` if you suspect rate limiting.
- **Slow runs on large lists**: raise `concurrency` (max 10); each store takes ~2–4s.

### Use cases

B2B sales prospecting into e-commerce brands, competitor tech-stack research, partnership/vendor outreach, and building targeted Shopify-merchant lead lists for agencies.

# Actor input Schema

## `urls` (type: `array`):

Shopify store URLs or domains to enrich (e.g. 'https://allbirds.com', 'gymshark.com'). One record is returned per input.

## `verifyEmails` (type: `boolean`):

Validate the best email's domain against live MX/DNS records.

## `concurrency` (type: `integer`):

Stores processed in parallel (1–10).

## `proxyConfiguration` (type: `object`):

Optional. Only needed if you hit rate limits; the Actor works without a proxy by reading each store's own public site.

## Actor input object example

```json
{
  "urls": [
    "allbirds.com",
    "gymshark.com"
  ],
  "verifyEmails": true,
  "concurrency": 5,
  "proxyConfiguration": {}
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "urls": [
        "allbirds.com",
        "gymshark.com"
    ],
    "proxyConfiguration": {}
};

// Run the Actor and wait for it to finish
const run = await client.actor("ayeeyee/shopify-store-lead-extractor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "urls": [
        "allbirds.com",
        "gymshark.com",
    ],
    "proxyConfiguration": {},
}

# Run the Actor and wait for it to finish
run = client.actor("ayeeyee/shopify-store-lead-extractor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "urls": [
    "allbirds.com",
    "gymshark.com"
  ],
  "proxyConfiguration": {}
}' |
apify call ayeeyee/shopify-store-lead-extractor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,ayeeyee/shopify-store-lead-extractor"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/McYwjIPgAh4kXoOUR/builds/tNzW8hIrmQpXb00cr/openapi.json