Website monitoring glossary

The practice of replaying a recorded checkout flow (add to cart, shipping, payment, confirmation) on a schedule using a real browser, so functional breakages are detected within minutes instead of hours or days. Distinct from uptime monitoring, which only verifies that a URL returns HTTP 200.

A monitoring approach that compares the current state of a webpage (scripts, cookies, DOM, content) against a previous snapshot and reports differences. Tracefox performs change detection on every scheduled scan, then classifies each change by category and severity.

A fast, shallow verification that the critical path of a checkout, product → cart → shipping → payment → confirmation, still works end-to-end. Typically seven steps, completable in under two minutes manually or automatically on a schedule.

Software that displays a cookie/consent banner to users and enforces which tracking scripts are allowed to fire based on consent state. Examples: OneTrust, Cookiebot, Iubenda, Usercentrics, Osano, Termly, Complianz. Tracefox does not implement a CMP; it monitors whether an existing CMP is still working correctly.

A Google-defined framework (required in the EEA/UK as of 2024) that allows tags to operate in restricted mode when users have not granted full consent. Determines whether `ad_storage`, `analytics_storage`, `ad_user_data`, and `ad_personalization` are granted or denied. Misconfiguration is a common cause of silently-missing analytics events.

A server-side event-sending API offered by Meta (and equivalents by Google, TikTok) that complements the browser-side Pixel. Because CAPI events are sent from your server rather than the user's browser, they bypass ad blockers and Safari ITP. Best practice in 2026 is to send events via both Pixel and CAPI.

A browser (typically Chromium, Firefox, or WebKit) that runs without a visible UI, used for automated scraping, testing, and scanning. Tracefox runs real headless Chromium via Playwright to scan client websites and replay checkout flows, ensuring captures reflect what real visitors experience.

A JavaScript tracking snippet that sends user behavior events (page views, adds to cart, purchases) from a website to Meta's ad platform for attribution, retargeting, and audience building. When the Pixel silently stops firing, usually after a theme update or app install. Meta ads performance degrades within days.

Running the same test against multiple viewport sizes (commonly desktop 1280×800, mobile 375×812, tablet 768×1024) from a single recording. Catches device-specific checkout bugs that don't manifest at a single viewport, a common failure mode for third-party scripts that only load on mobile.

An open-source browser automation framework maintained by Microsoft. Tracefox uses Playwright internally to drive headless Chromium for both scanning and checkout replay, customers never write Playwright code; they interact with the product via a Chrome extension recorder and a web UI.

An automated, unattended capture of a target webpage's state that runs on a fixed cadence (monthly on Free, weekly on Starter, daily on Pro, daily on Business). Each scan is stored as an immutable snapshot. Tracefox diffs each new scan against the previous one to detect change.

An automatic tagging step in the Tracefox pipeline that categorizes each detected change into HIGH (tracking pixel disappeared, consent banner broken), MEDIUM (new script, new cookie, CMP config change), or LOW (minor content edit, styling update). Severity determines which notification channel an alert routes to.

An umbrella term for scheduled checks that simulate user interactions, page loads, API calls, checkout flows, to verify availability and correctness. Tracefox performs synthetic monitoring of website content and checkout flows. Note: "synthetic monitoring" in enterprise contexts usually refers to DevOps tools like Datadog, Checkly, and Catchpoint; Tracefox serves a different audience (agencies, SMBs).

A small JavaScript or image-based tag embedded on a webpage that reports user events to an ad or analytics platform. Common examples: Meta Pixel, Google Analytics 4 tag, Google Ads conversion tag, TikTok Pixel, LinkedIn Insight Tag, Hotjar tracking code. Silent removal of these is one of the most common, and most expensive, agency-managed site failures.

Continuous or scheduled comparison of a website's state (scripts, cookies, consent banners, content, policies) against previous baselines, with alerting when drift is detected. Distinct from uptime monitoring, which only checks HTTP responses. Tracefox performs change monitoring continuously and classifies findings by severity.

Client-facing deliverables. PDF reports, shareable status pages, detection pages, branded with the agency's own name and logo instead of the monitoring tool's. Tracefox includes white-label reports on Starter plan and above, making every client-visible surface agency-branded.

A Tracefox account scope that owns a set of monitored websites, checkout tests, and team members. In a typical agency setup, the workspace belongs to the agency and contains all client sites; team members are invited into the workspace to collaborate. Data is scoped per-workspace, there is no cross-workspace leakage.