🌐 Marketing Stack Enricher

Give it a list of company domains; it returns one CRM-ready record per domain describing the marketing stack (analytics, tag managers, CRM/marketing automation, live chat, attribution/CDP, ad pixels, A/B testing, email). It works only from each company's own public pages, and it honours robots.txt per domain: any page a site disallows is skipped, never bypassed.

Tools are returned under a controlled martech taxonomy as campaign-usable columns, each with detection evidence and confidence.

Difference from a general tech-stack detector: martech only, campaign-usable columns.

Output is one marketing_stack row per result; billing is pay-per-event, the value event being one martech record (a $0.02 start fee per run, then $0.05 per martech record).

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out.

📊 Sample Output

Real rows from run icOhfFioniOc5YVNl on build 0.1.7 (2026-09-17), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

domain	checked_pages	martech	columns	status	charged_event
vercel.com	["https://vercel.com/"]	[{"category": "Advertising Pixels", "tool": "LinkedIn Insight", "evide	{"Advertising Pixels": ["LinkedIn Insight"]}	ok	martech_record
stripe.com	["https://stripe.com/"]	[{"category": "Attribution / CDP", "tool": "Branch", "evidence": "app.	{"Attribution / CDP": ["Branch"]}	ok	martech_record

The run finished with the status message: NORMAL: 2 of 2 domains enriched ({'ok': 2}). martech_record billable=2

✅ What you get

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):

• record_type (string) — e.g. marketing_stack
• domain (string/null) — e.g. vercel.com
• checked_pages (array/null) — e.g. ["https://vercel.com/"]
• robots_skipped (array/null) — null in every sample row
• observed_at (string/null) — e.g. 2026-09-17T17:34:50Z
• source_url (string/null) — e.g. https://vercel.com/
• martech (array/null) — e.g. [{"category": "Advertising Pixels", "tool": "LinkedIn Insight", "evidence": "sna
• columns (object/null) — e.g. {"Advertising Pixels": ["LinkedIn Insight"]}
• status (string/null) — e.g. ok
• charged_event (string/null) — e.g. martech_record
• terminal (string/null) — null in every sample row
• supplied (integer/null) — null in every sample row
• processed (integer/null) — null in every sample row
• status_counts (object/null) — null in every sample row
• billed (integer/null) — null in every sample row

Every run also writes a RUN_RECEIPT record to its key-value store with the source checks it made and the counts it charged — diagnostics never land in the paid dataset.

⚙️ Sample inputs

1. Quick start — the Store example (this is what the sample above came from)

{
  "domains": [
    "vercel.com",
    "stripe.com"
  ],
  "maxRecords": 10
}

The sample run charged exactly: 1 × $0.02 apify-actor-start + 2 × $0.05 martech_record = $0.12 on the Free tier — every delivered row was billed.

2. A smaller, narrowed run

{
  "domains": [
    "vercel.com",
    "stripe.com"
  ],
  "maxRecords": 5
}

Caps the run at 5 rows — about $0.27 on the Free tier ($0.02 start + 5 × $0.05).

3. A full-size run

{
  "domains": [
    "vercel.com",
    "stripe.com"
  ],
  "maxRecords": 100
}

Up to 100 rows (the schema default for maxRecords) — about $5.02 on the Free tier ($0.02 start + 100 × $0.05) if the source has that many.

🧾 JSON sample record

One real record from run icOhfFioniOc5YVNl, exactly as it lands in the dataset (emails masked, long text shortened):

{
  "record_type": "marketing_stack",
  "domain": "vercel.com",
  "checked_pages": [
    "https://vercel.com/"
  ],
  "robots_skipped": [],
  "observed_at": "2026-09-17T17:34:50Z",
  "source_url": "https://vercel.com/",
  "martech": [
    {
      "category": "Advertising Pixels",
      "tool": "LinkedIn Insight",
      "evidence": "snap.licdn.com",
      "evidence_url": "https://vercel.com/",
      "confidence": "high"
    }
  ],
  "columns": {
    "Advertising Pixels": [
      "LinkedIn Insight"
    ]
  },
  "status": "ok",
  "charged_event": "martech_record"
}

🔧 How it works

Transport. Plain HTTPS from the Apify platform, no proxy. robots.txt is read first and a disallowed path is never fetched.

Terminal states. A run ends NORMAL, CAPPED (your cap was reached), PARTIAL (something was withheld and the message says what), GENUINE_EMPTY (the source was read and truly had nothing in scope) or BLOCKED (the source refused or changed shape — the run FAILS loud and bills nothing). A zero-row run is never reported as a silent success.

Charging. Each martech record is charged at the moment it is pushed (martech_record); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

How it works

For each domain supplied, the actor runs a robots preflight on every page it wants to read. Allowed pages are fetched from the company's own site; disallowed pages are skipped and recorded in robots_skipped. Each record reports a status:

• ok — data was found (this is the only status that bills)
• no_data — the site was reachable but nothing matched
• robots_blocked — the page(s) needed were disallowed by robots.txt (skipped, never bypassed)
• unreachable — the site did not respond

A domain that is robots-blocked, unreachable, or yields no data is delivered as a record for your visibility but bills nothing. If every supplied domain is unreachable, the run fails loudly (an egress outage is never delivered as an empty success).

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

💰 Pricing example

Event	Free	Bronze	Silver	Gold
Actor Start (apify-actor-start)	$0.02	$0.02	$0.02	$0.02
Martech Record (martech_record)	$0.05	$0.04	$0.04	$0.03

Worked at the live Free-tier price:

• 2 martech records: $0.02 start + 2 × $0.05 = $0.12
• 25 martech records: $0.02 start + 25 × $0.05 = $1.27
• 100 martech records: $0.02 start + 100 × $0.05 = $5.02

A run that delivers zero rows charges the $0.02 start fee only. A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 1024 MB.

Yield on the sample run: NORMAL: 2 of 2 domains enriched ({'ok': 2}). martech_record billable=2. maxRecords is a hard ceiling on what is delivered and billed, never a target.

⚖️ Legal & ToS

This actor reads public data only. It collects only what the source publishes to any visitor, keeps to the source's robots rules (checked on every run), identifies itself, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

❓ FAQ

Q: Do I need an API key or a login?
A: No. the input schema has no key field and the actor carries no secrets.

Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input; BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee only.

Q: How many rows can one run return?
A: Up to maxRecords (default 100). Raise the cap for a bigger run; you pay per delivered row.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs. Put it on a schedule for a continuous feed.

Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

Q: How is this different from the other web QA and enrichment tools actors?
A: Same output shape and billing model; this one covers Marketing Stack Enricher. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

Q: Are there rate limits?
A: The actor paces itself against the source and honours its robots rules; there is no per-buyer limit beyond your Apify plan's concurrency.

🆘 Troubleshooting

• Run FAILED with BLOCKED → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
• Status says CAPPED → your cap (maxRecords) was reached → raise it for a bigger run.
• Input validation error on start → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
• Run TIMED-OUT → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.

🔗 Related Actors

• Crossref DOI Metadata QA — A per-DOI QA verdict from official Crossref metadata — each DOI returns valid, not_found, or metadata_incomplete with every missing required field na…
• HTML to PDF Evidence Renderer — Renders each HTML document or permitted public URL to a hashed, print-pinned PDF evidence artifact: page count, resource-failure ledger, input+output…
• Internal Link Architecture Verifier — Runs a bounded same-origin crawl unioned with your sitemap, builds the internal link graph, and returns one evidenced verdict per page: orphan-from-s…
• PDF Text Intake Auditor — Judges whether a PDF is ingestible before you spend on extraction: text-layer presence, page count, encryption, scan likelihood, per-page text densit…
• Responsive Visual QA Matrix — Runs a headless-Chromium responsive QA pass on each URL across desktop/tablet/mobile and returns one verdict per URL: per-viewport layout metrics, a…
• 🧠 Review Sentiment Analyzer — Themes, Trends & Complaints — Turn any review set into themes, complaints, sentiment % and trends
• 🏢 About NexGenData — NexGen Watch is NexGenData's fleet of 256 public monitoring and lookup actors built on official sources, pay-per-result. Browse the catalog at apify.com/nexgenwatch.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.