Why did a domain scan miss a Tracker?

A scan only observes resources that load on the selected public pages during that run. A Tracker may be absent when it loads only after interaction, behind authentication, in a region-specific flow, in an experiment, on an unscanned page beyond the plan limit, or after a third-party timeout.

Confirm that you registered the public hostname visitors use and that the relevant URL is discoverable from the sitemap or homepage. You can add the Tracker manually or category-tag the resource while you adjust discovery and rerun the scan.

Documentation: Domain Scans and Why Tracker counts can change.