Cookies and scripts
Everything OptSens found on your site lives under this section: scripts, cookies, iframes and the vendors behind them. The scanner visits your pages, records what runs, and OptSens sorts each item into a consent category. You review the result and change anything you disagree with.
How detection becomes consent
- The scanner loads your pages and records the cookies, scripts, iframes and tracking requests that appear. See OptSensBot for how the crawl works.
- Each detected item is matched against the OptSens categorized library. Known items get a category automatically. Anything not in the library is marked unknown for you to classify.
- Cookies become your cookie declaration, the public table embedded on your site.
- Scripts and iframes drive auto-blocking: each one is held back until the visitor consents to its category.
The five categories
Every cookie, script and iframe falls into one category. The category decides what consent the banner asks for and when the item is allowed to run.
| Category | Meaning | Blocked before consent |
|---|---|---|
| Necessary | Required for the site to work, such as login and cart | No, always allowed |
| Functional | Remembers preferences like language or region | Yes |
| Analytics | Measures traffic and how visitors use the site | Yes |
| Performance | Monitors speed, errors and load behavior | Yes |
| Advertising | Targets ads and measures campaigns across sites | Yes |
Necessary items are never blocked and are shown as Always active in the declaration. Everything else waits for the matching consent choice in opt-in regions with auto cookie blocking on. In opt-out regions, such as CCPA, items run until the visitor opts out. Geo rules control both per region.
Where each page fits
| Page | What you do there |
|---|---|
| Cookie declaration | View the public table of cookies grouped by category |
| Scripts and cookies | Review detected scripts and cookies, change their category |
| Iframe rules | Control how embedded iframes are blocked, add custom rules |
| Vendors | Select IAB TCF and Google Additional Consent vendors |
Unknown items
The library covers the common providers. When the scanner finds something that is not in it, the item shows as unknown and is counted separately on the page. Assign a category to tell the banner how to handle it and to keep the declaration accurate. Your choice is kept across future scans. When the same item later receives an official category in the OptSens library, the library category takes over.
Run a scan first. If a page shows no scripts, cookies or iframes, the most likely cause is that the scan was blocked. See OptSensBot for how to allow the scanner through a firewall or bot challenge.