Built by Cosmos Web Tech
A division of Ganda Tech Services — Digital Solutions for Sydney Businesses
← Back to Tag & Cookie Sentinel

Support

Tag & Cookie Sentinel

Getting Started

After installing the extension, navigate to any website. Tag & Cookie Sentinel begins monitoring immediately from the moment the page starts loading — no setup or configuration is needed.

  1. Click the extension icon in your Chrome toolbar to open the popup summary.
  2. The popup shows how many tags were detected, how many cookies were set, and whether any fired before consent was given.
  3. Click Open Dashboard in the popup for the full five-tab analysis.

Dashboard Tabs

Overview

A high-level snapshot of the current page: all detected tags with their colour-coded vendor dots, a cookie breakdown by purpose (Analytics, Advertising, Authentication, etc.), and a list of any pre-consent activity.

Tags

A filterable table of every tag detected on the page. Columns show the tag name, vendor, category, total fire count, number of fires before consent, any PII keys found in the payload, and a sample payload snippet. Use the search box or the category dropdown to narrow the list.

Cookies

A filterable table of every cookie set by the page. Each row shows the cookie name, domain, classified purpose, vendor attribution, first/third-party status, session vs persistent type, security flags present, missing flags (e.g. Secure, HttpOnly, SameSite), and whether it was set before consent.

Activity Feed

A chronological timeline of all events — tag fires, cookie sets, and consent interactions — since the page loaded. Use the Pre-consent only toggle to show only events that occurred before consent was recorded.

Compliance

Six compliance cards with red / amber / green severity ratings covering: pre-consent tag fires, PII transmission, insecure cookies, pre-consent cookies, third-party cookie exposure, and overall consent status.

Frequently Asked Questions

Why does the extension need access to all websites?
Tag & Cookie Sentinel uses the webRequest API to observe network requests in real time. Because tags and cookies can be present on any website, the extension needs <all_urls> access to monitor whichever page you are currently viewing. It does not collect or store data from pages you are not actively inspecting.
A tag I know is on the page is not being detected.
The extension recognises tags by matching known URL patterns. If a vendor recently changed their endpoint domain, or if the tag fires via a server-side proxy (server-side tagging), the client-side URL pattern will not match. You can still see the raw request in the Activity Feed to identify it manually.
How does pre-consent detection work?
The extension injects a small content script at document_start — before any other scripts run. It watches for clicks on known consent management platform (CMP) buttons (OneTrust, CookieBot, Didomi, TrustArc, and others) and monitors writes to localStorage that match consent key patterns. Any tag fire or cookie set that occurs before one of these consent signals is flagged as pre-consent.
The consent was given but tags still show as PRE.
This means those tag fires occurred before the consent interaction was detected — which is an actual pre-consent violation. If you believe the consent was given earlier (e.g. via a stored consent from a previous session), check the Activity Feed for a Consent recorded event and its timestamp relative to the tag fires.
PII keys are shown but no actual PII values are displayed.
The extension only checks whether known PII field names (such as email, ph, uid) appear in the tag payload. It does not log, store, or display the actual values of those fields, to avoid the extension itself handling personal data.
Data from a previous page is still showing.
Click the Clear button in the popup or sidebar to reset the state for the current tab. Data is also automatically cleared when you navigate to a new page (each full page load starts a fresh session for that tab).
The dashboard shows no data even though tags are present.
The extension monitors requests from the moment the page begins loading. If you open the dashboard on a page that has already finished loading, the data from the current load is still shown. If the page was loaded before the extension was installed or enabled, reload the page and check again.
Does this extension slow down my browser?
Tag & Cookie Sentinel uses the non-blocking webRequest observer API — it observes requests without intercepting or delaying them. The content script is minimal and runs only to detect script injections and consent interactions. There is no measurable impact on page load performance.

Contact Support

If you have a question not covered above, or you have found a bug, please get in touch:

Email us at

support@cchk.info

Please include the website URL where the issue occurred and a description of what you expected to see vs. what you saw.