Third-Party Script & Tracker Change Monitor
Pricing
$12.00 / 1,000 rendered script page checkeds
Third-Party Script & Tracker Change Monitor
Compare browser-observed scripts, tracker host matches and loading attributes across scheduled Playwright runs with persistent baselines and hashed paths.
Pricing
$12.00 / 1,000 rendered script page checkeds
Rating
0.0
(0)
Developer
ProdukDigitalAli
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
10 days ago
Last modified
Categories
Share
What does this Playwright script monitor do?
Detect script and tracker integration changes after website releases. This Actor renders supplied public pages in Chromium, observes script requests and external script DOM attributes, then compares them with the last complete baseline. It includes script elements injected during the observation window.
Use it alongside Browser Network & HAR Inspector and Cookie & Session Health Monitor. Apify provides API calls, scheduled runs, dataset export and integrations. Try the prefilled https://example.com/ page for a safe initial baseline.
Why use it?
Investigate script additions or removals after a release, tag-manager rollout, payment integration or vendor change. Reports include loading attributes and integrity fingerprints. Provider matches identify a small set of known hosts including Google Tag Manager, Meta Pixel, Clarity, Hotjar and OneTrust. These are observations, not compliance verdicts.
How to use it
- Enter one to three public URLs.
- Use a stable monitorKey such as release-homepage.
- Run once to create a baseline.
- Run later with identical URLs and observation settings.
- Inspect changeStatus and added, removed or changed IDs.
Each page has a fresh context. No login/session input or consent clicks. Main-frame DOM attributes are collected; script request observations may include child frames.
Input
urls: 1-3 HTTP(S) pages. monitorKey: 1-64 letters/digits/underscore/hyphen; default default. settleMs: default 1500, maximum 5000. navigationTimeoutSeconds: default 25, maximum 45. maxScriptsPerPage: default 100, maximum 200. Private destinations, credentials and nonstandard ports are rejected. Changing URLs or observation settings starts a separate baseline identity.
Output
CHECKED rows include scripts, changeStatus, added, removed, changed, finalPageChanged and timing/network evidence. First complete observations use BASELINE_CREATED; identical observations UNCHANGED. INCOMPLETE reports preserve prior baselines. ERROR rows contain fixed safe codes. Script/page paths and integrity values are hashed. No queries, raw paths, bodies, inline code, cookie values or authorization data persist. Hashes are identifiers rather than encryption: known path guesses can be matched. Download results as JSON, CSV, HTML or Excel. OUTPUT gives requested, succeeded, incomplete, failed and charged. Persistent baselines use a separate Actor-specific named key-value store.
Pricing and limits
Proposed standard PPE USD 0.012 per complete stored page check, including initial and unchanged complete observations. Error and incomplete reports are free. Actual price appears in Pricing after configuration; platform usage depends on the plan. Both dataset and baseline are stored before charge. chargeEligible is an eligibility flag; OUTPUT and platform events confirm charges.
Limitations and support
Requests do not prove successful script execution. Query-only version changes are ignored. Multiple instances at one origin/path collapse. Late injections, inline/eval and worker-only imports are not inspected. Images/fonts/media and mutation requests are blocked, so results describe a bounded diagnostic browser. CrossOrigin means different origin, not ownership under the public suffix list. Schedule serial runs to avoid baseline races. Contact the developer through Issues with sanitized examples.
