Your Consent Choices and What Your Site Does With Them

A consent-versus-script behavior review asks a simple operational question: do the choices a site presents align with the technologies its owners expect to find? It is not a shortcut to a legal conclusion. It is a structured way to turn an abstract concern about tags and permissions into specific evidence for the responsible teams to review.

What teams commonly look for

The review begins with the intended consent design and the known vendor inventory. Teams then inspect public page evidence for resource references and visible consent markup, asking whether the results are expected. A mismatch is a prompt for investigation, not proof of what happened in every visitor session.

• Analytics resources that appear before a visitor has made a permission choice.
• Advertising or session-recording references that remain visible when the intended configuration should restrict them.
• New scripts, pixels, embeds, or vendors that do not appear in the team's documented inventory.
• Expected technology references that are absent after a configuration change and need a technical check.

Use static evidence honestly

Consentlytics currently provides a point-in-time view of publicly accessible static HTML and discovered resources on authorized sites. That can help identify which script and vendor signatures merit follow-up. It cannot click a consent control, apply an opt-out, observe runtime network activity, or prove whether a resource executed after a visitor made a choice.

Browser-level interaction checks, ongoing monitoring, and regional or device comparisons are planned roadmap capabilities. Until then, use a static scan as a focused inventory and review input: confirm ownership, compare it with tag-management and CMP configuration, and ask the appropriate engineering or privacy owner to validate any concern.