Cookie CMP Scanner avatar

Cookie CMP Scanner

Pricing

from $15.00 / 1,000 browser page checkeds

Go to Apify Store
Cookie CMP Scanner

Cookie CMP Scanner

Inventory cookies, consent banners, CMP vendor hints, Consent Mode signals, tracker categories, and privacy risk recommendations from supplied page snapshots.

Pricing

from $15.00 / 1,000 browser page checkeds

Rating

0.0

(0)

Developer

junipr

junipr

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Categories

Share

Store Positioning

Store title: Cookie CMP Scanner

Short description: Inventory cookies, consent banners, CMP vendor hints, Consent Mode signals, tracker categories, and privacy risk recommendations from supplied page snapshots.

SEO title: Cookie CMP Scanner — browser, screenshot, and rendered-page audit

SEO description: Inventory cookies, consent banners, CMP vendor hints, Consent Mode signals, tracker categories, and privacy risk recommendations from supplied page snapshots. Use it when rendered pages, screenshots, dynamic UI, or browser-visible evidence matters, with explicit caps and cost controls.

Categories: SEO_TOOLS, AUTOMATION

Keywords: cookie, cmp, scanner, browser/screenshot/rendered-page actor

Fixed-Inclusive PPE Pricing

This actor uses pay-per-event pricing. Event prices include Apify platform usage; users are not expected to pay a separate platform-usage pass-through charge for the configured pricing model.

  • Tier: B1 — Browser/screenshot/rendered-page actor
  • Primary event: browser-page-checked at $0.01500 base
  • Default max charge: $50.00
  • Store discounts: FREE/BRONZE base, SILVER discounted, GOLD deepest approved discount

Event set:

  • actor-start: base $0.05000, GOLD $0.04400. Cookie Cmp Scanner: charged when actor start is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
  • browser-page-checked: base $0.01500, GOLD $0.01320. Cookie Cmp Scanner: charged when browser page checked is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
  • screenshot-captured: base $0.01000, GOLD $0.00880. Cookie Cmp Scanner: charged when screenshot captured is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
  • issue-detected: base $0.01300, GOLD $0.01140. Cookie Cmp Scanner: charged when issue detected is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
  • report-generated: base $0.10000, GOLD $0.08800. Cookie Cmp Scanner: charged when report generated is completed. The price includes Apify platform usage; no separate usage pass-through is intended.

Public Task Concepts

  • Audit Cookie CMP controls with capped supplied targets
  • Find high-priority Cookie CMP issues before release
  • Validate Cookie CMP evidence from supplied pages
  • Prioritize Cookie CMP fixes with severity and proof
  • Export Cookie CMP QA rows for client review

Inventory cookies, consent banners, CMP vendor hints, Google Consent Mode signals, tracker categories, and privacy risk recommendations from supplied page snapshots.

This actor is fixture-first by default: it analyzes HTML, headers, cookie banner text, and cookie snapshots supplied in the input. It does not launch a browser, run Playwright, or fetch URLs unless fetchUrls is explicitly set to true.

What It Checks

  • CMP vendor hints for OneTrust, Cookiebot, Didomi, TrustArc, Quantcast Choice, Osano, CookieYes, iubenda, Sourcepoint, and Termly.
  • Google Consent Mode signals such as ad_storage, analytics_storage, ad_user_data, and ad_personalization.
  • IAB TCF indicators including __tcfapi, __cmp, euconsent-v2, and IABTCF_* cookies.
  • Cookie categories: necessary, analytics, marketing, preferences, functional, and unknown.
  • Banner controls for accept, reject, preferences, and privacy policy links.
  • Privacy risk signals such as tracking without a detected CMP, missing reject controls, long-lived marketing cookies, and consent granted by default.

Input Example

Set maxChargeUsd to a finite run budget. It defaults to $10; the actor stops before paid work or withholds uncharged reports when the next event would exceed the cap.

{
"targets": [
{
"sourceId": "home-page-snapshot",
"sourceUrl": "https://example.com",
"html": "<script src=\"https://cdn.cookielaw.org/scripttemplates/otSDKStub.js\"></script><script>gtag('consent','default',{ad_storage:'denied',analytics_storage:'denied'});</script><div id=\"onetrust-banner-sdk\"><button>Accept all</button><button>Reject all</button><button>Preferences</button><a href=\"/privacy\">Privacy Policy</a></div>",
"headers": {
"set-cookie": [
"OptanonConsent=1; Max-Age=31536000",
"_ga=GA1; Max-Age=63072000",
"_fbp=fb.1; Max-Age=7776000"
]
}
}
],
"fetchUrls": false,
"includeReport": true,
"maxTargets": 1
}

Output

Each dataset item represents one scanned snapshot:

{
"sourceId": "home-page-snapshot",
"status": "warn",
"severity": "low",
"privacyHealthScore": 88,
"cmpVendorNames": ["OneTrust"],
"consentModeDetected": true,
"cookieCategoryCounts": {
"necessary": 1,
"analytics": 1,
"marketing": 1,
"preferences": 0,
"functional": 0,
"unknown": 0
},
"riskSignalCodes": ["marketing-cookies-present"],
"recommendations": ["Confirm marketing cookies are blocked until valid consent is collected."]
}

When includeReport is enabled, the actor also writes:

  • COOKIE_CMP_RESULTS.json
  • COOKIE_CMP_SUMMARY.json
  • COOKIE_CMP_REPORT.md

Optional Live Fetch

Set fetchUrls to true and provide urls to fetch HTML and response headers with Node fetch. This path is capped by maxTargets, fetchTimeoutMs, and maxHtmlBytes. It still does not run a browser, execute scripts, accept banners, or inspect post-interaction cookies.

Use supplied snapshots when you need deterministic QA, before/after comparisons, or scans collected by your own browser/testing stack.

Limitations

  • This is not legal advice and does not certify privacy-law compliance.
  • Static snapshots cannot prove whether cookies are blocked before consent unless the supplied snapshot captures that state.
  • Optional live fetch does not execute JavaScript, so it may miss CMPs injected only after client-side rendering.
  • Browser rendering, banner interaction, and post-consent comparison are intentionally out of scope for this package.

Safe Use

Scan only pages you are authorized to test. Avoid collecting personal data in supplied snapshots. Redact session identifiers or user-specific cookie values before uploading input.