Review missing and conflicting technology signals
A practical checklist for consent gates, storefront scripts, legacy markers and the limits of HTTP-based technology detection.
Content reviewed: · Evidence and limitations
Check the inspection status first
A timeout or access failure is unknown evidence, not a clean negative. Keep these rows separate from successfully fetched pages that contain no supported marker. Recheck the public site manually when a prospect matters.
Consider what the server actually returned
Region rules, consent gates and security tools can return a different page to an automated HTTP client. StoreTechScan does not execute JavaScript or click consent banners. A tool that loads after interaction may therefore be invisible in this scan.
Distinguish a marker from current usage
An old script, migration remnant or dormant widget can still match a rule. A public marker is evidence to review, not a claim about licensing, configuration or actual event delivery. Multiple platform markers can appear during migrations.
Qualify with several independent observations
Combine the detected platform with catalog availability, a relevant app marker and a manual look at the site. Record uncertainty in campaign notes. Do not turn a single absent script into a categorical claim about a store’s problems.