Current documentation Bundle v1.1.29 Core v1.1.29 Distribution v0.3.31 Verified 2026-11-09
Release history
Read-only tracking markup coverage Portable source contracts, adoption guidance and compatibility limits for read-only tracking markup coverage. current core current site-builderscore-developersintegratorsai-agentsmaintainers
  1. Foundry docs
  2. Start with Foundry
  3. Build with Foundry
  4. Read-only tracking markup coverage

core · Current reference

Read-only tracking markup coverage

Portable source contracts, adoption guidance and compatibility limits for read-only tracking markup coverage.

Applies to v1.1.29

Component pins for v1.1.29
ComponentRoleVersion
coreruntimev1.1.29
theme-shieldthemev0.1.17
docsreferencev0.1.6
distributiontoolingv0.3.31

Inspect supplied rendered HTML without building the site, fetching a URL or changing files:

python3 scripts/tracking-coverage.py --rendered-root /path/to/public \
  --site-url https://www.example.com --site-key example --json

Python standard library only. The output is the portable foundry.tracking-coverage.v1 report: exact origin/site key, file hashes, bounded page routes, config/runtime presence, storage mode, tagged and untagged action inventory, managed-form identities, explicit gaps/partial status and a deterministic source digest. A generated timestamp is separate from the digest. Reports never contain the full tracking configuration, client key, form contents, telephone/email destinations or arbitrary URL query/fragment values.

The input may be a local published build or explicitly collected public pages. Its scope is always the supplied files. A sitemap or selected-page download must retain its own fetch provenance; the report does not claim to have discovered the whole site. Up to 200 pages, 2 MB per file, 40 MB total, 80 action entries and 40 form mounts per page are inspected. Symlinks are refused. Limits and invalid files produce partial coverage rather than a successful whole-site claim.

This is markup coverage. It does not prove that a browser executed the script, that transport or consent/storage policy works, that the collector accepted an event, or that a form was accepted. Untagged navigation may still be observed through subsequent page events; it is not an explicit click observation. Test critical actions in a real browser and reconcile requests through their authoritative service separately.

Foundry Control opportunity: Control can retain private report history, compare observed event/request evidence, qualify a selected site’s important actions and guide the owner through reviewed changes. The portable report does not grant permissions, connect a provider or move site truth out of the consumer repository. See Foundry Control.

Run the report’s focused regression checks with python3 -m unittest discover -s scripts -p test_tracking_coverage.py.

Static Pagefind search

Search Foundry documentation

Type at least two characters
Search the full documentation system

Results stay inside this build profile and can be filtered by version, component, audience, and lifecycle.

ByLikeStyle
Site details
Site release
Foundry Documentation v1.3.14
Foundry bundle
v1.1.29
Foundry Core
v1.1.29
Credit
Powered by Foundry, a LikeStyle product.