# Website Tech Stack Detector (`fullspeedtram/website-tech-stack-detector`) Actor

Detect a website's technology stack in a real browser. Finds the analytics, ad tech, CDPs, chat widgets and payment providers that HTML-only scanners miss, and tracks what changes between scans.

- **URL**: https://apify.com/fullspeedtram/website-tech-stack-detector.md
- **Developed by:** [David Chicaiza](https://apify.com/fullspeedtram) (community)
- **Categories:** Business, Developer tools, Lead generation
- **Stats:** 2 total users, 1 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?

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

## Website Tech Stack Detector

Detects a website's tech stack **in a real browser**, so it sees what loads after the HTML arrives.

### Why rendering changes the answer

Most detectors pattern-match the served HTML. That finds the CMS and the ecommerce platform, and misses what a tag manager loads.

Across 5 live sites, only the method differing:

| | Technologies found |
|---|---|
| HTML only | 10 |
| Rendered | **40** |

The gap is what buyers want: Google Analytics 4 (missed on 4 of 5), Google Tag Manager, Meta Pixel, Braze, mParticle, Intercom, Datadog RUM, OneTrust, Algolia.

Every record carries `renderOnlyTechnologies`: the subset an HTML-only scanner cannot find.

### Enrich a lead list

Point `inputDatasetId` at another Actor's run: any lead list, company search or directory scrape. Every row comes back with its stack attached, so you enrich your own list instead of joining a second table. The website column is detected from the data.

Rows sharing a website are **scanned once and charged once**, because lead lists repeat companies.

### Multiple pages per site

Payment providers live at checkout, chat widgets on contact pages. The scanner follows internal links to the higher-signal pages and merges them into one record, reporting each technology's `foundOn` page.

### Change detection

Set `trackChanges` and each scan is compared against the last for that domain. `added` and `removed` only contain technologies anchored to a page **both** scans reached. Anything else returns as `inconclusive`, because a page that timed out is not a site that dropped Stripe.

### Output contract

One record per input row, always. An unreachable site returns an `error` field, not nothing. **You are charged per site successfully analysed**; failures and empty results cost nothing.

### Categories

Analytics, tag managers, ad tech, CDPs, chat, A/B testing, session replay, payments, ecommerce, frameworks, CMS, CDN, consent, error tracking, marketing automation, site search, auth.

# Actor input Schema

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

Domains or URLs to analyse, for example example.com or https://example.com. One record is returned per site. Leave empty if you are enriching a lead list instead.

## `inputDatasetId` (type: `string`):

Instead of typing websites, point this at the dataset of another Actor's run: any lead list, company search or directory scrape. Every row comes back with its technology stack attached, so you enrich your own list rather than getting a second table to join by hand. Rows sharing a website are scanned once and charged once.

## `domainField` (type: `string`):

Which column of that dataset holds the company website. Detected from the data by default, so set it only to correct a wrong guess.

## `passthroughFields` (type: `array`):

Which of your original columns to keep on the enriched rows. Empty means all of them, which is usually what you want. Every row also carries sourceItemIndex so you can join back by position.

## `maxLeads` (type: `integer`):

Cap on how many rows to read from that dataset.

## `maxPagesPerSite` (type: `integer`):

How many pages to scan per site. The scanner starts at the URL you give it and then follows internal links to higher-signal pages such as pricing, checkout and contact, where payment and chat tools live. 1 scans only the entry page.

## `categories` (type: `array`):

Restrict the report to certain categories. Leave empty to return everything detected.

## `trackChanges` (type: `boolean`):

Compare this scan against the previous one for the same domain and report which technologies were added or removed. The first scan of a domain establishes the baseline.

## `trackingStoreName` (type: `string`):

Named key-value store holding your baselines. Reuse the same name across runs to keep comparing against your own history.

## `onlyReportChanges` (type: `boolean`):

Skip sites whose stack is identical to the previous scan. Useful for monitoring a large list on a schedule. Sites with no baseline yet are always returned.

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

How many sites to scan in parallel.

## `timeoutSecs` (type: `integer`):

Maximum time to wait for a single page to load.

## `settleMs` (type: `integer`):

How long to wait after load for tags that arrive late, such as anything a tag manager or consent layer installs. Too short and the scan does not just miss them, it makes the same site look like it adopts and drops a pixel on alternate scans. Lower it only if you care more about speed than about a stable answer.

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

Datacenter proxy is the default and is sufficient for nearly every site, because a company's own marketing pages have no reason to block a reader. The country defaults to US and is worth keeping fixed: consent platforms gate marketing tags on the visitor's geography, so an unpinned proxy makes the same site look like it adopts and drops pixels between scans.

## Actor input object example

```json
{
  "urls": [
    "https://www.patagonia.com"
  ],
  "maxLeads": 1000,
  "maxPagesPerSite": 3,
  "trackChanges": false,
  "trackingStoreName": "technographics-baseline",
  "onlyReportChanges": false,
  "concurrency": 5,
  "timeoutSecs": 30,
  "settleMs": 6000,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyCountry": "US"
  }
}
```

# Actor output Schema

## `stacks` (type: `string`):

Every scanned site with its detected technologies, evidence and change report.

## `stacksCsv` (type: `string`):

The same results as a spreadsheet-friendly CSV.

## `runDetails` (type: `string`):

Logs and run statistics for this run.

# 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": [
        "https://www.patagonia.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("fullspeedtram/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 = { "urls": ["https://www.patagonia.com"] }

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

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,fullspeedtram/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/ZOApk8702JXyMMp0d/builds/oZDgccjjZMmZUhXQD/openapi.json