Website Tech Stack Detector avatar

Website Tech Stack Detector

Pricing

Pay per event

Go to Apify Store
Website Tech Stack Detector

Website Tech Stack Detector

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.

Pricing

Pay per event

Rating

0.0

(0)

Developer

David Chicaiza

David Chicaiza

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

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 only10
Rendered40

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.