Site Behavior Lab
Site

www.cvs.com

Baseline visit
Requested address
https://www.cvs.com/
Report ID
20260810-43de247f94bc3060390a811c7ed0c294
Evidence SHA-256
435adab00777851cb53ccbd7cf4ba732a7451ba86ffdf570d161c4d9a5932c32
Scanner
playwright-chromium

Public corrections ledger · SBL-CORR-2026-001

This report has a reviewed clarification

SBL-CORR-2026-001: The historical input-probe disclosure overstates coverage. Unload-only transmissions were not reliably recorded. Focus and blur handlers could run, and per-field failures were not fully counted. These reports cannot establish absence of input transmission outside their retained observations.

Read the public review record

cvs.com recorded 111 fewer third-party requests in the visit configured for Brave-list blocking.

Where this page's requests went

Both visits. One mark is one request row in the retained log.

No blocking

www.cvs.com itself157 requestsrequests that stayed on the site
Catalogued services70 requests6 names: Google 45, Quantum Metric 10, Tealium 9, Microsoft 3, The Trade Desk 2, and 1 more
Hosts the catalog does not name59 requests16 hosts; the catalog cannot say who operates them

Brave-list blocking

www.cvs.com itself157 requestsrequests that stayed on the site
Catalogued services1 request1 name: Tealium 1
Hosts the catalog does not name17 requests7 hosts; the catalog cannot say who operates them
Not measuredabsence here is not evidence of absence
  • Other pages on this site
  • Signed-in visitors, other browsers and other regions
  • Anything that loads only after interaction or consent
  • Services the catalog does not name
  • Checks with incomplete evidence
  • one request on record, same site
  • one request on record, cross-site
  • not measured

The visit with no blocking made 286 requests; the visit configured to apply Brave's ad-block engine and default Shields filter lists (a simulation in this scanner's browser, not a live Brave-browser visit) recorded 111 fewer third-party requests. The blocker directly stopped 13 requests; the remaining difference may include follow-on requests that never started once their sources were blocked, plus run-to-run variance. SBL-CORR-2026-001: The historical input-probe disclosure overstates coverage. Unload-only transmissions were not reliably recorded. Focus and blur handlers could run, and per-field failures were not fully counted. These reports cannot establish absence of input transmission outside their retained observations.

6tracking-service entities
129cross-site requests
9third-party cookie records

Worth checking

Bottom line: this visit has signals worth checking

The scan observed signals a non-expert should not have to decode from raw request tables. Some detector evidence was incomplete; each affected detector card states its own retained or unavailable scope, while completed request, cookie, and storage measurements keep their recorded exactness.

Where severity is ranked, the cohort is a curated set of popular, mostly commercial sites, not a random sample of the web. Details

The cards below translate the evidence into plain language. Where a measured distribution exists, severity ranks this visit against percentiles from this report's cohort, with each percentile card naming its metric-specific measured-site denominator; otherwise it uses fixed reference thresholds. That cohort is drawn from a curated set of popular, mostly commercial sites, not a random sample of the web. The request log, domain table, and methodology remain below for verification.

286 requests observed in one controlled visit.

What was checked

Page
https://www.cvs.com/
When
Aug 10, 2026, 6:52 AM UTC
Setup
Both visits used headless Chromium in a desktop window of 1440 × 980, with en-US language and UTC time zone. Both ran from a GitHub Actions Ubuntu runner; the network region was not recorded. Neither sent the Global Privacy Control (GPC) signal.
Visits
Two visits configured to differ in Brave-list blocking: No blocking and Brave-list blocking.
Interactions
Typed a made-up test value into 1 form field in each visit, never submitting the form. No scrolling, clicking or consent interaction.
Outcome
Both visits completed, but some evidence in the No blocking visit was cut short.

What these visits could not see

  • Other pages on this site. Only the requested page's activity was recorded. The privacy policy was opened only to read its text, and none of its activity was recorded.
  • Signed-in visitors, other browsers and other regions. Both visits were automated, from a fixed en-US / UTC profile. Sites can behave differently for real users, browsers, regions, accounts, or network locations.
  • Anything that loads only after interaction or consent. Trackers that load that late are not observed, so counts are a lower bound.
  • Services the catalog does not name. Service labels use a US-biased hand-curated catalog, so regional services may be under-labeled.
  • Checks with incomplete evidence. In the No blocking visit only: the consent banner, the privacy policy check, session-recording signals, fingerprinting, the typing test, CNAME cloaking and advertising pixels. Each linked card states what was retained.

Worth checking

78 requests matched Brave Shields filter lists

78 requests matched the default filter lists of Brave Shields, the ad and tracker blocker built into the Brave browser, while loading normally.

Blocking can also prevent follow-on requests, so this number is neither a measured block count nor what a Brave visit would block. Details

Computed with Brave's own ad-block engine and default filter lists in classification mode: matched requests were not blocked by the scanner and remain in this report's observed request counts. This is Site Behavior Lab's list-based simulation, which applies every list to the site's own requests too. Brave's default Standard setting skips most of these lists for such requests, so its results can differ.

The hand-curated service catalog separately matched 70 request rows in this visit.Show matched requests

Not flagged

Lower values observed across comparable metrics in the Brave-list blocking attempt

The blocking visit ran with the scanner configured to apply Brave's ad-block engine and default Shields filter lists. It was a simulation in this scanner's browser, not a live Brave-browser visit, and application was not verified. Compared with the unblocked visit, it showed 111 fewer third-party requests, 4 fewer third-party cookies and 69 fewer tracking-related service requests.

Treat this as an observed difference, not a measured blocking rate. Details

Services only seen in the unblocked visit: Google, Quantum Metric and Microsoft, plus 2 others. The blocking visit's engine directly blocked 13 requests; the remaining difference may include follow-on requests that never started once their sources were blocked. A single paired comparison can also reflect run-to-run variance (ad rotation, caching, experiments).

Signed per-metric differences between the two visits; nothing is summed across metrics.Show matched requests

Context

Privacy policy read; it made no statement this scan can check

None of the statements this scan knows how to check appear in the policy text. As a result, nothing was compared against this visit's evidence (no reliable company-mention results available). Policy mentions of Google, Quantum Metric and Tealium, plus 3 others are unknown because this read may have stopped at the scanner's 400,000-character limit. That is a limit of the automated check, not a finding about the site either way.

Evidence collection was cut short, so this covers only what was recorded before the cutoff. Details

Statements checked automatically: blanket no-cookie claims, third-party-cookie claims, and combined do-not-sell-or-share claims against advertising-pixel identifier fields. Global Privacy Control claims are never checked against request counts, which cannot show whether selling or sharing stopped.

Policy at https://www.cvs.com/…/help/…; 0 checkable statements matched; no reliable company-mention results available. Policy mentions of Google, Quantum Metric and Tealium, plus 3 others are unknown because this read may have stopped at the scanner's 400,000-character limit.

Worth checking

Catalogued service domains recorded responses during this visit

Google, Quantum Metric and Tealium, plus 3 others appeared in the request log.

A catalog match identifies a maintainer-reviewed service/domain mapping; it does not establish why an individual request occurred, what it carried, or whether profiling happened. Details

Functional catalog labels include advertising, analytics / tag management and session replay / product analytics. This scan could not identify 9 of the 30 third-party hosts recorded here, so it cannot say who operates them. That is a limit of identity coverage, not evidence about the site. Catalog labels include session-replay or behavior-analytics services: Quantum Metric. The domain match alone does not prove that a recording occurred.

129 cross-site requests across 30 third-party hosts.At or above the 75th-percentile mark for third-party domains across the 86 sites measured for this metric. Elevated distinct tracking-service entities count (at or above the 6 reference threshold).Show third-party requests

Context

Requests were dispatched to catalogued major-platform domains

This visit dispatched requests to catalogued domains for Google and Microsoft.

The domain matches identify services, not the requests' purpose, payload, or whether any profile linking occurred.

48 requests to these platforms.Show catalog-matched requests

Context

Google Tag Manager loaded; a remarketing sync cannot be told from this report

This visit contacted Google Tag Manager and recorded no request to a Google Analytics collection host. It also recorded DoubleClick hosts whose names this report generalizes, the remarketing sync host's among them.

This report neither shows nor rules out the sync. Details

Tag Manager is a loader. It can fetch Google Analytics or other tags, or none; this report cannot tell which it fetched here. The sync goes to stats.g.doubleclick.net, and a published report writes that name the same way as DoubleClick's ad-serving hosts.

googletagmanager.com observed; no google-analytics.com or analytics.google.com request; DoubleClick hosts recorded under generalized names.Show catalog-matched requests

Worth checking

Third-party cookies were present

9 third-party cookies showed up during the visit.

This report does not retain cookie values or partition keys, so it does not establish whether a cookie was a persistent identifier or could recognize a visitor across sites. Details

The scanner observed cookie metadata whose domain crossed the scanned site's registrable-domain boundary.

136 cookies total in this report.At or above the 75th-percentile mark for third-party cookies across the 86 sites measured for this metric.

Look closer

See other visits' cookie counts

Opens this site's history page, which lists the third-party cookie count each of its retained reports recorded.

Context

Session-replay vendor observed

Quantum Metric appeared in the request log.

The domain match alone does not prove that a recording occurred. Details

Catalog labels include session-replay or behavior-analytics services: Quantum Metric. Treat this card as a review prompt rather than proof.

Known session-replay vendor(s): Quantum Metric.

Look closer

Show requests to Quantum Metric

Opens this report's request log filtered to Quantum Metric; listener registrations are not request rows, so the log cannot show what was observed.

Context

Fingerprint-like browser APIs were called

At least 1 retained high-entropy API call appeared in the incomplete instrumentation log.

These calls can be legitimate (charts, graphics, media), so the count is observational, not a severity score, and it excludes Web and Service Workers. Details

Top calls: webgl.getParameter.UNMASKED_RENDERER_WEBGL.

Retained incomplete evidence includes 1 API event record; no exact API-family total is available.

Domain evidence

31 recorded domains
The busiest recorded domains of the No blocking visit, with role, request count, request start times and catalog match.
DomainRequestsWhen, 0 to 17.6 sCatalog matchRoleResource types
www.cvs.com157No catalog matchfirst-partydocument, stylesheet, script, font, image, media, xhr, fetch
*.*.doubleclick.net23Google: advertisingservicexhr, script, fetch, document, other, image
cdn.cookielaw.org11No catalog matchthird-partyscript, xhr, fetch, image
www.youtube.com10No catalog matchthird-partydocument, script, stylesheet, image, xhr
*.tiqcdn.com9Tealium: tag management / customer dataservicescript
*.quantummetric.com9Quantum Metric: session replay / product analyticsservicefetch, ping
www.google.com9No catalog matchthird-partyscript, fetch, document, image
*.adobedc.net9No catalog matchthird-partyfetch, ping
ad.doubleclick.net8Google: advertisingservicefetch
*.google.com7Google: advertisingserviceimage
*.adtrafficquality.google5No catalog matchthird-partyxhr, script, document, image
*.bing.com3Microsoft: advertising / analyticsservicescript, image
*.googlesyndication.com2Google: advertisingserviceimage, script
www.googleadservices.com2Google: advertisingservicescript
*.adsrvr.org2The Trade Desk: advertising / demand-side platformservicescript, xhr
*.go-mpulse.net2No catalog matchthird-partyscript, xhr
app.launchdarkly.com2No catalog matchthird-partyxhr
events.launchdarkly.com2No catalog matchthird-partyxhr
cdn.appdynamics.com2No catalog matchthird-partyscript
static.doubleclick.net1Google: advertisingservicescript
www.googletagmanager.com1Google: analytics / tag managementservicescript
*.*.googlesyndication.com1Google: advertisingservicedocument
*.demdex.net1Adobe: analytics / advertisingservicefetch
cdn.quantummetric.com1Quantum Metric: session replay / product analyticsservicescript
*.gstatic.com1No catalog matchthird-partyfont
*.ytimg.com1No catalog matchthird-partyimage
jnn-pa.googleapis.com1No catalog matchthird-partyxhr
*.onetrust.com1No catalog matchthird-partyxhr
cdn1.adoberesources.net1No catalog matchthird-partyscript
*.impactradius-event.com1No catalog matchthird-partyscript

+1 more in the evidence explorer below.

Raw evidence

Open the interactive evidence explorer

The findings above are built from the stored report. Load the request rows, domains, cookies, storage keys, browser signals, visit phases, charts and CSV export when you want to check them; the versioned report JSON is always available below without this interface.

This versioned report is currently retained in the public corpus. Follow the currently retained site history, repeat the same public route when it is available, or request a transparent evidence correction.

Report ID
20260810-43de247f94bc3060390a811c7ed0c294
Site
www.cvs.com
Latest visit
Schema
v1 schema · facts legacy-derived · descriptive report
Verify recorded provenance

Baseline visit

Started
Run quality
cut short: the in-page fingerprint observer could not read every frame, so the fingerprinting evidence is incomplete; derived from status and warnings
Scanner
playwright-chromium
Browser
151.0.7922.34
Redaction
not recorded by this schema
Provenance
Exact build and instrument digests were not recorded by this legacy schema.

Variant visit

Started
Run quality
complete; derived from status and warnings
Scanner
playwright-chromium
Browser
151.0.7922.34
Redaction
not recorded by this schema
Provenance
Exact build and instrument digests were not recorded by this legacy schema.

Recorded provenance is self-reported measurement metadata, not a cryptographic attestation. The public versioned report JSON contains the retained public evidence; see the methodology for interpretation and retention limits.

This report covers what the scanner measures, not everything a site can do. 17 browser surfaces are not instrumented at all (Every page except the one that was scanned; Anything that only loads after scrolling or interaction; Why a request happened, as a causal chain; and 14 others), 3 capabilities are declined by policy, and 3 are outside what any single visit can see. Their absence from this report is not evidence that they did not occur. Read the published coverage boundary.

Detector accuracy is unmeasured. No calibration study currently publishes a precision or recall for the detectors on this page, so a detector match here is a recorded observation, not a calibrated classification. A study has been recorded for pixel-events and does not support a published rate under the current build. How detector accuracy is measured.

Severity percentiles come from this report's exact schema, methodology, tracker-catalog, ServiceRole-taxonomy, metric-contract, producer, and Global Privacy Control cohort. Each percentile card's measured sites are among 99 sites with a successful load across all cohorts. Other methodologies and post-choice consent visits are excluded from each card's denominator, while failed or block-page attempts are outside that coverage. Visits with capped or incomplete request evidence are left out of each mark. They tend to be the heaviest pages, so a mark can sit lower than the cohort's true mark.

Approved use boundary: This report is investigative evidence that requires independent corroboration. It is not a standalone legal determination and not the sole exhibit in a legal proceeding. Recorded in this project's release manifest on .