# Website Technology & Tracking Detector (`vex_workflow/website-tech-stack-detector`) Actor

Find out what any website runs on: CMS, e-commerce platform, analytics, ad pixels, marketing automation, chat, payments, reviews, consent tools, frameworks, hosting and CDN. Also extracts tracking IDs (GA4, GTM, Google Ads, Meta, TikTok and more). Bulk, fast, about 140 technologies.

- **URL**: https://apify.com/vex_workflow/website-tech-stack-detector.md
- **Developed by:** [Ian McCann](https://apify.com/vex_workflow) (community)
- **Categories:** Lead generation, Developer tools, SEO tools
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

### What does Website Technology & Tracking Detector do?

Paste a list of websites and get back, for each one, **the technologies it runs on**, grouped into useful buckets:

- **CMS and site builders**: WordPress, Drupal, Webflow, Wix, Squarespace, Framer, Ghost and more
- **E-commerce**: Shopify, WooCommerce, BigCommerce, Magento, PrestaShop and others
- **Analytics and tag managers**: GA4, Tag Manager, Segment, Mixpanel, Amplitude, Hotjar, Clarity and more
- **Advertising pixels**: Meta, Google Ads, LinkedIn, TikTok, Pinterest, Snap, Microsoft, Reddit, Criteo and more
- **Marketing**: HubSpot, Marketo, Klaviyo, Mailchimp, ActiveCampaign, SMS and pop-up tools
- **Chat and support**, **payments and BNPL**, **reviews**, **scheduling and forms**, **cookie consent**
- **Frameworks, hosting, CDN and web server**

It also pulls out **tracking IDs** found on the page: GA4 measurement IDs, GTM containers, Google Ads conversion IDs, AdSense publisher IDs, Meta and TikTok pixel IDs, HubSpot portal IDs and more.

About 140 technologies are covered. The signature list is our own and is updated over time.

### Who uses it?

- **Sales teams and agencies** qualifying leads by stack ("Shopify stores with no email tool", "WordPress sites running Google Ads")
- **SaaS companies** finding users of a competitor or a complementary tool
- **Marketers** auditing their own and clients' tracking setup (missing pixels, duplicate tag managers)
- **Analysts** sizing technology adoption across a domain list
- **AI agents** that need a fast "what does this site use?" answer

### How to use it

1. Add websites or domains to **Websites**, one per line.
2. Keep **Extract tracking IDs** on if you want the IDs.
3. Start. Filter the dataset by `ecommercePlatform`, `advertisingPixels` or any category.

#### Input example

```json
{ "websites": ["apify.com", "allbirds.com", "wordpress.org"] }
```

#### Output example (shortened)

```json
{
  "domain": "example-store.com",
  "status": "ok",
  "cms": null,
  "ecommercePlatform": "Shopify",
  "analytics": ["Google Tag Manager", "Microsoft Clarity"],
  "advertisingPixels": ["Meta Pixel", "TikTok Pixel"],
  "marketingTools": ["Klaviyo", "Attentive"],
  "hostingAndCdn": ["Cloudflare"],
  "trackingIds": { "googleTagManager": ["GTM-XXXXXXX"] },
  "technologyCount": 9
}
```

### How much does it cost?

| Event | Price |
|---|---|
| Actor start | $0.001 per run |
| Website analyzed | **$0.004** per website |

10,000 websites cost about **$40**. Unreachable websites and websites blocked by robots.txt are not charged.

### How it works and its limits

- The home page HTML, script URLs, response headers and cookies are matched against our signatures. No browser is used, so it is fast and cheap.
- Tools that load only after a click, a login or a consent banner may not be visible. Results show what the public home page reveals.
- robots.txt is respected by default. No logins, no anti-bot circumvention.
- Product and company names are used only to describe what was detected. This tool is not affiliated with any of them.

### FAQ

**Can I check inner pages?** Enter any URL, not only home pages. Each URL is one check.

**How accurate is it?** Detection is based on clear fingerprints like script hosts and generator tags, so false positives are rare. Server-side tools that leave no trace in the page can't be seen.

# Actor input Schema

## `websites` (type: `array`):

Websites or domains, one per line.

## `extractTrackingIds` (type: `boolean`):

Also return the analytics, tag manager and ad pixel IDs found in the page (for example G-, GTM-, AW- IDs).

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

How many websites to check at the same time.

## `respectRobotsTxt` (type: `boolean`):

Skip websites whose robots.txt asks crawlers not to read the home page.

## Actor input object example

```json
{
  "websites": [
    "apify.com",
    "allbirds.com"
  ],
  "extractTrackingIds": true,
  "concurrency": 15,
  "respectRobotsTxt": true
}
```

# Actor output Schema

## `dataset` (type: `string`):

One row per website with detected technologies grouped by category and tracking IDs.

## `summary` (type: `string`):

Run summary with websites analyzed, failed and blocked.

# 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 = {
    "websites": [
        "apify.com",
        "allbirds.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("vex_workflow/website-tech-stack-detector").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 = { "websites": [
        "apify.com",
        "allbirds.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("vex_workflow/website-tech-stack-detector").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 '{
  "websites": [
    "apify.com",
    "allbirds.com"
  ]
}' |
apify call vex_workflow/website-tech-stack-detector --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,vex_workflow/website-tech-stack-detector"
        }
    }
}
```

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/A7faImb3lJf0vxgPa/builds/2CmYqEo92ko4bX58w/openapi.json