# E-commerce Store Leads (`mrdoe/ecommerce-store-leads`) Actor

Scrapes e-commerce store websites for platform, product count, social links, and contact info, and enriches leads with named contacts.

- **URL**: https://apify.com/mrdoe/ecommerce-store-leads.md
- **Developed by:** [MrDoe](https://apify.com/mrdoe) (community)
- **Categories:** E-commerce, Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 results

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

## E-commerce Store Leads + Verified Emails - Store Contacts, Platform & Product Data

Turn a list of e-commerce store URLs into structured sales leads - platform, approximate catalog size, social links, and named contacts, backed up by emails and phone numbers scraped directly from each store.

### What does this Actor do?

Give it one or more store URLs and it returns one structured record per contact found, including:

- **Store details** - name, website, domain, description, detected platform (Shopify, WooCommerce, BigCommerce, Magento, Wix, Squarespace), approximate product count, and social links (Instagram, Facebook, Twitter/X, TikTok)
- **Contact email** - named contacts with job title, department, confidence score, falling back to emails scraped directly from the store if none are found
- **Phone number** - scraped from the store's contact/about pages
- **Optional email verification** and **optional firmographics** (industry)

Nothing is guessed or invented - fields with no available data are returned as `null`.

### How it works

1. Fetches each store's homepage plus up to **Max contact/about pages per site** internal pages, scraping `mailto:`/`tel:` links and visible emails.
2. Detects the store's platform from homepage markup, reads social links from the page, and (for Shopify stores) checks the public `/products.json` endpoint for an approximate product count (capped at 250).
3. Looks up the domain for named contacts - the richest source of leads per store.
4. If none are found for a domain, falls back to the emails scraped directly from the store.
5. Optionally verifies each email's deliverability and enriches company firmographics, if enabled.

This Actor is HTTP-only (no headless browser), so it's fast and lightweight even across many stores.

### How to use

1. [Sign up](https://apify.com/sign-up) for a free Apify account.
2. Open this Actor and enter one or more **Store URLs**.
3. Set **Max leads per store** and **Max total leads** as needed.
4. Click **Start** and export results as JSON, CSV, Excel, or via API.

### Output

Each dataset item follows a standard lead shape shared across this Actor family, plus store-specific fields:

| Field | Description |
|---|---|
| `companyName`, `companyUrl`, `domain`, `companyWebsite`, `description` | Store identity, from the site itself |
| `platform` | Detected e-commerce platform, or `null` if not recognized |
| `productCount` | Approximate product count for Shopify stores (capped at 250), else `null` |
| `socialLinks` | `{ instagram, facebook, twitter, tiktok }`, each `null` if not found |
| `contactName`, `firstName`, `lastName`, `jobTitle`, `department`, `seniority` | Named contact (`null` if only an on-site email was found) |
| `email`, `emailType`, `emailConfidence`, `emailVerificationStatus`, `emailSources` | Contact email data |
| `phone` | Phone number scraped from the store |
| `source`, `sourceUrl`, `profileUrl`, `scrapedAt` | Provenance metadata |

Fields with no available data are returned as `null` rather than omitted or guessed.

### Cost & performance notes

- Enrichment is deduplicated per unique domain; email verification and firmographic enrichment are opt-in extras, off by default.
- Product count is only fetched for Shopify stores (its `/products.json` endpoint is public); other platforms return `null` rather than an unreliable estimate.
- Concurrency is kept conservative to stay reliable at scale.

# Actor input Schema

## `startUrls` (type: `array`):

E-commerce store URLs to scrape, e.g. https://www.example-store.com

## `maxContactPagesPerSite` (type: `integer`):

How many additional internal pages (contact, about, team, etc.) to check per store, beyond the homepage.

## `maxEmailsPerCompany` (type: `integer`):

Maximum number of contact records to return per store.

## `maxItems` (type: `integer`):

Overall cap on leads returned across all stores. Set to 0 for unlimited.

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

Proxy settings for the run.

## `enableContactEnrichment` (type: `boolean`):

When enabled, each store's domain is automatically looked up for named contacts and their emails. Falls back to on-site scraped emails if none are found.

## `enableEmailVerification` (type: `boolean`):

When enabled, every returned email is additionally checked for deliverability. Disabled by default.

## `enableCompanyEnrichment` (type: `boolean`):

When enabled, looks up each domain for industry/location data. Disabled by default.

## Actor input object example

```json
{
  "startUrls": [
    "https://www.allbirds.com"
  ],
  "maxContactPagesPerSite": 3,
  "maxEmailsPerCompany": 3,
  "maxItems": 0,
  "proxyConfiguration": {
    "useApifyProxy": true
  },
  "enableContactEnrichment": true,
  "enableEmailVerification": false,
  "enableCompanyEnrichment": false
}
```

# Actor output Schema

## `overview` (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 = {
    "startUrls": [
        "https://www.allbirds.com"
    ],
    "maxContactPagesPerSite": 3,
    "maxEmailsPerCompany": 3,
    "maxItems": 0,
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("mrdoe/ecommerce-store-leads").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 = {
    "startUrls": ["https://www.allbirds.com"],
    "maxContactPagesPerSite": 3,
    "maxEmailsPerCompany": 3,
    "maxItems": 0,
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("mrdoe/ecommerce-store-leads").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 '{
  "startUrls": [
    "https://www.allbirds.com"
  ],
  "maxContactPagesPerSite": 3,
  "maxEmailsPerCompany": 3,
  "maxItems": 0,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call mrdoe/ecommerce-store-leads --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,mrdoe/ecommerce-store-leads"
        }
    }
}

```

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/sAb0JVnybaJ0IHVX6/builds/6i35j4ZRdW1t7gy17/openapi.json