Website Monitor

The Astralis website monitor scans your websites the way a visitor experiences them, finds every cookie, tag, pixel, iframe, and network request they load, matches each one to the vendor behind it, and checks whether it respects the visitor's consent choice.

Marketing, analytics, and agency teams may add tags to a website through a combination of vendor scripts, tag managers, and third party configurations. The website monitor turns that sprawl into one reviewed inventory of third parties, keeps it current with scheduled scans, and records the evidence of how each one behaves around consent.

Follow a scan from page to vendor

Each scan works through the same four stages.

1. Pages. The monitor loads the website's URL, or every page in its sitemap up to the first 500.
2. Countries. The monitor visits each page from every country you select, through a connection in that country, so the site serves exactly what a local visitor sees.
3. Consent visits. On each page, the monitor records what loads before the visitor makes a choice, after Accept all, and after Reject all. The accept and reject visits run on sites managing consent with Astralis or with another supported consent platform. On any other site, the monitor records the first visit only.
4. Vendor matching. Compass, the Astralis privacy dictionary, matches each asset to the vendor that runs it and suggests its categories of consent.

Results land in the Action Center, grouped by vendor, ready for review.

See what the monitor finds

The website monitor reports five types of asset.

Every asset keeps the pages and countries it appeared on. Assets with machine-generated names, such as a cookie that carries a visitor ID, roll up into one consolidated asset, so a single vendor doesn't flood your results.

Turn findings into an accurate inventory

Reviewers add the assets they expect to the system inventory, under the vendor's system, with their categories of consent. Cookie assets you add attach to the privacy notices that cover their data use, so your privacy experiences list them and FidesJS can remove them when a visitor opts out. Assets you don't need, you ignore, and later scans leave them out.

On sites managing consent with Astralis, the monitor also runs a consent compliance check on every asset and gives it a status, such as Consent ignored when an asset loads after the visitor rejected it. A PDF report summarizes the findings for the team that owns your tag manager.

Key concepts