Run A, Run B, and Run C

Fresh browser, California profile, no stored cookies, no prior consent. Packet capture from the first byte for about 30 seconds with no click. Goal: see what transmitted visitor data before a choice. Also records whether a CMP was detected and whether it is working.

Dashboard Run A also runs a source pre-scan. Tags in HTML that never fired because SiteTrust blocked them still count as detected. The UI should not say “0 trackers” if the pre-scan found tags.

The robot accepts, then watches what loads. Analytics and marketing should appear only after that Accept and bind to a receipt. If Run A found zero fired tags only because the banner blocked them, Run B is still worth running. N/A is for “there is nothing to accept,” not for “the banner did its job.”

The robot declines, then navigates. Non-essential tags must stay off. Script termination matters. A site that honors Decline on page one and fires Meta on page two fails.

• No consent banner detected on Run A.
• A third-party CMP was detected. Automated click is supported for SiteTrust Consent, not for every vendor.

• Run A → Pre-Consent Behavior, and feeds Tracker Inventory and Banner Conformance.
• Run B → Post-Accept Behavior.
• Run C → Post-Decline Behavior.
• The live badge tracker gate wants A PASS, working banner, B PASS (or eligible N/A), and C PASS from a recent client session.