Open it
Open a project in Pulse, click History, then click a scan. The page title is the scan's date and time in the property's time zone, for example "Scan - Oct 14, 2026 9:30 AM (ET)".
Overview
The This scan panel lists what was measured:
| Item | Shows |
|---|---|
| Scanned | When the scan ran |
| Pages scanned | How many pages were visited |
| Checks run | Consent and/or Accessibility |
| Browser passes | How many separate browser visits the scan made |
Below it, one card per check that ran. Consent & Privacy shows the privacy score out of 100 (or "not scored"), the tier, and the issue and observation counts. Accessibility shows the number of rules failing and the most severe impacts. Click View details on a card to open that check. Back to scan overview returns here.
A check the scan did not run has no card. Not measured is never shown as a clean result.
Consent & Privacy
When reports were published for the scan, a Reports bar offers View Report, Shareable Report, and a button to copy the shareable link.
| Section | What it holds |
|---|---|
| Tiles | Privacy Score (or "Not scored" when the consent test could not complete), Privacy Tier, Technologies, Issues, Observations, and the site Category |
| Privacy Categories | One row per scored category with its score, a progress bar and notes: CMP Detected, CMP Timing, Consent Mode, Pre-Consent Tracking, Privacy Link, Consent Enforcement. Unscored categories such as US Opt-Out Control and Cookies After Opt-Out are listed underneath with their notes |
| Technologies & Features | Detected technologies and site features |
| Findings | Issues and observations, with severity. An observation is a record of what the site did, not a fault |
| Consent Pass Detail | One tab per browser visit (below) |
| Scanned Pages | Every page visited, the first marked Primary, each with a link to open it |
| Scan Screenshots | A screenshot from each consent state |
See Privacy Score for how the score is built.
Consent Pass Detail
Each tab is a separate visit in a fresh browser. Three chips above the tabs count marketing and analytics trackers: Trackers pre-consent, Trackers after deny and Trackers after GPC. The last two turn red when above zero.
| Tab | The visit |
|---|---|
| Baseline (pre-consent) | Loads the site with no consent action, as a first-time visitor sees it |
| Consent Denied | Rejects consent on the banner, then observes |
| GPC Enabled | Sends a Global Privacy Control signal |
| Opt-Out Used | Finds and uses the site's US opt-out control instead of a consent banner, then observes. Run only for projects using the US opt-out rubric; the tab is hidden otherwise |
Consent Denied, GPC Enabled and Opt-Out Used should not introduce trackers or new cookies. A red dot on a tab means a tracker fired in that visit.
Each tab shows:
- The visit's screenshot. Click it to open full size.
- Third-party requests, one row per host and vendor, with the number of requests and a type:
| Type | Meaning |
|---|---|
| Tracker | A marketing or analytics request. Red in the post-consent tabs |
| Consent Mode ping | A Google request sent with ad and analytics consent denied (or, on US opt-out scans, with ads opted out). Not counted as a tracker |
| Library | A vendor script being loaded, not data being sent |
| Consent | The consent management platform |
| Tag Manager | A tag manager container |
| Other | Anything else |
- Cookies in this pass. Cookies that were not present in the previous visit are marked new.
- Browser storage: local and session storage keys, with new keys marked the same way.
Requests to your own domain are left out unless they are trackers.
Accessibility
| Section | What it holds |
|---|---|
| Tiles | Rules Failing (of rules checked), Most Severe, Elements affected, Rules Passed, Engine |
| Impact Breakdown | Rules and affected elements per impact level |
| Findings | Failing rules, most severe first. Open one for the affected elements |
| Scan Context | Page scanned, final URL, page title, engine, viewport and when it was measured |
The accessibility check runs against the primary page and reports findings only. It does not judge legal conformance.
Empty states
| You see | It means |
|---|---|
| "No data found for this scan." | The scan has no stored result |
| "No accessibility result for this scan" | The scan did not run that check, or its results are not processed yet |
| "The accessibility check could not complete" | The check ran and failed. The reason is shown |
TagPipes monitors, configures and reports. It does not determine legal compliance and does not provide legal advice. Output is informational and reflects observed state at the time of observation. Confirm any regulatory interpretation with your counsel.